AS was implemented historically in hextof-processor, it was requested to make a class method in the processor which prints a description of relevant and statistical information about the runs loaded. Some examples are:
- number of pulses
- number of electron counts
- electrons/pulse electrons/second
- loaded channels
- start and end time of the acquisition
- run number(s)
Some of this metadata can be infered (in the case of FLASH) from the intermediate parquets. These should be gathered and made available not only in the loader but as part of the metadata in the processor instance.
Ohter data which needs to read the numbers could be computed in the dataframe generation step. This needs more thought though...
Moreover, this can be generalized to any system if the method searches for the metadata available to print, and based on what is implemented, different systems will report different information.
At FLASH, Some information might be also gathered from SciCat.
AS was implemented historically in hextof-processor, it was requested to make a class method in the processor which prints a description of relevant and statistical information about the runs loaded. Some examples are:
Some of this metadata can be infered (in the case of FLASH) from the intermediate parquets. These should be gathered and made available not only in the loader but as part of the metadata in the processor instance.
Ohter data which needs to read the numbers could be computed in the dataframe generation step. This needs more thought though...
Moreover, this can be generalized to any system if the method searches for the metadata available to print, and based on what is implemented, different systems will report different information.
At FLASH, Some information might be also gathered from SciCat.