Creating/Editing mSQL Databases for CODA

From UConn PAN
Revision as of 18:36, 26 November 2013 by Acarta (talk | contribs) (Created page with "= Creating/Editing mSQL Databases for CODA = As mentioned in the procedure for operation of the run control, CODA cannot be initialized without the mSQL daemon running. This ...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Creating/Editing mSQL Databases for CODA

As mentioned in the procedure for operation of the run control, CODA cannot be initialized without the mSQL daemon running. This is because CODA uses mSQL databases to store information about run configuration and the operational status of components. There are two tools included with CODA that allow the creation and maintenance of these databases: CEdit and DBEdit. The default directory for storing CODA run control databases is currently /home/halld/micro/coda/rcdb, but databases can also be stored in /usr/local/coda/2.6.1/common/rcdb.

CEdit

CEDit is the more user-friendly of the two tools. It features a gui that is designed for the creation of new CODA databases, and the addition of components and other information pertaining to configuration. CEDit can be opened from a terminal by typing "cedit".

  • Different run types are stored in databases, based on the components of the run. For example, the "micro_test" databases allows the use of an event builder and read-out controller. There is another database, "coda_test", which allows the use of an event builder, ROC, and event recorder.
  • Create a new database by clicking "File -> New Database". By next clicking "File -> New", a new run type can be created.
  • Open an existing database with "File -> Open Database". This will then allow access to different run types stored in that particular database.
  • To access run types in a particular database, click "File -> Open", and select the particular run type.