Need jobfiles to define how to process items and where the profiles are

Bug #482407 reported by Michael Wayne Goodman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Egad
Fix Committed
High
Michael Wayne Goodman

Bug Description

Rather than just providing command-line arguments to Egad, it would be nice to define a jobfile, then just use that as the single argument. This way, we could easily set up multiple jobs for the same grammar settings, define what features to use, etc.

For example

<?xml version="1.0" encoding="UTF-8"?>
<EgadJob jobtype="tsdb">
  <Grammar location="/dir/to/grammar" lexical_substitution="True" use_ignore_symbols="True" />
  <IgnoreSymbols symbol_list="!?.*^%" />
  <Job name="first job" ngram_length=4>
    <ParsingProfile location="/dir/to/parse/profile" />
    <GenerationProfile location="/dir/to/gen/profile" />
  </Job>
</EgadJob>

Changed in egad:
milestone: none → 0.2.x
importance: Undecided → High
assignee: nobody → Michael Wayne Goodman (goodmami)
Revision history for this message
Michael Wayne Goodman (goodmami) wrote :

Not all described features are accounted for, but support for this this is checked into r7 or r8.

Changed in egad:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.