Page History
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
NEW | WHERE IT WAS IN OLD SCHEMA OR NOTES
----------------------------------------+---------------------------------------------------------
/Data
/Data/EpicsConfig
/Data/EpicsConfig/BEAM:LCLS:ELEC:Q /Configure:0000/Epics::EpicsPv/EpicsArch.0:NoDevice.0/BEAM:LCLS:ELEC:Q
/Data/EpicsConfig/Attenuator_transmission /Configure:0000/Epics::EpicsPv/EpicsArch.0:NoDevice.0/Attenuator_transmission
/Data/Config
/Data/Config/Control * a standard source name, not an alias *
/Data/Config/Control/AliasConfig /Configure:0000/Alias::ConfigV1/Control
/Data/Config/Control/ControlDataConfig /Configure:0000/ControlData::ConfigV3/Control
/Data/Config/Control/EvrIOConfig /Configure:0000/EvrData::IOConfigV2/Control
/Data/Config/Control/PartitionConfig /Configure:0000/Partition::ConfigV1/Control
/Data/Config/EBeam * a standard source name, not an alias *
/Data/Config/EBeam/BldDataEBeam /Configure:0000/Bld::BldDataEBeamV7/EBeam
/Data/Config/Opal_1 * this is a Daq Alias for XppEndstation.0:Opal1000.1 *
/Data/Config/Opal_1/TimeToolConfig /Configure:0000/TimeTool::ConfigV2/XppEndstation.0:Opal1000.1
/Data/Config/Opal_1/FrameFexConfig /Configure:0000/Camera::FrameFexConfigV1/XppEndstation.0:Opal1000.1
/Data/Config/Opal_1/Opal1kConfig /Configure:0000/Opal1k::ConfigV1/XppEndstation.0:Opal1000.1
/Data/Config/cs140_0 * also an alias *
/Data/Config/cs140_0/CsPad2x2Config /Configure:0000/CsPad2x2::ConfigV2/XppGon.0:Cspad2x2.0
/Data/Config/evr0 * alias *
/Data/Config/evr0/EvrConfig /Configure:0000/EvrData::ConfigV7/NoDetector.0:Evr.0
/Data/Config/evr1 * alias *
/Data/Config/evr1/EvrConfig /Configure:0000/EvrData::ConfigV7/NoDetector.0:Evr.1
/Data/Config/MyTimeToolConfig * special alias from user, soft link to Opal_1/TimeToolConfig
/Data/Config/NH2-SB1-IPM-01/IpimbConfig /Configure:0000/Ipimb::ConfigV2/NH2-SB1-IPM-01
/Data/Config/NH2-SB1-IPM-01/IpmFexConfig /Configure:0000/Lusi::IpmFexConfigV2/NH2-SB1-IPM-01
/Data/Config/XppEnds_Ipm0/IpimbConfig /Configure:0000/Ipimb::ConfigV2/XppEnds_Ipm0
/Data/Config/XppEnds_Ipm0/IpmFexConfig /Configure:0000/Lusi::IpmFexConfigV2/XppEnds_Ipm0
/Data/Config/Event/L3TConfig /Configure:0000/L3T::ConfigV1/Event
/Data/Run
/Data/Run/Config
/Data/Run/Config/noSrc/mykey # if a user did configStore().put(myndarray, 'mykey') during beginrun
/Data/Run/Config/Opal_1/mykey # likewise, if a user did configStore().put(mystring, psana.Source('Opal_1'),'mykey')
/Data/Run/EndData/noSrc/summary # if a user did configStore().put(myndarray, 'summary') during endrun
/Data/Run/EndData/Opal_1/summary # if a user did configStore().put(myndarray, 'summary') during endrun
# HERE IS WHERE REGULAR EVENT DATA IS
/Data/Run/Step:0000 /Configure:0000/Run:0000/CalibCycle:0000
/Data/Run/Step:0000/Config
/Data/Run/Step:0000/Config/noSrc
/Data/Run/Step:0000/Config/noSrc/myKeyString # if user adding something to configStore during begincalibcycle
/Data/Run/Step:0000/Epics
/Data/Run/Step:0000/Epics/pvName
/Data/Run/Step:0000/EBeam/BldDataEbeam
/Data/Run/Step:0000/Opal_1/CameraFrame
/Data/Run/Step:0000/Opal_1/TimeToolData
/Data/Run/Step:0000/MyTimeToolData {soft link to above}
/Data/Run/Step:0000/cs140_0
/Data/Run/Step:0000/cs140_0/CsPadElement
/Data/Run/Step:0000/cs140_0/radialIntegration # a user module ndarray attached to a source
/Data/Run/Step:0000/evr0
/Data/Run/Step:0000/evr1
/Data/Run/Step:0000/evr0/EvrData
/Data/Run/Step:0000/evr1/EvrData
/Data/Run/Step:0000/noSrc/mykey # a user module ndarray not attached to a source
/Data/Run/Step:0000/NH2-SB1-IPM-01/IpimbData
/Data/Run/Step:0000/NH2-SB1-IPM-01/IpmFex
/Data/Run/Step:0000/EndData
/Data/Run/Step:0000/EndData/noSrc/myKeyString
/Data/Run/Step:0000/EndData/opal_1/myKeyString
/Data/CalibStore
same as before, but invert type/source, and use DAQ aliases |
Feedback
Here is some feedback I have gotten.
Keep hiearchy close to EventKeys
Simplifying the hiearchy too much could be confusing, keeping closer to what one sees with psana EventKeys is helpful
Original Sources are Useful
Just having the DAQ aliases may not be good, One could put both the DAQ alias and native source in the name, or have them side by side, one a link, or keep aliases separate from original native source names, in different groups.
compound types vs. Basic Types
Use basic types in place of compound types.
Flattened Input
A tool to gather up, and event build the particluar data a user is intereted in. This may be a few fields from EBeam, a particular EPICS PV, links to camera images.
Overview
Content Tools