Short term fix is to always supply -f option

Several options would be best:

• local working directory
• environment variable
• location determined at time of Make
• location of binary/../cfg/

• Remove experiment-specific stuff left over in runinfo
• Use dynamic arrays and maps to define a list of required fields for each run
  • Only require fields when RawWriter is enabled
  • Possibly allow array fields of some type as well
• At run start (if RawWriter enabled) prompt user for any missing required fields with a pop-up window
  • Allow specification of drop-down lists for enum-type fields
  • Allow specification and prompting for optional fields
• Provide syntax to specify system command to be executed at run start and end (for database insertion, e.g.)

In order to minimize frequency of disk access, add a parameter to RawWriter so that it will buffer some N events in between each actual disk write.

Make sure to account for max file size and n events, and to save any remaining buffered events on Finalize

Some of the modules that are included by default are either very specific to a given analysis, or require additional data files to work properly, or are just plain broken. Potential fixes:

• Only register the basic common modules useful to any project
• Make the problematic modules disabled by default
• Make all modules disabled by default, so you have to explicitly enable them in your config file
• Use some sort of factory to register the modules directly in the config file (bleh...)

• vector. Syntax: [ item1 , item2 , item3 ] .
• set. Same syntax as vector
• map. Syntax: { key : value , key : value , key : value }
• append syntax: prefix opening with '+' for any style
• Make sure that vector and map interfaces are JSON compatible

Questions?

• Should we also allow enclosing () rather than [] ? Or should we enforce that () encloses fully pre-defined entities like ParameterLists, while [] enclose dynamic entities?
• Should we require separating commas between elements?
• Should we require the separating colon between key value pairs in maps?
• Should we keep ParameterLists as they are, or switch them to use the underlying map functions?

The default config files daqman.cfg genroot.cfg and daqview.cfg are all broken, so that users need to always give --no-cfg on first running. The default files in the config directory should be replaced with functional ones or the output of --show-parameters.

Or figure out how to call the default ROOT initialization defined in .rootrc