...

• binVar_bins: bin edges as defined in the config or the default (unique) motor positions. In the latter case, the first value is NaN, as a bin is manually added to catch outliers on the left for the general case.
• nEntries: number of shots in each bin
• binVar: sum of the binned variable. When binning linearly, binVar/nEntries should return the most accurate position. A field with the binned variable name contains the same information.
• All the binned variables defined in varList: for . These entries are the sum of all data falling in the corresponding bin. For the regular detectors (non-area detectors) the syntax follow that of the varList, where "/" have been replaced by "__" (two underscores). Binned area detectors images or calib are under <detname>_data. A <detname>_nEntries field should match the nEntries field. If not, contact your controls and data PoC.
  Example from the config file above:
  • ipm2__sum
  • ipm3__sum
  • diodeU__channels
  • jungfrau1M_data
  • jungfrau1M_nEntries
• <detname>_cfg: a config group for each area detector that contains the detector config (pedestals, gain map, mask, etc.)

...

Please don't modify this file directly, copy it to your home or experiment area to test and explore.

Debug the cube production

...

1. Check that the filters do not filter out all the pulses. In the current state, if all shots are being filtered, the job will just hang forever. This can easily spotted by looking for the following section in the log file:

2. 
   

   Code Block
   language bash theme RDark
   did not select any event, quit now! getFilter: Cut 0.500000 < evr/code_94 < 1.500000 passes 0 events of 11252, total passes up to now: 0 getFilter: Cut 24.464119 < scan/diag_x < 24.496000 passes 11252 events of 11252, total passes up to now: 0 getFilter: Cut 0.500000 < damage/jungfrau1M < 1.500000 passes 11252 events of 11252, total passes up to now: 0

   
   

3. The MPI error handling is not yet in a very good state. If one of the rank fails (often rank 0), the other rank will still be hanging there, waiting for further tasks. The will this hang forever. In this, a traceback of the error will be available towards the end of the log file (it is not always at the very end). It typically can be identified by a line looking like:

   Code Block
   language bash theme RDark
   Traceback (most recent call last): ...

   
   

Notes on the multi-dimensional cube

...