Parser Stats automatically and incrementally reported with each parse
A parser reads text to discover structure and meaning. For example, a C language parser can read a C program and understand in a real sense everything that the program has to say. Contrast this to a pattern matcher...
Parser generators have traditionally been used to describe exactly what should be written and anything else is a "syntax error". Wiki allows writers to write what they think makes sense. With Exploratory Parsing we now have a way for the parser writer to discover what has been written after the fact.
> This Inversion of Control mirrors the original thinking behind wiki. Let those who know write as they see fit. Trust people to be regular enough to create lasting value. Use the power of our modern computers and networks to organize that value. github
See blog post announcing the open-sourcing of this technology. github ![]()
YOUTUBE HCmrVp8WR6c SAO's video of Ward's performance
This was a web based experiment manager that could prepare, monitor, and refine task specific grammars turned into engines with a slightly enhanced version of Ian Piumarta's peg/leg. site ![]()
Developed sediment inspired uniform sampling algorithm. Add elements at period p until sediment reaches limit. Then decimate the sediment by 1/2 and 2x the period. github ![]()
See related Reservoir Sampling which is happy to be uniformly random but not evenly spaced. wikipedia ![]()
My approach here was informed by my positive experience with XML Import in Ruby.
~