Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
how_to_run_combined_s800_gretina [2016/03/17 09:39] pereira |
how_to_run_combined_s800_gretina [2020/04/01 20:25] pereira |
====== How to run combined S800 + GRETINA ====== | ====== How to run combined S800 + GRETINA ====== |
In order to run the combined S800 + Gretina daq, the following steps need to be taken: | In order to run the combined S800 + Gretina daq, the following steps need to be taken: |
| - [[S800 DAQ tools#Running the S800 DAQ|Run the S800 ReadoutGUI]] for the S800 data acquisition system as you normally would on the S800 spdaqXX (note, at present X=50), and click the ''Start'' button. |
- [[S800 DAQ tools#Running the S800 DAQ|Run the S800 ReadoutGUI]] for the S800 data acquisition system as you normally would on spdaq19, and click the ''Start'' button. | - Make sure that the external synchronization and external clock are enabled in the S800 ULM trigger module. (Just click on the corresponding "check boxes" in the ULM GUI.) |
- Log in using the experimental account to **ddasdaq3** or any other of the systems dual homed to the GRETINA/NSCLDAQ network. | - Make sure that GRETINA DAQ is ready. |
| - Using one of the dataU6 Linux boxes (e.g. u6pc2) Log in using the experimental account to **ddasdaq3** or any other of the systems dual homed to the GRETINA/NSCLDAQ network. |
- Use command ''godaq'' to run the Readout control program. | - Use command ''godaq'' to run the Readout control program. |
- Click the ''Start'' button. This will grab remote control over the S800 Readout GUI. The S800 daq will now be in slave mode. | - Click the ''Start'' button. This will grab remote control over the S800 Readout GUI. The S800 daq will now be in slave mode. |
- You should now be able to start runs as needed in the experiment's ReadoutGUI running on the dual homed system. | - You should now be able to start runs as needed in the experiment's ReadoutGUI running on the dual homed system. |
| |
You can check the ring buffers using the command **/usr/opt/nscldaq/xxxxx/bin/ringbuffer status**, where xxxxx is the nscldaq version (as of March 2016, 11.0-020). If everything has started correctly you should have the following ring buffers in the dual homed system (e.g. ddasdaq3): | You can check the ring buffers using the command **/usr/opt/nscldaq/xxxxx/bin/ringbuffer status**, where xxxxx is the nscldaq version. If everything has started correctly you should have the following ring buffers in the dual homed system (e.g. ddasdaq3): |
| |
* **experimental-user-name (e.g. e14045)**: This ring is where sampled coincidence data is placed. This is done via a tapcat, glom pipeline. | * **experimental-user-name (e.g. e14045)**: This ring is where sampled coincidence data is placed. This is done via a tapcat, glom pipeline. |
* **spdaq19.rawccusb**: It will provide raw data from the S800 CAMAC crate. | * **spdaqXX.rawccusb**: It will provide raw data from the S800 CAMAC crate. |
* **spdaq19.rawvmusb**: It will provide raw data from the S800 VME crate. | * **spdaqXX.rawvmusb**: It will provide raw data from the S800 VME crate. |
* **spdaq19.s800filter**: It will provide the event built, reformated data from the S800 Filter. During a run, data are pushed from this ring into the GRETINA GEB. | * **spdaqXX.s800filter**: It will provide the event built, reformated data from the S800 Filter. During a run, data are pushed from this ring into the GRETINA GEB. |
| |
In addition to the normal **stagearea** structure, three directories are added that will be used to store raw S800 data: | In addition to the normal **stagearea** structure in the experiment account, three directories are added that will be used to store raw S800 data: |
| |
* **~/stagearea/rawccusb**: Event files containing raw CCUSB data from the S800. | * **~/stagearea/rawccusb**: Event files containing raw CCUSB data from the S800. |
| |
| |
| |
| |
| |
| |
| |
| |
| |
1. On spdaq48 in /user/s800/operations/daq/usb/TclXXUSB do: | |
| |
**wish ./RunControl.tcl** | |
| |
or, on devop2 (the S800 MAC machine) | |
| |
click on the operations folder on the lower icon bar and select runcontrol.command | |
| |
2. On a dataU machine logged in as the experimental account (e11007 for the June 2012 testing period) do | |
| |
**godaq** | |
| |
3. On spdaq44 do: | |
| |
**/usr/opt/daq/10.1/bin/ringbuffer status**. The output should look similar to: | |
| |
<code> | |
+----------------+------------+-------+-------------+--------+---------+---------+------+-------------+ | |
|Name |data-size(k)|free(k)|max_consumers|producer|maxget(k)|minget(k)|client|clientdata(k)| | |
+----------------+------------+-------+-------------+--------+---------+---------+------+-------------+ | |
|0400x |8195 |8195 |100 |-1 |0 |0 |- |- | | |
|s800 |8195 |8195 |100 |7485 |0 |0 |- |- | | |
|- |- |- |- |- |- |- |9143 |0 | | |
|segatest |8195 |8195 |100 |-1 |0 |0 |- |- | | |
|spdaq48.0400x |8195 |8195 |100 |17205 |0 |0 |- |- | | |
|spdaq48.segatest|8195 |8195 |100 |-1 |0 |0 |- |- | | |
+----------------+------------+-------+-------------+--------+---------+---------+------+-------------+ | |
</code> | |
| |
Upon start of run there will be another client of the s800 ring, which is the pushToGEB process. This should die on end run. | |
| |
| |
The S800 daq will now be in slave mode, and run control is done from the NSCL daq window. | |
| |
| |
| |