about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* Fixed a few minor compile errors in freevarsFeffernoose2013-10-072-1/+2
|
* Implemented freevarsFeffernoose2013-10-075-4/+82
| | | | Arbitrary variable tokens can now be defined (though at this point only in the code itself) as a pair of a variable name and a filename pointing to a plain text file containing a newline-delimited list of elements. When a token of the form $name$ (where name is the name of a variable) is encountered, the output will include a random element from the appropriate list. The variables $name$ and $noun$ are hard-coded at this point, but the program will not crash if names.txt and nouns.txt do not exist and will instead just silently ignore the variables.
* Removed yamlcpp dependency from rawr-genFeffernoose2013-10-063-15/+28
| | | | rawr-gen now takes the input corpus as a command-line argument, so as to increase the ease-of-use. It also now shows a usage message if provided with a non-existent file or no argument.
* Merge branch 'master' of http://github.com/hatkirby/rawr-ebooksFeffernoose2013-10-061-2/+8
|\
| * Merge branch 'master' of https://github.com/hatkirby/rawr-ebooksFeffernoose2013-10-061-11/+11
| |\
| * | Stripped empty tokens from corpusFeffernoose2013-10-061-2/+8
| | |
* | | Split rawr-ebooks and rawr-genFeffernoose2013-10-064-7/+94
| |/ |/| | | | | Also wrote README
* | Program no longer recalculates kgramstats repeatedly within each runFeffernoose2013-10-051-11/+11
|/
* Rewrote weighted random number generatorFeffernoose2013-10-052-34/+39
| | | | | | The previous method of picking which token was the next one was flawed in some mysterious way that ended up picking various words that occurred only once in the input corpus as the first word of the generated output (most notably, "hysterically," "Anarchy," "Yorkshire," and "impunity.").
* Changed incidence of random kgram-trimmingFeffernoose2013-10-041-4/+10
| | | | Also added better terminal output
* Weighed token casing and presence of periodsFeffernoose2013-10-012-28/+76
| | | | | | | | Tokens which differ only by casing or the presence of an ending period are now considered the same token. When tokens are generated, they are cased based on the prevalence of Upper/Title/Lower casing of the token in the input corpus, and similarly, a period is added to the end of the word based on how often the same token was ended with a period in the input corpus.
* Wrote programFeffernoose2013-10-016-1/+336
|
* Started automake stuffFeffernoose2013-09-304-0/+38
|
* Initial commitKelly Rauchenberger2013-09-303-0/+356