| Proposal | Arguments In Favor | Argument Against |
|---|---|---|
| Data shall be accessible with a syntax like evt.xppcspad.attr1.attr2 | allows for easy exploration of the contents of an event | |
| All attributes must exist on every event, with the lowest-level attribute returning None if the data is not accessible for any reason (e.g. missing detector, missing raw data, missing calibration constants) | makes user code simpler to check for missing information | computationally expensive to add all attributes when data is not present |
| No functions allowed. Configurable parameters (e.g. common-mode params) will be set with other attributes | ease-of-use in AMI | artificial constraint on use of python |
| All attributes should be discoverable on the Configure transition | ease-of-use in AMI | |
Overview
Content Tools