cet-is » art

There have been requests for features like the following:

1. name the disk file based on a pattern specified in the configuration file, and allow the pattern to include fields such as the current run number, the current subrun number, and a timestamp.
2. allow users to specify a maximum file size or a maximum number of events per file or a maximum amount of time for a file to be open. The idea here would be that after the configurable size or number of events or amount of time, the current file would be closed and a new one opened, and new events would be written to the new file.
3. after a file is successfully closed, move it to a different (configurable) directory

In all of these cases, I think that it would be useful to discuss the needs and the available options a bit more. For example, in the case of the second request, it may be more robust to have the System Control application send Pause & Resume commands at the appropriate times to get the files to have the correct size, number of events, or time range.

For the first request, it would be good to discuss the patterns that would need to be supported and how they would be specified.
--Kurt

Here is a note from Jim on the first request:

• This is experiment-specific configuration. A proposal that is more detailed is needed here - one that includes an example art fhicl configuration fragment that would specify the name. An alternative to changing fundamental behavior for naming conventions would be to use an experiment-specific service that renames the files to an appropriate name when a "file closed" event is generated within art.

And, here is a note from Jim on the third request:

• An experiment-specific art service may be able to easily be used for this using the existing APIs.