The current .nxs files contain the EPICS putlog as a string-typed selog entry.
We need to decide how to pipe this data through to the filewriter.
Questions
The ISISICP currently writes strings in a way that is not nexus-compliant. Do we want to continue to do that?
There is a new NXtextlog class for storing string-logs: nexusformat/definitions#1590
Potential differences from existing files
- Some of the PV names (particularly the DAE PVs) will be different in the datastreaming system, and may not be captured in the CA putlog as they are served over PVA instead. For example if downstream analysis is expecting to be able to parse strings like
Changed PV: IN:SANS2D:DAE:BEGINRUNEX new=0 old=0 from this log, then that would no longer be valid.
The current
.nxsfiles contain the EPICS putlog as a string-typedselogentry.We need to decide how to pipe this data through to the filewriter.
Questions
The ISISICP currently writes strings in a way that is not nexus-compliant. Do we want to continue to do that?
There is a new NXtextlog class for storing string-logs: nexusformat/definitions#1590
Potential differences from existing files
Changed PV: IN:SANS2D:DAE:BEGINRUNEX new=0 old=0from this log, then that would no longer be valid.