The initial release of `bin/readme2index.sh` tool that converts `READMD.md` and various JSON files such as `.winner.json` as well as "author/author_handle.json" files. Applied the `readme2index.sh` tool to generate `2020/ferguson1/index.html`. We generated the `2020/ferguson1/index.html` by executing: ```sh ./bin/readme2index.sh -v 3 2020/ferguson1 ``` NOTE: This above tool requires **pandoc to be installed**. See the [pandoc web site](https://pandoc.org) for how to install. We used _HomeBrew_ to install it, but there is also a _macports_ process as well. NOTE: While the above web page does have formatting issues, it is a first attempt data driven programmatic web page generation. Some adjustments can be made by mostly improving `ioccc.css`, and some perhaps by modifying how `bin/pandoc_wrapper.sh` invokes pandoc. But probably most of the improvements can be made by fixing and improving `ioccc.css`. TODO: Fix and improve the `2020/ferguson1/index.html` web page by fixing and improving `ioccc.css`. Moved scripts and tools needed to generate HTML pages into a new `/bin` subdirectory. TODO: Consider getting rid of the [build-ioccc repo](https://github.com/ioccc-src/build-ioccc) and just use the `/bin` subdirectory. NOTE: Some links in the `2020/ferguson1/index.html` web page do not (yet) exist. TODO: Once the basic format of the `2020/ferguson1/index.html` web page is somewhat reasonable, generate `index.html` pages for other winners. Generate the year level `index.html' files. Generate the top level HTML files, including the missing `location.html` file. Greatly simplified the `.winner.json` file format, removing a number of fields that were not strictly needed for generating an inventory on a `index.html` page. Updated various versions: * `bin/gen-author.sh` VERSION="1.3 2024-01-14" * `bin/gen-inventory.sh` VERSION="1.0 2024-01-14" * `bin/manifest.winner.json.awk` VERSION="1.0 2024-01-14" * `bin/pandoc_wrapper.sh` VERSION="1.3 2024-01-14" * `bin/readme2index.sh` VERSION="1.0 2024-01-14" * `bin/subst.default.sh` VERSION="1.1 2024-01-14" * `bin/subst.winner-index.sh` VERSION="1.1 2024-01-14" * `tmp/gen_path_list.found.sh` VERSION="1.1 2024-01-14" * `tmp/gen_winner_json.sh` VERSION="1.1 2024-01-14" The `.winner.json` file format from winner_JSON_format_version "0.5 2023-11-04" to "1.0 2024-01-14". All `.winner.json` files have been updated to use the new `.winner.json` file format. The manifest (`tmp/manifest.numbers` and `tmp/manifest.csv`) has updated to use the new `.winner.json` file format. The following procedure was used to generate the `tmp/manifest.csv` manifest file: 0. open [manifest.numbers](manifest.numbers) in numbers: modify if/as needed NOTE: Please try to keep the [manifest.numbers](manifest.numbers) spreadsheet in order order. Use Organize -> Sort -> ((Sort Now)) to sort. NOTE: Empty fields in the [manifest.numbers](manifest.numbers) spreadsheet are not allowed. By default, a cell that is empty is colored as a warning. 1. File -> Export To -> CSV... * 1a. `[ ]` Include table names (unset) * 1b. Text Encoding: Unicode (UTF-8) * 1c. Click ((Save..)) 2. Save As: manifest.csv * 2a. Select the `tmp` directory 3. Click ((Export)) * 3a. If needed click ((Replace)) 4. Execute ./tmp/[fix_csv.sh](fix_csv.sh) NOTE: You must run the [fix_csv.sh](fix_csv.sh) in the above step in order to make the CSV file usable by other tools. NOTE: If no changes are needed in the above step, the original file content will be restored. 5. Execute ./tmp/[gen_path_list.found.sh](gen_path_list.found.sh) NOTE: The above step silently performs a `make clobber` at the top level, and so it takes a bit of time. NOTE: If no changes are needed in the above step, the original file content will be restored. 6. Execute ./tmp/[check_path_list.sh](check_path_list.sh) NOTE: The above step prints nothing and for an exit 0, then all is well. If there is a problem, such as files found that are not part of the manifest, or files in the manifest that are not found, then an error message will be printed and the tool will exit non-zero. If errors are reported, go back to step 0 and correct the errors. 7. Execute ./tmp/[run_all.sh](run_all.sh) ./gen_winner_json.sh NOTE: The above step will take a few seconds to run. It will rebuild all `.winner.json` files for all winners. NOTE: If no changes are needed in the above step, the original file content will be restored. 8. Execute `git status` and inspect changes NOTE: Check in changes if and as needed. NOTE: In a number of shell scripts under `bin/*.sh`, and in the `bin/manifest.winner.json.awk` script you will find comments of the form: ``` ``` This is a note that when tools such as `jnamval` (and `jval` and `jfmt`) are ready, these gross hacks should be replaced with calls to those tools. Until they are ready, some must be careful with the layout of JSON files. A number of bugs and typos have been fixed. NOTE: Fixing typos in the files touched by this comment is welcome. This includes scripts, data files, text files, etc. The _inventory_order_, _display_as_, _display_via_github_. and _winners_text_ fields of the [manifest.numbers](manifest.numbers) spreadsheet were just set to have some initial values. As they impact the inventory displayed on `index.html` pages, their content needs to be improved. NOTE: Improving the above mentioned fields of the [manifest.numbers](manifest.numbers) spreadsheet is welcome.
To build:
make
Bugs and (Mis)features:
The current status of this entry is:
STATUS: missing or dead link - please provide them
STATUS: INABIAF - please **DO NOT** fix
For more detailed information see 2011 dlowe in bugs.md.
To use:
./dlowe -<n_iterations> corpus1/ [...] corpus0/ < start.net > trained.net
NOTE: In the above command, the directory args MUST end in a /.
Then to use trained.net:
./dlowe file [file ...] < trained.net
Try:
Try these pre-trained networks:
./try.sh
NOTE: The dlowe-aux-data/ directory, which try.sh refers to, was
created by:
tar -jxf dlowe-aux-data.tar.bz2
Judges' remarks:
This entry is a ghoulish example of a brain (dead?) neural network classifier. It comes with a set of corpora for you to try.
ioccc-winlose-trained.net
You can create your own trained networks. For example, we trained a network on the C code of entries that were supplied to the 20Th IOCCC.
The ioccc-winlose-trained.net was trained using the
earlystop.pl tool:
rm -f ioccc-winlose-trained.net
./earlystop.pl ioccc-winlose-trained.net ioccc_won_training/ ioccc_lost_training/ ioccc_won_test/ ioccc_lost_test/
where:
-
ioccc_won_training/1/2 of C code of the 20th IOCCC winners (except for dlowe.c from 2011) plus 1/2 of the C code winners from prior IOCCC contests -
ioccc_won_test/1/2 of C code of the 20th IOCCC winners (except for dlowe.c from 2011) plus 1/2 of the C code winners from prior IOCCC contests -
ioccc_lost_training/1/2 of C code from entries that that did not win -
ioccc_lost_test/1/2 of C code from entries that that did not win
NOTE: The above directories were not shipped and everything from the entries
that did not win were flushed to /dev/null.
The earlystop.pl tool wrote:
training 1 to 1001...
training 1001 to 2001...
prior error = 56.746974766043; current error = 58.095691135305
The resulting ioccc-winlose-trained.net file was included in the
dlowe-aux-data.tar.bz2 tarball.
The dlowe.c was explicitly excluded from this trailing set, so this test is interesting:
./dlowe dlowe.c < dlowe-aux-data/ioccc-winlose-trained.net
NOTE: this is done in try.sh.
The match of dlowe.c to the lose/win trailed network was:
dlowe.c 0.125108
NOTE: The non-artificially intelligent decisions of the IOCCC judges include random quirks and their non-linear judgment calls not found in the ioccc trained network. Just because C code is or isn't scored highly by this network does not mean it will win or lose a future IOCCC. On the other hand ... it just might!
other data sets to try
While we cannot supply you with the losing IOCCC source code, the author did supply a number data sets on which to test:
We created the english-trained.net as follows:
./dlowe -8000 dlowe-aux-data/english-1/ dlowe-aux-data/english-0/ < /dev/null > dlowe-aux-data/english-trained.net
-
dlowe-aux-data/english-0/ Non-English (French) text
-
dlowe-aux-data/english-1/ English (non-French) text
We created the png-trained.net as follows:
./dlowe -8000 png-1/ png-0/ < /dev/null > dlowe-aux-data/png-trained.net
-
dlowe-aux-data/png-0/ Non-png (gif) images
-
dlowe-aux-data/png-1/ png (non-gif) images
We created the xor-trained.net as follows:
./dlowe -8000 dlowe-aux-data/xor-1/ dlowe-aux-data/xor-0/ < /dev/null > dlowe-aux-data/xor-trained.net
-
dlowe-aux-data/xor-0 Data that XORs to 0
-
dlowe-aux-data/xor-1/ Data that XORs to 1
NOTE: The directory args must end in a / for them to work.
Author's remarks:
Synopsis
This is an artificially intelligent judging tool to help the IOCCC judges. Here's to shorter, more frequent contests!
Description
This is a multilayer perceptron (a feedforward artificial neural network) which can be trained, using on-line backpropagation, to classify input files.
It has a fixed topology of 2^16 input neurons, 6 hidden neurons and 1 output
neuron.
The neurons' activation function is the logistic function 1 / (1 + e ^ -x).
Classifying
./dlowe file [file ...] < trained.net
To classify files, one specifies a trained network (on stdin) and one or more
files to classify. The program will output one line per successfully-classified
file to stderr, with the filename and the classification: a number between 0
and 1.
The interpretation of the classification number depends on how the network was trained, but it's geared toward interpretation as a probability or a confidence.
Training
./dlowe -<n_iterations> corpus1/ [...] corpus0/ < start.net > end.net
NOTE: The directory args must end in a / for them to work.
To train a network, one specifies a starting network (on stdin), two or more
corpora (directories containing training data), and the number of training
iterations to run. The program will write some progress data to stderr and,
when it's done, will serialize the updated network to stdout.
If no input network is given, a random new network will be generated as a
starting point (i.e. provide an empty stdin).
The first corpus will be assigned a target value of 1. The last will be
assigned a target value of 0. Intervening directories (if any) will be assigned
intermediate target values.
The learning rate is hard-coded as 0.3. No momentum factor is used.
png corpora
The png-1 corpus was obtained by manually scraping the first results from an https://images.google.com search for "obfuscate filetype:png".
The png-0 corpus was obtained by manually scraping the first results from an https://images.google.com search for "obfuscate filetype:gif".
Results:
- Using these corpora as a training set;
- Using several hundred random
*.gifand*.pngfiles from my home computer as a test set; - Using the included earlystop.pl script, which stopped after 67000 iterations.
- Interpreting output of
> 0.5as "probably a.png" and< 0.5as "probably a.gif"
produced a network with about 87% accuracy
English corpora
The english-1 corpus was obtained by manually scraping the first results from a https://www.google.com/webhp?lr=lang_en search for "paris filetype:txt".
The english-0 corpus was obtained by manually scraping the first results from a https://www.google.com/webhp?lr=lang_fr search for "paris filetype:txt".
Results:
- Using these corpora as a training set;
- Using several dozen additional text files (obtained by the same methods) as a test set;
- Using the included earlystop.pl script, which stopped after 10000 iterations;
- Interpreting output of
> 0.5as "probably English" and< 0.5as "probably French"
produced a network with 100% accuracy.
xor corpora
The xor-1 corpus consists of two files containing 01
and 10 respectively.
The xor-0 corpus consists of two files containing 00
and 11 respectively.
Results:
Using these corpora as a training set takes about 8000 iterations to learn xor
to within a tolerance of <0.01.
Limitations
The program can't tell you anything meaningful about files with less than two bytes in them (I'm looking at you, smr.c!)
You must include the trailing directory separator on training directories (this allows the program to be portable without wasting precious bytes on figuring out how to concatenate directory and file names...).
Serialized network files are only portable between systems with the same floating-point representation and endianness.
Making sure not to overfit the network to the training data is a bit of a black art. I have enclosed earlystop.pl, a wrapper script that implements a simple 'early stopping' algorithm; other techniques are possible.
Bad input (e.g. nonexistent files, non-numeric number of iterations, etc.) tends to result in empty output.
Given exactly one corpus, the program will crash or produce garbage.
Leaks memory and file descriptors while processing files.
Will crash and die horribly if it runs out of memory.
The Microsoft C compiler doesn't provide a dirent API, so to get this working
on a Windows system you'll need cygwin+gcc (tested) or a dirent compatibility
library (untested, but they do exist).
Backpropagation doesn't always converge: if you play with this long enough, you'll eventually have a training session that completely fails to converge.
Obfuscation
- Zombies! (Since neural networks are modeled after BRAINS, ya know? And corpus sounds a lot like corpse. And I have 4- and 7-year-old kids ;) )
- Neural networks are interesting, and while the math isn't terribly difficult, their behavior is difficult to fully understand.
- Had some extra space in one of the major data structures, and it seemed a shame to waste it.
- Similarly, I think three file pointers ought to be enough for anyone.
- Lots of magic numbers expressed in various ways.
- Random abuse of random C trivia.
- Some textual changes were made to maximize the classification of this program by a network trained to recognize IOCCC winners ;)
... but mostly zombies!
Copyright and CC BY-SA 4.0 License:
This file is Copyright (c) 2023 by Landon Curt Noll. All Rights Reserved. You are free to share and adapt this file under the terms of this license:
Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
For more information, see: https://creativecommons.org/licenses/by-sa/4.0/