Issues:
- how to introduce fast scan and slow scan axes in the psana geometry format?
- how to make the psana geometry format complete (incorporate some geometry information inside the psana code)?
| Proposal | Arguments In Favor | Argument Against |
|---|---|---|
| Use NeXus format | Complete | Hdf5 format is inconvenient for mongoDB, very verbose, only cctbx people use it |
| Use CrystFEL format | Uses fs/ss, many users, Geoptimizer available | No hierarchy, does not account for mixed pixel sizes, does not handle z-offset from optical metrology, non-geometry related fields are included in the geometry file |
| Keep using the same psana geometry format (unless we have a big gain) | keep the number of formats to 3. less work in implementing a new format | No fs/ss axes that users want. Incomplete information. |
Overview
Content Tools