Decide to keep or discard _i[x] tag in certain files

[Juergen Reuter]

They are there in the process code and in the phs file (at the moment), but not in the VAMP grids. This has to be decided and unified (and explained to me, what is behind it!!!), and pretty soon. This at the moment endangers the beta release on Wednesday!

[kilian]

The file suffixes are as intended. I think we discussed this in a previous meeting.

Each process consists of several components (matrix elements), which are distinguished by the iXXX suffix. This suffix is applied to all files _except_ the grids. For integration, several components are collected in MCI groups. There should be a MCI group suffix for the grid files, but this is not implemented yet.

In practice, all processes so far have a single MCI group and a single component. However, Christian's subtraction terms (not in the trunk yet) already use multiple components.

In addition to the component or MCI suffix, each file should get a run-ID suffix, if there is one. This is also not implemented yet. Did anybody use this in 2.1?

[Juergen Reuter]

Ok, understood. That means that the construction for the run IDs for the phs files cannot be as simple as for the grid files. Instead, I need to channel the run IDs to the phs_wood_config structure. Will do that. (same for the log files).

[kilian]

Yes, d'accord. The run ID should be straightforward to access as a member of the process_metadata (IIRC) structure.

Event files should not use run IDs, just the $sample name.

[Juergen Reuter]

Found a working solution which is pretty simple. So this was only a decision ticket. Reconciliation between run IDs and process (component) IDs is achieved in r5072. Closing.