Software Status

Murrough Landon - 17 December 2002
http://www.hep.ph.qmul.ac.uk/landon/talks

Overview

• Overall status
• Package Details
• Schedule and next steps

Status summary

Recent progress

• Production 3 day working session with Cano
• JEM module services in good shape and related JEM software is developing rapidly
• Apart from that, many of us have spent lots of time in meetings...

Whats missing

• Feedback from our first release
• User guide for our first release?
• Working modules to integrate!

Packages (1)

HDMC: done recently

• New parts for the JEM

HDMC: to be done

• Integrate in CMT environment
• Move to pure STL (no Qt dependence for hardware parts)?

Module Services: done recently

• jemServices package

Module Services: to be done

• CMM module services to be completed
• CPM module services to be completed
• Documentation is still required

Packages (2)

Databases: done recently

• Additions for the JEM (trigger menu in existing framework)

Databases: to be done

• Conflicts with test vector generators to be resolved
• More work required for calibration datasets
• Use trigger menu configuration from CTP group
• Support for PP system
• Evolve with external changes (eg Conditions database)
• Draft user guide to be completed

Packages (3)

Run Control and IGUI: done recently

• Nothing

Run Control and IGUI: to be done

• Sequencer program for multistep tests (or calibrations)
• Update/provide documentation
• Hardware monitoring status (simple display may already be supported by Dataflow panel?)

Packages (4)

Simulation: done recently

• CPROD variants added

Simulation: to be done

• CMM, JEM, PPM simulation to be completed

Test Vector Generation: done recently

• Work on integrating JEM test vectors started

Test Vectors: to be done

• Test vectors for CMM and PPM
• CP subsystem, other subsystems, slice test system (we need to specify in detail what we want to do)

Packages (5)

Calibration: to be done

• Calibration and setup procedures required (some database infrastructure exists)

Hardware monitoring: to be done

• Read hardware status (eg links) and report to IGUI (some IGUI infrastructure exists for this)

Readout (via ROS): to be done

• Install latest ROS software, read events via Online Monitoring framework

Event dump and display: to be done

• Customise event dump (now possible!)
• Develop graphical event display?

DCS: to be done

• Hmmmm

Priorities (1)

CP or JEP?

• We always thought we would start with the CP subsystem
• But the JEM may be the first module ready and eager for testing in a larger scale setup
• ROD firmware exists (tested?) for JEM data and RoIs
• DSS LVDS and GIO cards exist (with tested software?) for sending input data and generating L1A sequences
• Not sure about CMM emulator (ie read JEM data to CMM)
• Special treatment may be needed for the JEM to set its TTCrx parameters (no I2C bus on board)

Priorities (2)

Other

• Feedback from software group required....tomorrow....