Difference between revisions of "Online Database"

From MidasWiki
Jump to navigation Jump to search
m
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
<div style="column-count:4;-moz-column-count:4;-webkit-column-count:4">
+
{{Pagelinks}}
* [[Midas_documentation|Midas Documentation]]
 
* [[Feature_listing|Feature Listing]]
 
* [[Application_listing|Application Listing]]
 
* [[Online_Database|Online Database]]
 
</div>
 
  
 
==== Links ====
 
==== Links ====
Line 11: Line 6:
 
* [[mhttpd]]
 
* [[mhttpd]]
 
* [[odbedit]]
 
* [[odbedit]]
 +
*
 
</div>
 
</div>
 
=== Accessing the ODB interactively ===
 
Accessing the MIDAS ODB interactively is done in two possible ways:
 
* Using the [[odbedit|odbedit application]] command line.
 
* Using the [[ODB Page]] of a web browser accessing the URL of the [[mhttpd|midas server]].
 
  
 
=== 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 such as the [[/Logger_ODB_tree|'''Data Logger''']], [[/ODB_Equipment_tree|'''Frontend''']] will create on their initial ODB structure without user intervention. Later it will be possible for the user to modify these configurations to fit his requirements.
+
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 40: Line 32:
 
* [[/Sequencer ODB tree]]    &rarr; ''Contain the run sequencer configuration''
 
* [[/Sequencer ODB tree]]    &rarr; ''Contain the run sequencer configuration''
 
* [[/System ODB tree]]      &rarr; ''Maintain current system information for all the connected application''
 
* [[/System ODB tree]]      &rarr; ''Maintain current system information for all the connected application''
 +
* [[/Webserver ODB tree]]    &rarr; ''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.
  
'''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 14: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)

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.