Feature targeted verbosity
It would be useful to have verbosity tied to features instead of verbosity levels.
Proposal: FeatureEnum and special option class which stores all feature which have been requested to print. Some features might then be aggregates of a set of features.
Comments (12)
-
reporter -
reporter Errors, verbosity, timing
Updated solver Refs
#102: Added a new set option, which contains a set of characters notifying which verbosity we are interested in.Refactored the warnings and removed the printing of the first error, only done when there are lots. TODO might become when there is lot of output.
Refs #183: Tried to add timing of the grounding of a sentence, but was problematic because a grounder does no really know whether he is a toplevel sentence => what is the correct granularity?
-
Prepared the feature-targetted options, see
#102Prepared the 'Options' class for a new kind of option: an optionOption That is: an option that is in fact an optionsblock. For example, you can now write stdoptions.verbosity.creategrounders=true
TODO: adapt the rest of the system to work with this.
→ Wiki macro error: Changeset efc4ed7f8cb6 not found.
-
Prepared the feature-targetted options, see
#102Prepared the 'Options' class for a new kind of option: an optionOption That is: an option that is in fact an optionsblock. For example, you can now write stdoptions.verbosity.creategrounders=true
TODO: adapt the rest of the system to work with this.
→ Wiki macro error: Changeset f8220ae5eb5e not found.
-
Prepared the feature-targetted options, see
#102Prepared the 'Options' class for a new kind of option: an optionOption That is: an option that is in fact an optionsblock. For example, you can now write stdoptions.verbosity.creategrounders=true
TODO: adapt the rest of the system to work with this.
→ Wiki macro error: Changeset f8220ae5eb5e not found.
-
- changed status to resolved
Moved the groundverbosity method to the grounder
It used to be in globaldata, but the groundverbosity is now local to the grounders. Also abstractgroundtheory now contains a proper method to get the right verbosity. Doing this, every occurence of "Groundverbosity" has been replaced. Hence I also removed the groundverbosity option. This fixes
#102. However, see #167, these changes have not been documented.→ Wiki macro error: Changeset b02185d5c495 not found.
-
Prepared the feature-targetted options, see
#102Prepared the 'Options' class for a new kind of option: an optionOption That is: an option that is in fact an optionsblock. For example, you can now write stdoptions.verbosity.creategrounders=true
TODO: adapt the rest of the system to work with this.
-
It used to be in globaldata, but the groundverbosity is now local to the grounders. Also abstractgroundtheory now contains a proper method to get the right verbosity. Doing this, every occurence of "Groundverbosity" has been replaced. Hence I also removed the groundverbosity option. This fixes
#102. However, see #167, these changes have not been documented.→ Wiki macro error: Changeset 4c4bb2dbc1cc not found.
-
Moved verbosity() method to local to grounders and mx
It used to be in globaldata, but the groundverbosity is now local to the grounders. Also abstractgroundtheory now contains a proper method to get the right verbosity. Doing this, every occurence of "Groundverbosity" has been replaced. Hence I also removed the groundverbosity option. This fixes
#102. However, see #167, these changes have not been documented. -
Prepared the feature-targetted options, see
#102Prepared the 'Options' class for a new kind of option: an optionOption That is: an option that is in fact an optionsblock. For example, you can now write stdoptions.verbosity.creategrounders=true
TODO: adapt the rest of the system to work with this.
-
Moved verbosity() method to local to grounders and mx
It used to be in globaldata, but the groundverbosity is now local to the grounders. Also abstractgroundtheory now contains a proper method to get the right verbosity. Doing this, every occurence of "Groundverbosity" has been replaced. Hence I also removed the groundverbosity option. This fixes
#102. However, see #167, these changes have not been documented. -
reporter - removed milestone
Removing milestone: Later (automated comment)
- Log in to comment
Errors, verbosity, timing
Updated solver Refs
#102: Added a new set option, which contains a set of characters notifying which verbosity we are interested in.Refactored the warnings and removed the printing of the first error, only done when there are lots. TODO might become when there is lot of output.
Refs #183: Tried to add timing of the grounding of a sentence, but was problematic because a grounder does no really know whether he is a toplevel sentence => what is the correct granularity?
→ aca25f44f36f