Database
Database
The database can be viewed and edited with either cedit (graphical tool for adding elements) or dbedit (tabular access of the database). The database for this setup is gep5test.
The database program is msql. The msqld daemon must be running to run coda. It is useful to start this daemon in a terminal window, so as to monitor it. The msql configuration directory is /home/gep5/msql. These various directories and names are specified in the appropriate places in the /home/gep5/codausersetup script:
Cedit screenshots
Here is the main cedit screenshot, showing the four elements that are needed for a simple VME-based acquisition system:
- A ROC, corresponding to the VME crate (ROC1 - vmedvcseel2)
- An event recorder (ER1)
- An event buffer (EB1)
- A element corresponding to the data file (coda_1)
Here are screenshots of the four subwindows corresponding to each of the above four components; these show the setup for each of them.
Dbedit screenshots
Here is a screen shot of the "scint" table in the gep5test database. The basic elements are:
- A ROC, corresponding to the VME crate (ROC1 - vmedvcseel2)
- An event recorder (ER1)
- An event buffer (EB1)
- A element corresponding to the data file (coda_1)
Here is a screen shot of the "scint_option" table in the gep5test database. The point here is that the datafile element needs to be edited to point to the appropriate data file (/home/gep5/CODA/data/test_%d.dat)
Here is a screen shot of the "process" table in the gep5test database. This was taken with CODA running, and shows the appropriate processes that should be running ...