Difference: PVNamingConventions (1 vs. 7)

Revision 7
10 Jan 2018 - Main.PeterZumbruch
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Changed:
<
<

PANDA PV Naming Conventions

>
>

PANDA PV Naming Conventions

 
Changed:
<
<
The naming convention for PANDA slow control process variables is outlined below. We recommend implementing these rules early, to avoid later confusion.
>
>
The naming conventions for PANDA slow control process variables are outlined in this wiki. We recommend adopting these rules early on, to avoid confusion later and simplify integration of the various subsytems and LabVIEW/EPICS connectivity.
 

Changed:
<
<
... to be discussed ...
>
>

PV Basics

 
Changed:
<
<

preface and basics

>
>
Process Variables (PV) are the values monitored and/or controlled via the slow controls system.
 
Changed:
<
<
In view of the use of EPICS as major control system for PANDA those basic rules have to been followed
>
>
For PANDA Process Variables these basic rules should be followed:
 
Changed:
<
<
  • maximum 63 characters, recommended maximum 40 (to comply with (old) EPICS standards)
  • forbidden:
    • blanks: " ",
    • periods "." (used as attribute delimiter)
    • local special letters, Umlaute "üØ, ..." , Accents "è, ..." (possible but forbidden by this convention)
  • Logical separation by colon ":"
  • case sensitive
>
>
  • A PV name should contain maximum 63 characters, recommended maximum 40 (to comply with older EPICS standards)
  • A PV name should not contain:
    • blanks or tabs (" "),
    • periods (".") (they are used as attribute delimiter)
    • special characters (Umlaute: "ü, Ø, ..." , Accents: "è, ...")
  • Colon (":") should be used as logical delimiter
  • The PV names are case sensitive
  • The PV name must start with "PANDA:"
 
Changed:
<
<

convention

>
>

PV Name Template

 
Changed:
<
<
In one line
<Experiment specifier>:<Detector Sub System>:<optional Device specification>:<Signal Type>:<Segmentation coordinates>:<Channel number>:<Value/Task>
>
>
In one line:
<Experiment specifier>:<Detector Sub System>:<optional Device specification>:<Signal Type>:<Segmentation coordinates>:<Channel number>:<Value/Task>
 
Changed:
<
<
Giving first an example might help
PANDA:EMC:APD:HV:S1:M4:TR4:L8:C40:Imon
which would be the monitor value of channel 40 of the current of the High voltage of an APD of the EMC in sector 1, module 4, tray 4, layer 8.
>
>

Example

 

Changed:
<
<

In detail

  • The colon ":" separates the hierarchy levels

... the levels from left to right are:
>
>
For example one could have:
PANDA:EMC:APD:HV:S1:M4:TR4:L8:C40:Imon
which would be the monitored value of channel 40 of the current of the High voltage of an APD of the EMC in sector 1, module 4, tray 4, layer 8.
 
Added:
>
>
The colon ":" separates hierarchy levels. In this example, the levels from left to right are:
 
  1. Experiment specifier: PANDA
Changed:
<
<
  1. Detector sub system specifier (3-5 letters recommended):
    Subsystem specifier
    EMC EMC
>
>
  1. Detector subsystem specifier (3-5 letters):
    From http://nuclear.gla.ac.uk/DCS/interactiveTable.php?name=Subgroups
    Subsystem Specifier
    EMC EMC, (FEMC, REMC, BEMC)
 
RICH RICH
MVD MVD
Changed:
<
<
Endcap DIRC EDI
Barrel DIRC BDI
>
>
Endcap DIRC EDIRC
Barrel DIRC BDIRC
 
GEM GEM
Changed:
<
<
MUON MU
>
>
MUON MUON
 
TOF TOF
Forward Spectrometer FWD
STT STT
TPC TPC
Changed:
<
<
Magnet MAG
Target TAR
>
>
Magnet MAG, (DIP, SOL)
Target TGT, (PEL, CJT)
 
