CODA

In the process of editing and updating this page. Please contact Juliette Mammei crowder@jlab.org with questions or suggestions.

PREX Main<< HOW TOs

Starting Parity DAQ CODA

Starting the GUI

Figure 1 - Main CODA window when first started.

Figure 2 - Icons at the top of the GUI, before loading a configuration.

Figure 3 - After loading the configuration, you can now press Configure.

Figure 4 - After configuring, you can now press Download, then Prestart.

Figure 5 - After a successful prestart, you can now press Go and then End.

Figure 6 - Run start window for changing info about a particular run.

Figure 7 - Run end window for entering notes about the run.

Figure 8 - CODA window after a successful run start.

• Log in as apar@adaq1
• In a terminal type startcoda
  • 4 xterms will appear (red, orange, green and yellow) as well as the main CODA window (see Figure 1)
  • CODA will automatically load the last configuration used. If you are ok with this then just go to Platform->Connect
• To change the configuration, choose Configurations->Cool
  • Select the desired configuration from the dropdown list
  • Production running would be ALL_PREX
  • Once you have loaded a configuration, some of the icons (see descriptions below) will change from grey (see Figure 2) to green (Figures 3-5)
• Press the configure icon (see Figure 3)
  • Warnings about waiting for a ROC can be ignored if it does not take too long to respond (~10s) and things are eventually successful
  • Error messages should be taken seriously
    • You can try a Reset and re-Configure
    • If that doesn't work - see DAQ Troubleshooting
• Press the Download icon (see Figure 4)

Starting a run

• After starting the GUI and loading a configuration (see above)
• Press the Prestart icon (see Figure 4)
  • As above, warnings about waiting for a ROC can be ignored (if it does not take too long to respond, ~10s) and things are eventually successful
  • Error messages should be taken seriously!
    • You can try a Reset and re-Configure
    • If that doesn't work - see DAQ Troubleshooting
• Press Go (see Figure 5)
  • a window will pop up where you can add notes (see Figure 6)
    • you can click the buttons to choose the data that goes to the runDB
    • you can also add a comment at the bottom if needed
    • Press "CLICK HERE TO ACCEPT AND START THE RUN"
  • the event counter should start incrementing (see Figure 7)
  • the event rates should be expected values
• If you made a mistake, such as:
  • accidentally loading the wrong configuration
    • stop and restart the run
    • make a followup halog entry and refer to the run
    • take note of it in the run list in the shift summary
  • accidentally submitting the wrong notes in the notes window
    • you can let the run continue as long it is the correct configuration
    • make a followup halog entry and refer to the run
    • take note of it in the run list in the shift summary

Ending a run

• Press End
  • A window should open so that you can add any needed comments (see Figure 8)
    • add any notes if necessary
    • Press "CLICK HERE TO ACKNOWLEDGE AND EXIT"
  • if this was a normal end of the run, and it ends successfully
    • all the states should change to downloaded
    • the Prestart icon should be green
• If the run ends because of a problem with CODA - see DAQ Troubleshooting

Description of the GUI

Numbered from the top left of the GUI window (see any of the Figures):

1. Configure (tools) - this opens a drop-down menu to choose the configuration
2. Download (floppy disk) - this loads the chosen configuration to the crates
3. Prestart () - this will prepare to start a run
4. Go (triangle with point to right) - this starts a run
5. End (square) - this ends a run
6. Fast Start (double-triangle pointing right) tries to go through all the steps (can be used as long as things aren't changing)
7. Reset (double-triangle pointing left) configured, but not downloaded (if you need to change configuration or GUI is wonky)
8. Pause (two vertical bars) - pauses a run (rarely used - to quote Paul King "Nothing good can come of this.")

Instructions for shift checklist

• Latest run type (Test, Physics,..)
  • You can get this from the auto-logs of start and stop runs
  • It is also in the runstart and runend windows
• Is the auto replay script running?
  • ask the analysis expert
• Run added to shift summary?
  • keep up with the run list in your shift summary
• Please attach the left/right HV and Scalers Screenshots to the shift report (do we need this)?
• Time of beginning of latest run
  • This is at the top of the CODA Run Control Window
  • You also can get this from the auto-logs of start and stop runs
• Latest run number
• Dead time (%)