Jump to content

Christian: Difference between revisions

From Luter 345 Experiments
en>Jlabdaq
No edit summary
 
Brash99 (talk | contribs)
m 1 revision imported
 
(No difference)

Latest revision as of 17:58, 24 December 2024

In order to allow both of the computers to communicate with one another, a common kernel needed to be created. They would both run separate kernels, but they would be able to share file systems. So, a visualization software package VirtualBox was used in order to create a version of Centos and put it into the data acquisition computer's file system. This way, the VME controller and the data acquisition computer would be able to share files and data.

To start the CODA Gui, numerous programs had to be running. The ER1 (event recorder), EB1 (event buffer), and ROC1 are just a few of the programs that needed to be started up before the rcgui in order to get the system properly working. So, in order to make the process simpler, a script was created that opened all of the programs automatically. After CODA was finished, the script would then kill all of the background processes. This was important because if they weren't killed, then CODA would not properly run.

To remotely log into the controller from the data acquisition computer, the command ssh -X root@jlabvme was used. This ensured made it easier to access the controller from multiple computers at once.

A database, session, and configuration had to be created so CODA would know how the computers are connected and how to transfer the data across different computers.

When the CODA software started, it worked well after the initial problems were fixed. However, after the download took place, new errors started developing. These errors were due to the ROC codes. By checking to see if there were any differences between two of the same files in different locations, it was seen that the same files were actually different. So the newer files had to be copied over to the location where the computer was pulling from to fix the problem. After this change, CODA seemed to be working almost flawlessly.

In order to make sure the CODA software worked, a test called UnixTest was run. This would send it fake data for CODA to pick up and ensure that it is properly working. So, CODA was installed from scratch using the Jlab CODA wiki. Then, a database, session, and configuration was created using the Cedit and Dbedit setups on the Jlab CODA wiki. Then, CODA was run and data was obtained for the test.