DAQ DAQ
Changed:
<
<
  1. optional sub type (e.g. APD) :
  2. signal specification (HV, LV, Temperature, ADC ....) :
  3. optional segmentation coordinates ( e.g. Sector1, Module4, Layer3, x20, y55, z1, ...) :
>
>
  1. Optional subtype (e.g. APD)
  2. Signal specification (HV, LV, Temperature, ADC ... )
  3. Optional segmentation coordinates (e.g. Sector1, Module4, Layer3, x20, y55, z1, ... )
 
  1. Channel number
Changed:
<
<
  1. value ( e.g. vmon, imon, iset, iget, ... ) :
>
>
  1. Value (e.g. vmon, imon, iset, iget, ... )
 
Changed:
<
<
capitalization
acronyms: upper case (PANDA, EMC, HV, L, S, M, T, C)
>
>
All acronyms should be capitalized: PANDA, EMC, HV, etc. The optional fields mean that a PV name can have between 8 and 10 hierarchy levels (i.e. contain 7 to 9 colons ":").
 
Changed:
<
<
-- PeterZumbruch - 08 Dec 2009

-- PeterZumbruch - 08 Dec 2009
-- DanProtopopescu - 07 Dec 2009
>
>

Contact person

 

Added:
>
>
For further questions and suggestions please contact PeterZumbruch.
 
Revision 2
08 Dec 2009 - Main.PeterZumbruch
Line: 1 to 1
 
META TOPICPARENT name="WebHome"
Changed:
<
<

PANDA PV Naming Conventions

>
>
<--			   
  • Style shortcuts - small caps (larger) bold
    • Set SCB =
    • Set SCE =
    • Set SCLB =
    • Set SCLE =
-->

PANDA PV Naming Conventions

 

The naming convention for PANDA slow control process variables is outlined below. We recommend implementing these rules early, to avoid later confusion.

Added:
>
>
... to be discussed ...

preface and basics

In view of the use of EPICS as major control system for PANDA those basic rules have to been followed

  • maximum 63 characters, recommended maximum 40 (to comply with (old) EPICS standards)
  • forbidden:
    • blanks: " ",
    • periods "." (used as attribute delimiter)
    • local special letters, Umlaute "üØ, ..." , Accents "è, ..." (possible but forbidden by this convention)
  • Logical separation by colon ":"
  • case sensitive

convention

In one line
<Experiment specifier>:<Detector Sub System>:<optional Device specification>:<Signal Type>:<Segmentation coordinates>:<Channel number>:<Value/Task>
 
Added:
>
>
Giving first an example might help
PANDA:EMC:APD:HV:S1:M4:TR4:L8:C40:Imon
which would be the monitor value of channel 40 of the current of the High voltage of an APD of the EMC in sector 1, module 4, tray 4, layer 8.

In detail

  • The colon ":" separates the hierarchy levels

... the levels from left to right are:

  1. Experiment specifier: PANDA
  2. Detector sub system specifier (3-5 letters recommended):
    Subsystem specifier
    EMC EMC
    RICH RICH
    MVD MVD
    Endcap DIRC EDI
    Barrel DIRC BDI
    GEM GEM
    MUON MU
    TOF TOF
    Forward Spectrometer FWD
    STT STT
    TPC TPC
    Magnet MAG
    Target TAR
    DAQ DAQ
  3. optional sub type (e.g. APD) :
  4. signal specification (HV, LV, Temperature, ADC ....) :
  5. optional segmentation coordinates ( e.g. Sector1, Module4, Layer3, x20, y55, z1, ...) :
  6. Channel number
  7. value ( e.g. vmon, imon, iset, iget, ... ) :

capitalization
acronyms: upper case (PANDA, EMC, HV, L, S, M, T, C)

-- PeterZumbruch - 08 Dec 2009

-- PeterZumbruch - 08 Dec 2009
  -- DanProtopopescu - 07 Dec 2009
Added:
>
>
 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding PANDA Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)