Versions Compared

Old Version 50

changes.mady.by.user Christopher O'Grady

Saved on

compared with

New Version 51

changes.mady.by.user Unknown User (davidsch)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

There are a number of specialized options in psana that we do not generally document in the main user documentation. These are options that engineers or , points of contact (POC's), or possibly users may need to deal with special circumstances. We document these here - package.module.optionThese are described in the table below:

package.module.option or psana.optiondata typeoption description
PSXtcInput.XtcInputModule.liveTimeoutintegerlive time out in seconds run running in live mode
psana.first_control_streamintegerwhich stream starts the control or IOC streams (xtcav, etc) defaults to 80
psana.l3t-accept-onlyboolwhen true, checks for trimmed datagrams. If the datagram is trimmed, it does not trigger an event for the user. Trimmed datagrams should be empty. There was a case where trimming was not set up properly, and we needed to turn this off to see the data. Note - this is different then the l3t pass/fail that users POC's may setup - though one does not expect trimmed data unless the l3t is a fail.
psana.allow-corrupt-epicsboolfor data from before approximately July 2014 when the DAQ epics archiver recorded different variables at different rates, the index files do not contain enough information to properly get access the correct epics values. When this happens, and the user is running in index mode, psana will exit with a fatal error. Setting this flag to True will allow psana to analyze these runs (in index mode) but some of the epics data could be corrupted.

...