Agenda:

  1. Software schedule - general comments     5       -- Maurik
  2. ECAL Software Schedule                         15+5 -- Stuart
  3. SVT Software Schedule                           15+5 -- Omar
  4. Online Monitor - Features & Schedule       10+5 -- Jeremy
  5. Other questions, brief updates                          -- All

Notes:

General comments on the software schedule:  The scheduling of tasks for software is always tricky, it depends on the availability of the person implementing the task, the difficulty and amount of work of the task, and how familiar the implementer is with the system involved. Thus the person implementing a software task should have a large say in the scheduling.

The level of importance a particular task should be discussed at the software meeting, or if it affects a particular subsystem only, at the meeting for that subsystem. Especially for framework related tasks, we should discuss the task at the software meeting and assess the priority this task gets. This is especially important for those tasks that one person wants to see implemented, but someone else needs to do the implementation. Any tasks that affect the overall software design should also be brought up at the meeting and discussed. 

Online Monitor: There were some feature requests for the online monitoring system. We talked about implementing a status page. This is now a JIRA task, but it has not been discussed sufficiently to asses a priority. We also talked about the Wired based event display. Jeremy thinks that implementing this properly will be a very large amount of work, involving writing a driver for JAS3. We talked about wether it would be sufficient to open a file and run through the events that way. This seems like the way to go, at least for now.

 

  • No labels