Creating/Editing mSQL Databases for CODA - Revision history

Acarta: fixing an unfinished sentence

2013-12-06T16:18:58Z

fixing an unfinished sentence

Acarta: /* CEdit */

2013-11-26T20:17:00Z

CEdit

Acarta: /* Creating/Editing mSQL Databases for CODA */

2013-11-26T19:30:01Z

Creating/Editing mSQL Databases for CODA

Acarta: finishing dbedit section

2013-11-26T19:29:42Z

finishing dbedit section

Acarta: 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 ..."

2013-11-26T18:36:12Z

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 ..."

New page

= 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.

@@ Line 21: / Line 21: @@
 *Be sure to save the database/run type and exit CEdit before trying to run CODA.
-*The components required for a minimal setup are a ROC, Event Builder, Event Recorder, and Output File. Each ROC needs to be connected to the Event Builder, and the Event Recorder needs to be
+*The components required for a minimal setup are a ROC, Event Builder, Event Recorder, and Output File. Each ROC needs to be connected to the Event Builder, and the Event Recorder needs to be connected to an output file, but the event recorder and event builder do not need to be connected to each other.
 ==DBedit==

← Older revision		Revision as of 20:17, 26 November 2013
Line 20:		Line 20:

	*Be sure to save the database/run type and exit CEdit before trying to run CODA.		*Be sure to save the database/run type and exit CEdit before trying to run CODA.
		+
		+	*The components required for a minimal setup are a ROC, Event Builder, Event Recorder, and Output File. Each ROC needs to be connected to the Event Builder, and the Event Recorder needs to be

	==DBedit==		==DBedit==

← Older revision		Revision as of 19:30, 26 November 2013
Line 1:		Line 1:
−	~~= 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.		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.

@@ Line 4: / Line 4: @@
 ==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.
@@ Line 10: / Line 11: @@
 *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.
+*Open an existing database with "File -> Open Database". This will then allow access to different run types stored in that particular database. For example, "File -> Open Database -> micro_test" will open the default run control database, which was included with the halldtrg5 machine.
-*To access run types in a particular database, click "File -> Open", and select the particular run type.
+*Opening other kinds of objects as tables can have varying results. Opening "runtypes" allows editing of the id's of runtypes, while "sessions" allows one to edit parameters of a runtype such as run number, congifuration, owner, and other identifiers. This kind of editing is what DBedit is best used for: general run control parameters of existing configurations, as opposed to creation of new run configruations or addition of components.