…t can be used with Exago.
…lly file by file depending on the input being acquired. The idea is that if you have a large set of files, you should use a file splitter as its more efficient, and if you are dealing with a dynamic stream of some kind, use an event splitter as its not known when the eos will occur.
…d so that it could interact with the splitter apropriately.
…xtended and used for the main analysis soon, to replace having to check data against the state machine model, with checking statistics against it, and optionally data.
…The idea is to turn the system into a demand driven one, and this is aimed towards achieving that goal. At the moment it supports reading of files only, and is not integrated within the wider system.
…hat a custom file parser should have in order to conform with the rest of the system. This allows the transparent replacement of file parsers to still work with the systems underlying field types.
…string, the implementation so far relies on a positional list. It was done this way to intentionally give as much flexibility as possible to the user when parsing date fields. We want to be able to cater for dates that dont contain microseconds, or any other time unit.
…system that Exago will make use of. The reason this augmentation is needed is so that we have a well defined type protocol to go by in the future, and so that we can easily extend the functionality that is already available. This will make it trivial to add new types of values and parsers.
…place the current exago_field.
…claration to not compile)
…me work to be done in this area.
… least it exists now.
…rom some lingering identifiers that have been badly named (Transaction for describing a set of events ...).
… generate a report with this configuration.