2014.02.06 - Software Meeting

Agenda:

1. Software Review response                        -- Maurik, all
2. Workshop
3. Framework
4. Software Schedule updates                       -- Maurik, all
5. Project updates?                                      -- All
6. Questions?                                              -- All

Please let me know if you would like to present something.

Meeting Notes:

Responses-1

Prioritizing Tasks:  

A column is added to the software schedule showing the priorities of tasks. Most priorities are at "normal", the default. We need to pay attention to which tasks should have elevated ("high", "very high"=critical) priorities or low priority. 

Priorities will be set in two ways: From feedback from the detector groups and developers, and by looking at the timeline and the times that certain tasks need to be completed.

Data Quality Checks: 

Matt thought this was a great suggestion from the reviewers.
Sho told us that some of these checks are in place, but more are needed. 
Matt suggested that we need a Data Quality Manager, who implements and oversees the data quality. This person will need to interface with the Data Manager (formerly Homer, looking for new person) and the people from the detector subgroups. This is a very important job, but can be a lot of work. It would be good to have some level of automation.

Responses-2

Clustering Algorithms: Implementing the Jlab clustering algorithm is well on its way (Holly, Kyle). The algorithm will be implemented in Java shortly. There will also be a standalone version for comparison. A further step is to test the algorithms and to study the detailed behavior of the ECAL. 

Clustering in trigger: This is a different algorithm, because it needs to correspond to what runs on the FPGA in great detail. Kyle is reviewing the initial implementation from Sho and will make changes if needed. Kyle will also look at the trigger algorithm and make sure the diagnostics from the trigger are replicated in the software.

Globus Toolkit: Sho has already started looking into getting the Globus toolkit running at SLAC for improved data transfer speeds.

Responses-3

EVIO to Offline data mapping: Sho tells us this is in the code. It still needs to be interfaced with the Conditions Database.

Trigger monitoring: How to get the trigger monitor output accessible for comparison to our algorithms. This will be a sub-task of the task to check and update the implementation of the trigger in the offline code. (assigned to Kyle).

Interface with Slow Control DB: New task: write scripts to copy relevant information from the Slow controls DB to the Conditions Database, determine what data needs to be copied, resolve which run number is valid for the data.