Online Database: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<div style="column-count: | {{Pagelinks}} | ||
* [[ | |||
* [[ | ==== Links ==== | ||
* [[ | <div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"> | ||
* | * [[ODB]] | ||
* [[mhttpd]] | |||
* [[odbedit]] | |||
* | |||
</div> | </div> | ||
=== The ODB Structure === | === The ODB Structure === | ||
The data in the ODB are structured in a '''tree form''' with each "directory" dealing with a specific section of the acquisition. | The data in the ODB are structured in a '''tree form''' with each "directory" dealing with a specific section of the acquisition. The MIDAS system creates certain ODB trees e.g. {{Odbpath|path=/System}}, {{Odbpath|path=/Runinfo}},{{Odbpath|path=/Experiment}} when the ODB is first created. Particular system applications automatically create the ODB trees they require the first time they are run. For example, the Data Logger [[mlogger]] will create the {{Odbpath|path=/Logger}} ODB tree, and a [[Frontend Application|Frontend]] will create the {{Odbpath|path=/Equipment}} ODB tree. The user | ||
Particular system applications | will then be able to customize the ODB to fit his/her requirements by modifying the values of these keys, | ||
adding optional keys and links, and adding his/her own "directories" and keys as described throughout this documentation. See [[ODB]] for more information. | |||
=== List of ODB Trees (in alphabetical order) === | === List of ODB Trees (in alphabetical order) === | ||
| Line 28: | Line 25: | ||
* [[/History ODB tree]] → ''Contain history definition/configuration'' | * [[/History ODB tree]] → ''Contain history definition/configuration'' | ||
* [[/Logger ODB tree]] → ''Location for the data logger configuration'' | * [[/Logger ODB tree]] → ''Location for the data logger configuration'' | ||
* [[/Lazy ODB tree]] → ''Location for the secondary data logger configuration'' | |||
* [[/MSCB ODB tree]] → ''Location for the Ethernet MSCB device accessible from this experiment'' | * [[/MSCB ODB tree]] → ''Location for the Ethernet MSCB device accessible from this experiment'' | ||
* [[/Programs ODB tree]] → ''Contain all the applications information connected to this experiment'' | * [[/Programs ODB tree]] → ''Contain all the applications information connected to this experiment'' | ||
| Line 34: | Line 32: | ||
* [[/Sequencer ODB tree]] → ''Contain the run sequencer configuration'' | * [[/Sequencer ODB tree]] → ''Contain the run sequencer configuration'' | ||
* [[/System ODB tree]] → ''Maintain current system information for all the connected application'' | * [[/System ODB tree]] → ''Maintain current system information for all the connected application'' | ||
* [[/Webserver ODB tree]] → ''Configure the mhttpd web server'' | |||
'''Note:''' The user is allowed to create his/her own directory structure under root (/) for his/her own purpose. All the ODB functions are applicable to this structure as well. | |||
[[Category:ODB]] | |||
Latest revision as of 13:46, 31 March 2020
Links
The ODB Structure
The data in the ODB are structured in a tree form with each "directory" dealing with a specific section of the acquisition. The MIDAS system creates certain ODB trees e.g. /System, /Runinfo, /Experiment when the ODB is first created. Particular system applications automatically create the ODB trees they require the first time they are run. For example, the Data Logger mlogger will create the /Logger ODB tree, and a Frontend will create the /Equipment ODB tree. The user will then be able to customize the ODB to fit his/her requirements by modifying the values of these keys, adding optional keys and links, and adding his/her own "directories" and keys as described throughout this documentation. See ODB for more information.
List of ODB Trees (in alphabetical order)
- /Alarms ODB tree → Contain all the alarms definitions created by the user
- /Alias ODB tree → Location for shortcut visible in the Mdias web page
- /Analyzer ODB tree → Reserved for the data analyzer
- /Custom ODB tree → Location for custom webpage
- /Customscript ODB tree → Location for general custom scripts
- /Elog ODB tree → Location for Elog interface definition and configuration
- /Equipment ODB tree → Location for Frontend Equipment operation
- /Experiment ODB tree → Location for Experiment general configuration
- /History ODB tree → Contain history definition/configuration
- /Logger ODB tree → Location for the data logger configuration
- /Lazy ODB tree → Location for the secondary data logger configuration
- /MSCB ODB tree → Location for the Ethernet MSCB device accessible from this experiment
- /Programs ODB tree → Contain all the applications information connected to this experiment
- /Runinfo ODB tree → Contain run information
- /Script ODB tree → Contain external scripts links
- /Sequencer ODB tree → Contain the run sequencer configuration
- /System ODB tree → Maintain current system information for all the connected application
- /Webserver ODB tree → Configure the mhttpd web server
Note: The user is allowed to create his/her own directory structure under root (/) for his/her own purpose. All the ODB functions are applicable to this structure as well.