TWiki> BL4S Web>MajorTasks (revision 8)EditAttachPDF
Task list for BL4S 2015:

Development

Topic DateSorted descending Action
CrystalUndulator 2015-08-20 Assembled goniometer in B4 office
CherenkovCounter 2015-08-18 Worked with the beam instrumentation people to change gas in the Cherenkov volumes
Achieved a vacuum of 10 mBar
CrystalUndulator 2015-08-05 In contact with Ulrik Uggerhøj about goniometer at CERN
ScintilatorCounter 2015-07-29 Sketching small trigger scintillator
MonitoringSoftware 2015-07-28 New monitoring programs: DWCTracking and DWCBurstDisplay
VideoStreaming 2015-07-27 Set up BL4S-CAM-02 & 03 - FMLE installed and streaming on boot
VideoStreaming 2015-07-22 Received BL4S-CAM-02 & 03 - registered and HDDs installed
WebcamDetector 2015-07-20 Opencv installed on pcbl4sleo4g PC.
WebcamDetector 2015-07-16 Centos 7 installed in new hard disk. PC name is: pcbl4sleo4g.
VideoStreaming 2015-07-13 Flash Video live Encoder installed
Tested streaming
Tested stream on boot
CrystalUndulator 2015-07-10 Vidyo meeting with SimonHConnell and TimBrooks - discussed simulation results and planning
CrystalUndulator 2015-07-01 Meeting with SergioBallestrero, MarkusJoos and TimBrooks - discussed status and plans moving forwards
DelayWireChamber 2015-06-30 Installed regulator - need different pitch compression fittings to attach flow meter
Tested front end electronics with pulse gen and scope
VideoStreaming 2015-06-29 Ticket resolved - Windows activated remotely - Marek contacted
VideoStreaming 2015-06-26 Opened ticket with IT INC0813421
CrystalUndulator 2015-06-24 Vidyo meeting with SimonHConnell, MarkusJoos and TimBrooks - discussed experimental requirements
DelayWireChamber 2015-06-23 Borrowed LV power supply and Arb. pulse gen from electronics pool
Discussed operation with Cenk and Jorgen
VideoStreaming 2015-06-23 Put new HDD in BL4S-CAM-01 and installed Windows 7 x64
WebcamDetector 2015-06-23 Managed to disable MJPEG compression on camera
DelayWireChamber 2015-06-17 Took receipt of 2 chambers from JensSpanggaard
Got a selection of Gas fittings, thanks to KonstantinZhukov
CrystalUndulator 2015-06-16 Met with SergioBallestrero and SimonHConnell to discuss support for Team
VideoStreaming 2015-06-16 Met Marek to discuss webcam setup
Put BL4S-CAM-01 in office
WebcamDetector 2015-06-16 Vide for Linux (V4L2) installed on bl4sdaq/blrsdaq1 PC for controlling webcam from Linux.
yum install v4l-utils
WebcamDetector 2015-06-15 Pixelman s/w installed on centos 7 , connected TimePix device to PC.
CrystalUndulator 2015-06-12 Contacted LauGatignon about magnet system
Spoke to Jerome Alozy about rotation stage for crystal
WebcamDetector 2015-06-12 Met with Jerome Alexandre Alozy for TimePix. Decided to use webcam between 2 TimePix to compare the webcam results.
MRPC 2015-06-11 Recieved pin headers for board interconnects
WebcamDetector 2015-06-04 ffmpeg s/w installed on bl4sdaq PC ,tested.
MRPC 2015-05-26 Recieved PCBs
MRPC 2015-05-21 Received DIN connectors and resistors from Farnell, and caps from CERN stores
MRPC 2015-05-16 Drew the enclosure in more detail
Reminded TRT folks about enclosure requirements
StrawTracker 2015-05-15 Integrate UDP recv into DataChannel
Tested correction to error handling code
Received data from udp_sender_receiver test program, recoding it to disk
StrawTracker 2015-05-13 Integrate UDP socket code into rcd_trb Module
Looked at RAW event format
Worked on error handling code
Loaded module on BL4S DAQ hardware and tested error handling
DaqSoftware 2015-05-11 Testing rcd_empty
  • Added Jorgens schema file for rcd_trb package - can do this with oks_data_editor:
    Right click on a Data File and select 'Details', right click in the 'Include files' list and select a location in the 'Add from' sub menu.
  • Using schema, created a ReadoutModuleTRB object called TRBModule contained by the RCD object called BL4SApp
  • Created a HW_InputChannel called TRB_channel_0 contained by TRBModule and a resource of the Segment called BL4SSegment
  • Compiled all modules in dbg mode
  • Switched to prefer dbg code and enabled tracing on RCDExample packages
  • Ran BL4S partition and confirmed configuration and transitions of modules were as expected
  • DaqSoftware 2015-05-07 Monitoring beam muons
  • Spoke to Sergeui.Kolos about oh_display and ohp - directed us to /afs/cern.ch/atlas/project/tdaq/inst/tdaq/tdaq-05-05-00/ohp/share/example.conf.xml
  • Started first recording of beam muons on H8 line (run 1431024945)
  • MRPC 2015-05-06 Sent finalised designs to TS-DEM.
    DaqSoftware 2015-04-30 Long run testing
  • Ran part_BL4S and TRT_Testbeam overnight
  • Both remote IGUI instances had gone
  • part_BL4S had lost a few processes
  • Later on, PMG was briefly unavailable: - This may be due to some of the partition being restarted with a new IGUI - will retest with a clean partition
  • Agent log: bl4sdaq.cern.ch:/logs/tdaq-05-05-00/initial/pmg_agent_bl4sdaq.cern.ch_1430324493.out
  • Last job (test_app_pmg -p part_BL4S -H lnxpool41.cern.ch -a BL4SApp) ran at 17:52:27
  • Next batch of jobs all started at 17:52:49
  • RootController (bl4sdaq:/logs/tdaq-05-05-00/initial/DefaultRootController_bl4sdaq.cern.ch_1430324568.err) raised TIMEOUT at 17:52:44
  • StrawTracker 2015-04-24 Discussion of Readout architecture with Markus and Jorgen
    Jorgen proposes writing a RCD_empty package into which we can add TRB specific code
    A TRBscope program should be written to capture data from the TRB
    The TRBscope can explore the data format and understand handling of UNIX sockets
    A TRBemulator could be written to send arbitrary data at arbitrary times, or replay a sequence of packets from the TRB
    Ultimately the TRBscope code should be integrated into the RCD_empty package to form an RCD_TRB package that can run in the BL4S data-taking partition
    TimePix 2015-04-20 Trying Pixelman on SLC6
    StrawTracker 2015-04-08 Working with Elena Zarkh
    Set up DAQ PC and electronics
    Dual timer is tricky to start up as a pulse generator
    Used switch box to view test pulses from front end electronics
    Found that the TRB needs a LVDS trigger, when disconnected it free runs to around 40kHz
    The trigger box (based around one of the level converter cards) accepts TTL level signals and outputs LVDS across all channels
    Some channels seem to be flipped or offset - check trigger box outputs when setting up
    Outputs are on a pin header so one can use the switch box to probe the channels, connecting to a scope over LEMO cables
    The discriminator for one of the channels had a very narrow pulse width, killing the coincidence rate - we adjusted this up to ~100ns
    We measured the coincidence rate of the scintilators to be just below 10Hz
    A small test run did not collect any meaningful statistics
    Overnight run started ~21:50
    StrawTracker 2015-04-07 Meeting with Elena Zarkh
    Started HV for overnight conditioning
    Found DAQ PC(styxbn.cern.ch) had a dead power supply
    Borrowed PSU from bl4sdaq1 for the moment
    StrawTracker 2015-04-02 Meeting with Konstantine Zhukov
    Started gas flow to condition straws
    MRPC 2015-04-01 Emailed comments from William Billereau - add README for organisation of the output files, add corner alignment markers to the copper and silk layers.
    TimePix 2015-03-31 Meeting with TimePix experts Winnie and Erik
    Possible Neutron converters applied to the sensor
    FitPix USB readout card ~3000CHF
    TimePix readout + Si sensor + wirebonding ~1000CHF
    Data clock: 50MHz
    14 bits per pixel
    MRPC 2015-03-23 The PCB layout of Anode, Cathode and VHDCI adapter boards is done. Need to verify mechanical and electrical correctness.
    StrawTracker 2015-03-13 Visit SR1 to see CERN's STYX module
    Check the gas system in SR1
    Mix the gasses (Ar/CO2)
    MRPC 2015-03-11 Draft layouts for Anode and Cathode boards done.
    MRPC 2015-03-09 Met Adrian to discuss layout issues and power supply. Met PCB fabrication group (TS-DEM-PMT).
    MRPC 2015-03-04 First layouts.
    MRPC 2015-02-25 First meeting with Crispin and Adrian.

    GeneralInfrastructure

    CrystalUndulator

    Date Action
    2015-08-20 Assembled goniometer in B4 office
    2015-08-05 In contact with Ulrik Uggerhøj about goniometer at CERN
    2015-07-10 Vidyo meeting with SimonHConnell and TimBrooks - discussed simulation results and planning
    2015-07-01 Meeting with SergioBallestrero, MarkusJoos and TimBrooks - discussed status and plans moving forwards
    2015-06-24 Vidyo meeting with SimonHConnell, MarkusJoos and TimBrooks - discussed experimental requirements
    2015-06-16 Met with SergioBallestrero and SimonHConnell to discuss support for Team
    2015-06-12 Contacted LauGatignon about magnet system
    Spoke to Jerome Alozy about rotation stage for crystal

    WebcamDetector

    Date Action
    2015-07-20 Opencv installed on pcbl4sleo4g PC.
    2015-07-16 Centos 7 installed in new hard disk. PC name is: pcbl4sleo4g.
    2015-06-23 Managed to disable MJPEG compression on camera
    2015-06-16 Vide for Linux (V4L2) installed on bl4sdaq/blrsdaq1 PC for controlling webcam from Linux.
    yum install v4l-utils
    2015-06-15 Pixelman s/w installed on centos 7 , connected TimePix device to PC.
    2015-06-12 Met with Jerome Alexandre Alozy for TimePix. Decided to use webcam between 2 TimePix to compare the webcam results.
    2015-06-04 ffmpeg s/w installed on bl4sdaq PC ,tested.
    2015-07-03 Meeting with Jerome to work with several medipix devices in one readout. Request for second Timepix and radioactive source.

    Description Action by Status
    We should by the same Web cam as they have Candan Looking for a supplier
    Look for Linux compatible S/W for reading single images via USB from the camera Candan to be started
    Understanding the camera Candan Question: can we control the exposure time? If necessary Markus will contact Logitech about technical support

    List Of Equipments

    1. 3 Logitech C270 Webcam.
    2. 2 Timepix with FITPIX.
    3. 5 SATA Hard Disk
    4. 1 USB Hub (7-Port Powered Mobile Hub) and cables

    -- TimBrooks - 2015-06-03

    MRPC

    Date Action
    2015-05-16 Drew the enclosure in more detail
    Reminded TRT folks about enclosure requirements
    2015-06-11 Recieved pin headers for board interconnects
    2015-05-26 Recieved PCBs
    2015-05-21 Received DIN connectors and resistors from Farnell, and caps from CERN stores
    2015-05-06 Sent finalised designs to TS-DEM.
    2015-04-01 Emailed comments from William Billereau - add README for organisation of the output files, add corner alignment markers to the copper and silk layers.
    2015-03-23 The PCB layout of Anode, Cathode and VHDCI adapter boards is done. Need to verify mechanical and electrical correctness.
    2015-03-11 Draft layouts for Anode and Cathode boards done.
    2015-03-09 Met Adrian to discuss layout issues and power supply. Met PCB fabrication group (TS-DEM-PMT).
    2015-03-04 First layouts.
    2015-02-25 First meeting with Crispin and Adrian.

    StrawTracker

    Date Action
    2015-05-15 Integrate UDP recv into DataChannel
    Tested correction to error handling code
    Received data from udp_sender_receiver test program, recoding it to disk
    2015-05-13 Integrate UDP socket code into rcd_trb Module
    Looked at RAW event format
    Worked on error handling code
    Loaded module on BL4S DAQ hardware and tested error handling
    2015-04-24 Discussion of Readout architecture with Markus and Jorgen
    Jorgen proposes writing a RCD_empty package into which we can add TRB specific code
    A TRBscope program should be written to capture data from the TRB
    The TRBscope can explore the data format and understand handling of UNIX sockets
    A TRBemulator could be written to send arbitrary data at arbitrary times, or replay a sequence of packets from the TRB
    Ultimately the TRBscope code should be integrated into the RCD_empty package to form an RCD_TRB package that can run in the BL4S data-taking partition
    2015-04-08 Working with Elena Zarkh
    Set up DAQ PC and electronics
    Dual timer is tricky to start up as a pulse generator
    Used switch box to view test pulses from front end electronics
    Found that the TRB needs a LVDS trigger, when disconnected it free runs to around 40kHz
    The trigger box (based around one of the level converter cards) accepts TTL level signals and outputs LVDS across all channels
    Some channels seem to be flipped or offset - check trigger box outputs when setting up
    Outputs are on a pin header so one can use the switch box to probe the channels, connecting to a scope over LEMO cables
    The discriminator for one of the channels had a very narrow pulse width, killing the coincidence rate - we adjusted this up to ~100ns
    We measured the coincidence rate of the scintilators to be just below 10Hz
    A small test run did not collect any meaningful statistics
    Overnight run started ~21:50
    2015-04-07 Meeting with Elena Zarkh
    Started HV for overnight conditioning
    Found DAQ PC(styxbn.cern.ch) had a dead power supply
    Borrowed PSU from bl4sdaq1 for the moment
    2015-04-02 Meeting with Konstantine Zhukov
    Started gas flow to condition straws
    2015-03-13 Visit SR1 to see CERN's STYX module
    Check the gas system in SR1
    Mix the gasses (Ar/CO2)

    TimePix development

    Date Action
    2015-04-20 Trying Pixelman on SLC6
    2015-03-31 Meeting with TimePix experts Winnie and Erik
    Possible Neutron converters applied to the sensor
    FitPix USB readout card ~3000CHF
    TimePix readout + Si sensor + wirebonding ~1000CHF
    Data clock: 50MHz
    14 bits per pixel

    DaqSoftware upgrade

    Date Action
    2015-05-11 Testing rcd_empty
  • Added Jorgens schema file for rcd_trb package - can do this with oks_data_editor:
    Right click on a Data File and select 'Details', right click in the 'Include files' list and select a location in the 'Add from' sub menu.
  • Using schema, created a ReadoutModuleTRB object called TRBModule contained by the RCD object called BL4SApp
  • Created a HW_InputChannel called TRB_channel_0 contained by TRBModule and a resource of the Segment called BL4SSegment
  • Compiled all modules in dbg mode
  • Switched to prefer dbg code and enabled tracing on RCDExample packages
  • Ran BL4S partition and confirmed configuration and transitions of modules were as expected
  • 2015-05-07 Monitoring beam muons
  • Spoke to Sergeui.Kolos about oh_display and ohp - directed us to /afs/cern.ch/atlas/project/tdaq/inst/tdaq/tdaq-05-05-00/ohp/share/example.conf.xml
  • Started first recording of beam muons on H8 line (run 1431024945)
  • 2015-05-03 Very long run testing
  • Some PMG timeouts around 07:06
  • BL4SApp starts throwing errors:
    20:05:12 ERROR BL4SApp rc::ParentUpdateFailure Failed to notify the parent controller "BL4SSegment" about changes in my status
    20:05:11 ERROR BL4SApp rc::CorbaException Received CORBA exception "TRANSIENT" when interacting with BL4SSegment
  • IGUI commands raise the following errors: Command Error Close
    IGUI - Command Error
     
    
    Message:
        daq.rc.RCException$CORBAException: Failed contacting "BL4SSegment". Reason: org.omg.CORBA.TRANSIENT: Retries exceeded, couldn't reconnect to 137.138.89.83:34362  vmcid: 0x0  minor code: 0  completed: No
    Level:
        SEVERE
    Stack Trace:
    Failed contacting "BL4SSegment". Reason: org.omg.CORBA.TRANSIENT: Retries exceeded, couldn't reconnect to 137.138.89.83:34362 vmcid: 0x0 minor code: 0 completed: No
        daq.rc.CommandSender.executeCommand(CommandSender.java:376)
        Igui.Igui.sendControllerCommand(Igui.java:1919)
        Igui.RunControlAdvancedPanel$ButtonActions$1.run(RunControlAdvancedPanel.java:249)
        java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        java.lang.Thread.run(Thread.java:724)
    Retries exceeded, couldn't reconnect to 137.138.89.83:34362
        org.jacorb.orb.iiop.ClientIIOPConnection.connect(ClientIIOPConnection.java:226)
        org.jacorb.orb.giop.GIOPConnection.sendMessage(GIOPConnection.java:1072)
        org.jacorb.orb.giop.GIOPConnection.sendRequest(GIOPConnection.java:1017)
        org.jacorb.orb.giop.ClientConnection.sendRequest(ClientConnection.java:308)
        org.jacorb.orb.giop.ClientConnection.sendRequest(ClientConnection.java:289)
        org.jacorb.orb.Delegate._invoke_internal(Delegate.java:1419)
        org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1244)
        org.jacorb.orb.Delegate.invoke(Delegate.java:1232)
        org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:475)
        rc._commanderStub.executeCommand(_commanderStub.java:1185)
        daq.rc.CommandSender.executeCommand(CommandSender.java:358)
        Igui.Igui.sendControllerCommand(Igui.java:1919)
        Igui.RunControlAdvancedPanel$ButtonActions$1.run(RunControlAdvancedPanel.java:249)
        java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        java.lang.Thread.run(Thread.java:724)
    Transition Error Close
    IGUI - Transition Error
     
    
    Message:
        daq.rc.RCException$CORBAException: Failed contacting "RootController". Reason: org.omg.CORBA.TRANSIENT: Retries exceeded, couldn't reconnect to 137.138.89.83:42921  vmcid: 0x0  minor code: 0  completed: No
    Level:
        SEVERE
    Stack Trace:
    Failed contacting "RootController". Reason: org.omg.CORBA.TRANSIENT: Retries exceeded, couldn't reconnect to 137.138.89.83:42921 vmcid: 0x0 minor code: 0 completed: No
        daq.rc.CommandSender.executeCommand(CommandSender.java:431)
        daq.rc.CommandSender.makeTransition(CommandSender.java:468)
        Igui.Igui.sendRootControllerTransitionCommand(Igui.java:1890)
        Igui.MainPanel$8.run(MainPanel.java:2606)
        java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        java.lang.Thread.run(Thread.java:724)
    Retries exceeded, couldn't reconnect to 137.138.89.83:42921
        org.jacorb.orb.iiop.ClientIIOPConnection.connect(ClientIIOPConnection.java:226)
        org.jacorb.orb.giop.GIOPConnection.sendMessage(GIOPConnection.java:1072)
        org.jacorb.orb.giop.GIOPConnection.sendRequest(GIOPConnection.java:1017)
        org.jacorb.orb.giop.ClientConnection.sendRequest(ClientConnection.java:308)
        org.jacorb.orb.giop.ClientConnection.sendRequest(ClientConnection.java:289)
        org.jacorb.orb.Delegate._invoke_internal(Delegate.java:1419)
        org.jacorb.orb.Delegate.invoke_internal(Delegate.java:1244)
        org.jacorb.orb.Delegate.invoke(Delegate.java:1232)
        org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:475)
        rc._commanderStub.makeTransition(_commanderStub.java:1081)
        daq.rc.CommandSender.executeCommand(CommandSender.java:413)
        daq.rc.CommandSender.makeTransition(CommandSender.java:468)
        Igui.Igui.sendRootControllerTransitionCommand(Igui.java:1890)
        Igui.MainPanel$8.run(MainPanel.java:2606)
        java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        java.lang.Thread.run(Thread.java:724)
  • Logs from this time:
    /tmp/part_BL4S/RCD@BL4SApp@TestRCAppRunning-test_app_pmg_bl4sdaq.cern.ch_1430628559.err
    /tmp/part_BL4S/RCD@BL4SApp@TestRCAppRunning-test_app_pmg_bl4sdaq.cern.ch_1430628579.err
    /tmp/part_BL4S/BL4SSegment_bl4sdaq.cern.ch_1430411323.err
    /tmp/part_BL4S/RootController_bl4sdaq.cern.ch_1430411315.err
    /tmp/part_BL4S/RCD_Monitor_bl4sdaq.cern.ch_1430411369.out
    /tmp/part_BL4S/RCD_Monitor_bl4sdaq.cern.ch_1430411369.err
    /tmp/part_BL4S/monitoring-conductor_bl4sdaq.cern.ch_1430411315.out
    /tmp/part_BL4S/core.26581
  • PMG lists the following: pmg_list_partition -p part_BL4S Close
    Asking all the agents about processes running in partition part_BL4S
    APPLICATION            PARTITION   HANDLE                                                   
    CHIP                   part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/CHIP/1                   
    DDC                    part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/DDC/1                    
    DF                     part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/DF/1                     
    DFConfig               part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/DFConfig/1               
    DQM                    part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/DQM/1                    
    Histogramming          part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/Histogramming/1          
    ISRepository           part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/ISRepository/1           
    MTS                    part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/MTS/1                    
    Monitoring             part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/Monitoring/1             
    PMG                    part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/PMG/1                    
    RDB                    part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/RDB/1                    
    RDB_POOL_1             part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/RDB_POOL_1/1             
    RDB_RW                 part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/RDB_RW/1                 
    ResInfoProvider        part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/ResInfoProvider/1        
    Resources              part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/Resources/1              
    RunCtrl                part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/RunCtrl/1                
    RunCtrlStatistics      part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/RunCtrlStatistics/1      
    RunParams              part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/RunParams/1              
    Setup                  part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/Setup/1                  
    ipc-server             part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/ipc-server/1             
    monitoring-conductor   part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/monitoring-conductor/1   
    mts-worker             part_BL4S   pmg://bl4sdaq.cern.ch/part_BL4S/mts-worker/1             
    BL4SApp                part_BL4S   pmg://lnxpool41.cern.ch/part_BL4S/BL4SApp/2
  • 2015-04-30 Long run testing
  • Ran part_BL4S and TRT_Testbeam overnight
  • Both remote IGUI instances had gone
  • part_BL4S had lost a few processes
  • Later on, PMG was briefly unavailable: - This may be due to some of the partition being restarted with a new IGUI - will retest with a clean partition
  • Agent log: bl4sdaq.cern.ch:/logs/tdaq-05-05-00/initial/pmg_agent_bl4sdaq.cern.ch_1430324493.out
  • Last job (test_app_pmg -p part_BL4S -H lnxpool41.cern.ch -a BL4SApp) ran at 17:52:27
  • Next batch of jobs all started at 17:52:49
  • RootController (bl4sdaq:/logs/tdaq-05-05-00/initial/DefaultRootController_bl4sdaq.cern.ch_1430324568.err) raised TIMEOUT at 17:52:44
  • 2015-04-29 Integrated monitoring
  • Fixed issue with v792 channel labelling - turns out the upper and lower 16 channels are interleaved with each other
  • Have rcd_monitor running continuously, collecting histograms every 10 seconds
  • Added RCD_Monitor to BL4S configuration database as a CustomLifetimeApplication under the BL4SSegment, lifetime set to SOR_EOR so the monitoring is available when running
  • Worked with Emre to test TRT_Monitor on TRT and BL4S hardware
  • 2015-04-26 Modified DAQ school monitoring code to monitor all channels
  • Saved in new module RCDMonitor
  • bl4sdaq paused for ~7 minutes with the message:
    Apr 26 17:31:16 bl4sdaq kernel: volume 537093198 is busy or server is down, rechecking
  • Strange monitoring-conductor error:
    omniORB: From endpoint: giop:tcp:137.138.89.83:51793. Detected GIOP 1.2 protocol error in input message. giopImpl12.cc:411. Connection is closed.
  • 2015-04-22 Run DAQ school monitoring program in BL4S partition
  • CmdLine object needs a NULL instead of 0
  • TDC data now has a timestamp as 'channel 0' and the first physical channel is now named 'channel 1'
  • Included TH2.h to produce 2D histograms
  • Published a 2D histogram of charge from QDC0 vs. QCD1
  • ROOT still has the horrific 16-bit colour palette
  • 2015-04-13 Run TRT partition on TRT hardware
  • Fixed pmgserver issue by removing reject rule in iptables for pc-test-trt-01 - thanks to Giovanna (See HowTo#Setting_up_computers for more)
  • Set addresses to match the TRT hardware
  • 2015-04-09/10 Set up TEST-TRT PCs
  • Ran into trouble running TRT_Testbeam partition - Giovanna helped killing a rogue IPC server and diagnosing a linux ulimit on threads that was causing applications to fail randomly
  • Had trouble getting the PMG server to start on the TRT SBC (lnxpool46) - Actually it started all right but couldn't communicate back to its client. The client needs to have iptables rules relaxed from the default.
  • 2015-04-01 Met with TRT team for discussion of requirements
  • Forked bl4sdaq repository to have a TRT package: https://svnweb.cern.ch/cern/wsvn/bl4sdaq/TRTTestBeamDaq
  • Ran BL4S DAQ with pulser input - achieved 10kHz readout of full TDC buffer and 32x QDC channels
  • 2015-03-26 Updated to tdaq-05-05-00 with the help of Jorgen and Per
  • Having problems with passwordless login to lnxpool41 - need root access to debug server side of connection - daquser seems to have no such problems.
  • This works fine on sbctest-717
  • setup_daq sometimes has problems starting the pmgserver on lnxpool41 - probably as a result of the above.
  • 2015-03-26 Updating to tdaq-05-05-00
  • Remember to update the project.cmt file or you'll include headers from the old version.
  • Updated tags for the partition and sw_repository objects in the database.
  • Starting the partition, have error message that "/logs" doesn't exist - defined in the LogsRoot attribute of the partition (=LogsRoot= is some nonsense in the setup_daq script - the message comes from checking $TDAQ_LOGS_PATH, $TDAQ_RESULTS_LOGS_PATH and $TDAQ_BACKUP_PATH which are populated by rc_print_partition_env).
    The path is correctly defined in the LogRoot attribute. Can't see this new attribute in the tdaq-05-05-00 schema. - Looks to be from the initial partition defined in '/afs/cern.ch/atlas/project/tdaq/databases/v41/daq/segments/setup-initial.data.xml' but that is LogRoot = '/logs/${TDAQ_VERSION}'
  • The initial partition tries to connect to pc-atd-cc-02.cern.ch - while I was working, someone modified the database file above to fix this.
  • IGUI Main Panel Error when clicking 'Set Values' in the Run Settings: Main Panel Error Close
    Main Panel Error
     
    
    Message:
        java.util.concurrent.ExecutionException: Igui.IguiException$ISException: Checkout from RunParams IS server failed: is.InfoNotCompatibleException
    Level:
        SEVERE
    Stack Trace:
    Igui.IguiException$ISException: Checkout from RunParams IS server failed: is.InfoNotCompatibleException
        java.util.concurrent.FutureTask.report(FutureTask.java:122)
        java.util.concurrent.FutureTask.get(FutureTask.java:188)
        javax.swing.SwingWorker.get(SwingWorker.java:602)
        Igui.MainPanel$RunParamsUpdater.done(MainPanel.java:1416)
        javax.swing.SwingWorker$5.run(SwingWorker.java:737)
        javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.run(SwingWorker.java:832)
        sun.swing.AccumulativeRunnable.run(AccumulativeRunnable.java:112)
        javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.actionPerformed(SwingWorker.java:842)
        javax.swing.Timer.fireActionPerformed(Timer.java:312)
        javax.swing.Timer$DoPostEvent.run(Timer.java:244)
        java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)
        java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733)
        java.awt.EventQueue.access$200(EventQueue.java:103)
        java.awt.EventQueue$3.run(EventQueue.java:694)
        java.awt.EventQueue$3.run(EventQueue.java:692)
        java.security.AccessController.doPrivileged(Native Method)
        java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
        java.awt.EventQueue.dispatchEvent(EventQueue.java:703)
        java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
        java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
        java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
        java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
        java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
        java.awt.EventDispatchThread.run(EventDispatchThread.java:91)
    Checkout from RunParams IS server failed: is.InfoNotCompatibleException
        Igui.MainPanel$RunParamsUpdater.doInBackground(MainPanel.java:1386)
        Igui.MainPanel$RunParamsUpdater.doInBackground(MainPanel.java:1343)
        javax.swing.SwingWorker$1.call(SwingWorker.java:296)
        java.util.concurrent.FutureTask.run(FutureTask.java:262)
        javax.swing.SwingWorker.run(SwingWorker.java:335)
        java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        java.lang.Thread.run(Thread.java:724)
    null
        is.Repository.getValue(Repository.java:355)
        is.NamedInfo.checkout(NamedInfo.java:124)
        Igui.MainPanel$RunParamsUpdater.doInBackground(MainPanel.java:1380)
        Igui.MainPanel$RunParamsUpdater.doInBackground(MainPanel.java:1343)
        javax.swing.SwingWorker$1.call(SwingWorker.java:296)
        java.util.concurrent.FutureTask.run(FutureTask.java:262)
        javax.swing.SwingWorker.run(SwingWorker.java:335)
        java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        java.lang.Thread.run(Thread.java:724)
    - This was due to an old log file that was being incorrectly parsed for the run settings. Deleting the logs forced IGUI to fill in the default values and allowed them to be set.
  • 2015-03-25 First run of BL4S partition in 2015!
  • ReadoutApplication hung while looking for VME modules - base addresses were mismatched between database and hardware.
  • CenkYildiz will commit current state into SVN then tag as last version of BL4S2014 DAQSoftware. BL4S2015 development can continue from there.
  • Tried debugging ReadoutApplication by setting TraceLevel and TracePackage - MAKE SURE TO RESET THIS
  • Next MajorTask is to run with tdaq-05-05-00. Will need to switch CMTCONFIG to use gcc48.
  • May look at diff of the readout modules between the bl4sdaq repository and ATLAS SVN with a view to pushing changes upstream.
  • MonitoringSoftware expects data layout as in 2014 and so will not run with the lab test setup. Could split this into low- and high-level monitoring, such that low-level monitoring only looks at available modules and performance metrics. High-level monitoring could perform reconstruction and physics analysis under an assumed detector configuration.
  • MonitoringSoftware

    Date Action
    2015-07-28 New monitoring programs: DWCTracking and DWCBurstDisplay

    EventViewer

    AnalysisSoftware

    -- TimBrooks - 2015-03-25

    Edit | Attach | Watch | Print version | History: r9 < r8 < r7 < r6 < r5 | Backlinks | Raw View | Raw edit | More topic actions...
    Topic revision: r8 - 2015-06-04 - TimBrooks
     
      • Cern Search Icon Cern Search
      • TWiki Search Icon TWiki Search
      • Google Search Icon Google Search

      BL4S All webs login

    This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
    Ideas, requests, problems regarding TWiki? Send feedback