* Generation with modified simulation inputs

• some information is in the native gSeaGen file, how to store in the data format
  • some are not in the gSeaGen structure
    • tau polarisation: storing the vector
    • tau decay channel (see effective volume discussion)
  • new gSeaGen has a tool to convert from native to km3net dataformat
    • not the genie format, the gSeaGen one. The genie format can be output of the processing with specific option. If one wants more info, the gSeaGen class for writing files should be expanded.
  • genie systematics: written in the native genie file
    • an interface is present in gSeaGen. Systematics for individual parameters (out of a list) can be stored.
    • how to write in dataformat.
    • inputs needed from Oscillation Working Group.
• original configuration file maintained then different versions for each tune.
  • Q: The configuration file is passed via a path: in a container, how does this work?
    • it can be re-defined in own directories.
  • All cross sections (physically or symbolic link - <tune_name>.xml) in the same location, so that it can be used directly. Just one name per tune. This works if all configuration files are OK for all the tunes.
    • Otherwise: not define the variables in the container but in the data_processing https://git.km3net.de/common/data_processing/-/issues/113
    • this will depend on what we actually want to do. e.g. different energy ranges.
    • will clear situation e.g. for low-energy tune used in mass production
  • Decay mode in new container to be tested. Understand what can also go into mass production.
    • Note: UnstableParticleDecayer.xml in the new genie version is in a new file

* Cross sections

• both differential and total cross sections are stored in gSeaGen. with (X,Y) one could reweight
• genie systematics (see above)