...

For Epics variables we need two names: the complex epics variables name (e.g. HX2:DVD:GCC:01:PMON) and a simple user alias e.g. STAGE_POSITION.  Mona currently allows variables in the epics-store to have illegal python names (i.e. with ":" in them).  This is different than other detector names.

Proposal:

• the DAQ reads epixArchepicsArch.txt.  it can use either the epics name or the alias as the detname in xtc2.  This keeps things "natural" in xtc2, where each detector has one and only one user name.  
• the DAQ optionally stores an extra epics_info object in the configure transition.  this single object would contain ancillary information about each epics variable, e.g.
  • the full epics name
  • the alias name (defaults to the full name if not specified in epicsArch.txt)
  • description of the epics variable
• the epics_info object would have its own Detector interface
• the epics_info object (and Detector interface) could expand over time, presumably in a backwardly-compatible way by using the usual middle-version-number increment patternfor PvaDetector Ric uses a user-specified detName, and the full epics name is not persisted in the data.  But in the future it could be persisted using the above epics_info mechanism..  Might be easiest if new fields for each variable were added to the end of the struct
• in epicsArch right now, Ric/Matt now use the epics variable name (was "value" previously) and ignores the alias.  Ideally this would change to use the Alias alias if it existed in epicsArch.txt.right now Ric passes the alias as the .cnf "id" (e.g. tmomanta_0).
  • probably needs a command-line argument to support both an andor/manta in one pva
• we should try to make the DetType more generic (not "manta" but maybe "pv")
• all PvaDetectors in one segment level (e.g. andor/manta) need to be in the same readout group
  • not certain about this.  ask Matt.  maybe we could have one segment sign up for multiple lanes, each on a different readout group?
  • in control_gui have to assign one segment level to a readout group.  is this cast in stone, or can it be changed?
• PvaDetector two options for supporting multiple pv's within one segment level:
• all epics variables (e.g. manta, Andor) within one PvaDetector.  if so:
  
  • if a detector is missing on a particular shot we should throw out all
(preferred) each epics variable has its own detector (similar to raw/fex) e.g. tmomanta/tmoandor (probably both have DataType "raw")this could tolerate individual missing detectors

Area Detector Brainstorming (AreaDetector)

...