Week Seven

7 July:
SBS Collaboration meeting.
8 July:
SBS Collaboration meeting.
9 July:
Received email from Eric. CNU PC is still experiencing DNS problems. Keeps spamming ns.jlab.org for hostname. Not sure what is causing the error as it doesn't seem to be a visible program. Always occurs in a spam of 8 requests. Use tcpdump command to troubleshoot. Problem occurs as soon as eth0 is enabled, regardless of programs running. Experiencing problems when initializing the rcgui. When configuration and session are loaded all equipment is recognized, but fails to connect. They throw errors and are unable to properly communicate with the runcontrol. Tried various combinations of starting the run elements, to no avail. Don't think I need to re-translate since the cool database is formed but it's possible. Turns out the problem is the .tcshrc file. When I started the computer and did not run the codausersetup script I initialized CODA with incorrect variables. Should be fine now, variable definitions match. Second detector from Alex/Kondo is setup and ready for cosmic runs, flowing gas overnight.
10 July:
Seminar: Kinematic Fitting CODA still fails to initialize properly. Not sure if I accidentally changed a setting or path while trying to integrate slow_control into the rc modules. In the process of changing the testSRS configuration it seems I must have changed a setting for ROC1. I'm guessing the boot string is to blame but that seems unlikely since I haven't changed the boot string of EB1 or ER1, yet they still follow the exact same format of ROC1 (${CODA_BIN}/coda_roc1_). Whenever I try to start the equipment I receive the response (ERROR: Can not connect to session test0). I know the database that houses the equipment exists and is running since I edit the configuration using cedit. Going to delete and recreate the database using a short guide I found online. Now CODA initializes properly when I start the rcplatform but I am still unable to properly start the individual equipment.
11 July:
Talked with Alex, turns out I missed a step. Using dbedit I needed to access the "sessions" table of the srscoda database and manually add the test0 session. Important: need to specify the owner info as well as name. Owner field should read: (hostname uid gid). For the codadaq user this reads: (codadaq 501 100). Equipment now start properly. Alex suggested first doing all the coding outside CODA. Just keep everything in executable C-files, then import to CODA once it is understood properly. After checking slow_control it appears that the start-up routine sets the destination port (i.e. DAQ computer) of the reply protocol to 6039. Not sure why, since this is the APV port address. The port of the request is set to 6007, which makes sense considering it is the FEC address.