Difference between revisions of "EPICS archiving with MYA"
From GlueXWiki
Line 1: | Line 1: | ||
* Accelerator division at Jefferson Lab developed and currently maintains a [http://devweb.acc.jlab.org/controls_web/certified/mya/ MySQL-based EPICS archiving system called MYA]. Hall D controls group will use this system to archive the EPICS variables. | * Accelerator division at Jefferson Lab developed and currently maintains a [http://devweb.acc.jlab.org/controls_web/certified/mya/ MySQL-based EPICS archiving system called MYA]. Hall D controls group will use this system to archive the EPICS variables. | ||
* The accelerator division is also developing a Backup/Restore framework based on the MYA archiver which should allow us to tag sets of values for Hall D EPICS in MYA PVs and restore these values from the archived values. | * The accelerator division is also developing a Backup/Restore framework based on the MYA archiver which should allow us to tag sets of values for Hall D EPICS in MYA PVs and restore these values from the archived values. | ||
+ | ** Not ready for us to use. | ||
+ | |||
* MYA has a [http://devweb.acc.jlab.org/controls_web/certified/myapi/html/index.html well documented C++ API] that should allow the offline analysis software to retrieve the archive values and store them into a conditions database. | * MYA has a [http://devweb.acc.jlab.org/controls_web/certified/myapi/html/index.html well documented C++ API] that should allow the offline analysis software to retrieve the archive values and store them into a conditions database. | ||
− | * There are command-line tools that allow to work with MYA archiver, for instance to get values for particular variable in a specific time-span. | + | |
+ | * There are command-line tools, like <i>myget</i>, that allow to work with MYA archiver, for instance to get values for particular variable in a specific time-span. | ||
** Currently installed on <b>gluon01</b> and ops-machines only. It will be available on the gluon-cluster. | ** Currently installed on <b>gluon01</b> and ops-machines only. It will be available on the gluon-cluster. | ||
+ | |||
* MYA also has a graphical tool [http://devweb.acc.jlab.org/controls_web/certified/MyaViewer/ <b>MyaViewer</b>] to display variable being archived in MYA. | * MYA also has a graphical tool [http://devweb.acc.jlab.org/controls_web/certified/MyaViewer/ <b>MyaViewer</b>] to display variable being archived in MYA. | ||
** Currently no interface is available between MYA and CSS BOY, but we can pop up <b>MyaViewer</b>. | ** Currently no interface is available between MYA and CSS BOY, but we can pop up <b>MyaViewer</b>. | ||
− | ** Currently installed on <b>gluon01</b> and ops-machines only. It will be available on the gluon-cluster. | + | ** Currently installed on <b>gluon01</b> and ops-machines (like opsl00) only. It will be available on the gluon-cluster. |
+ | |||
* Figure 1 shows a screenshot of MyaViewer with some BCAL temperature history plotted. | * Figure 1 shows a screenshot of MyaViewer with some BCAL temperature history plotted. | ||
Line 14: | Line 19: | ||
** The corresponding MYA groups so far are <i>HD_BCAL_TEMPS</i>,<i>HD_FCAL_ROOM</i>, <i>HD_VME</i> . | ** The corresponding MYA groups so far are <i>HD_BCAL_TEMPS</i>,<i>HD_FCAL_ROOM</i>, <i>HD_VME</i> . | ||
** More groups and PVs will be added in time. | ** More groups and PVs will be added in time. | ||
+ | |||
+ | * To give the accelerator division capability to archive Hall D variable we gave them access to our controls network. | ||
+ | ** They can also modify our PVs (most likely inadvertently) | ||
+ | ** We need to implement ChannelAccess Security for Hall D PVs and IOCs to control what accelerator can modify. | ||
+ | **: protection is based on hostname and username that attempts to read or write EPICS PVs via ChannelAccess. |
Revision as of 09:04, 29 May 2014
- Accelerator division at Jefferson Lab developed and currently maintains a MySQL-based EPICS archiving system called MYA. Hall D controls group will use this system to archive the EPICS variables.
- The accelerator division is also developing a Backup/Restore framework based on the MYA archiver which should allow us to tag sets of values for Hall D EPICS in MYA PVs and restore these values from the archived values.
- Not ready for us to use.
- MYA has a well documented C++ API that should allow the offline analysis software to retrieve the archive values and store them into a conditions database.
- There are command-line tools, like myget, that allow to work with MYA archiver, for instance to get values for particular variable in a specific time-span.
- Currently installed on gluon01 and ops-machines only. It will be available on the gluon-cluster.
- MYA also has a graphical tool MyaViewer to display variable being archived in MYA.
- Currently no interface is available between MYA and CSS BOY, but we can pop up MyaViewer.
- Currently installed on gluon01 and ops-machines (like opsl00) only. It will be available on the gluon-cluster.
- Figure 1 shows a screenshot of MyaViewer with some BCAL temperature history plotted.
- So far requested MYA archiving for some BCAL temperature, BCAM VME fan-tray parameters and FCAL dark room parameters:
- The corresponding MYA groups so far are HD_BCAL_TEMPS,HD_FCAL_ROOM, HD_VME .
- More groups and PVs will be added in time.
- To give the accelerator division capability to archive Hall D variable we gave them access to our controls network.
- They can also modify our PVs (most likely inadvertently)
- We need to implement ChannelAccess Security for Hall D PVs and IOCs to control what accelerator can modify.
- protection is based on hostname and username that attempts to read or write EPICS PVs via ChannelAccess.