Would be nice if the event builder .ini objects were stored in the same DB as the reader .ini objects. A reader .ini object would then link an event builder .ini file that should be used for that data by writing the name of the .ini doc to the run['trigger']['mode'] field. The same will hopefully be done for the data processor.
Right now reader .ini files are in online.run_modes. Trigger ones could go in online.trigger_modes or something like that.
Just a wishlist thing for unification of these parts, so no hurry on this.
Would be nice if the event builder .ini objects were stored in the same DB as the reader .ini objects. A reader .ini object would then link an event builder .ini file that should be used for that data by writing the name of the .ini doc to the run['trigger']['mode'] field. The same will hopefully be done for the data processor.
Right now reader .ini files are in online.run_modes. Trigger ones could go in online.trigger_modes or something like that.
Just a wishlist thing for unification of these parts, so no hurry on this.