Difference between revisions of "Online Projects"

From GlueXWiki
Jump to: navigation, search
m
m
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
Contact Elliott Wolin (wolin@jlab.org) for more details.
+
Contact Elliott Wolin (wolin@jlab.org) for more details.  Abbreviated descriptions of most of the 12GEV tasks can be found in the most recent BOE area (http://www.jlab.org/Hall-D/halld_secure/rebaseline/BOE).
  
  
Line 7: Line 7:
 
* '''Event display'''
 
* '''Event display'''
 
** Fully develop online event display using bCNU, EVE or other framework.
 
** Fully develop online event display using bCNU, EVE or other framework.
** estimate 26 man-weeks effort.
+
** estimate 22 man-weeks effort.
 
** Status:
 
** Status:
 
*** Have working (preliminary) version using bCNU framework (CNU students).
 
*** Have working (preliminary) version using bCNU framework (CNU students).
Line 13: Line 13:
  
  
* '''RootSpy'''
+
* '''Event monitoring'''
** Fully develop distributed Root histogram creation, viewing and archiving package.
+
** Develop JANA framework for RootSpy-enabled online monitoring, collect detector histogram plugins from detector groups.
** Need plugin, gui, gateway, aggregator, archiver, finish mini-HBook facility, etc.
+
** estimate 8 man-weeks effort.
** estimate 12 man-weeks effort.
+
 
** Status:
 
** Status:
*** Dave Lawrence wrote initial version.
+
*** Elliott W has plugin templates.
*** Have working prototype developed by students.
+
*** Northwestern Univ. interested.
  
  
* '''Process monitoring'''
+
* '''RootSpy Histogram archive/retrieval'''
** Develop process monitoring system.
+
** Develop histogram archive/retrieval system for the RootSpy system.
** estimate 4 man-weeks effort.
+
** estimate 5 man-weeks effort.
 
** Status:
 
** Status:
*** Have example from CLAS.
+
*** Prototype RootSpy system exists.
 
+
*** Northwestern University interested.
 
+
* '''Hardware monitoring'''
+
** Develop computer hardware monitoring system.
+
** estimate 6 man-weeks effort.
+
** Status:
+
*** Vardan has many ideas.
+
  
  
Line 69: Line 62:
 
* '''Conditions database'''
 
* '''Conditions database'''
 
** Develop conditions database.
 
** Develop conditions database.
** estimate 6 man-weeks effort
+
** estimate 4 man-weeks effort
 
** Status:
 
** Status:
 
*** Mark has design, Dmitry will probably implement this.
 
*** Mark has design, Dmitry will probably implement this.
Line 81: Line 74:
  
  
* '''Self-configuring front end readout list'''
+
* '''Front end readout lists'''
** Develop readout list capable of detecting which boards are in a crate and reading them out efficiently.
+
** Develop a generic readout list scheme capable of detecting which boards are in a crate and reading them out efficiently.
** Must implement only those boards in operator-chosen trigger configuration.
+
** Must implement only those boards listed in operator-chosen trigger configuration.
** Should also document configuration in Hall D database.
+
** Must also document configuration in Hall D database.
 
** estimate 6 man-week effort.
 
** estimate 6 man-week effort.
 
** Status:
 
** Status:
Line 91: Line 84:
  
 
* '''Alarm system'''
 
* '''Alarm system'''
** Implement experiment alarm system based on recommendations.
+
** Implement experiment alarm system based on recommendations (earlier task).
 
** estimate 8 man-weeks effort.
 
** estimate 8 man-weeks effort.
 
** Status:
 
** Status:
Line 97: Line 90:
  
  
* '''Event disentangler'''
+
* '''Run bookkeeping scripts'''
** Develop Hall D specific event disentangler capable of handling full luminosity.
+
** Develop scripts to store pre- and post-run information in online databases.
** Determine where it should run (ROC, EB, both?).
+
 
** estimate 6 man-week effort.
 
** estimate 6 man-week effort.
 
** Status:
 
** Status:
*** Carl best choice, he's done some work on this already.
+
*** Most if not all can be stored in the to-be-developed conditions database.  Backup mechanism needs to be developed.
 +
 
 +
 
 +
* '''Archive run conditions'''
 +
** Collect relevant information from multiple sources during run and archive.
 +
** estimate 10 man-week effort.
 +
** Status:
 +
*** Most if not all can be stored in the to-be-developed conditions database.  Backup mechanism needs to be developed.
 +
 
 +
 
 +
 
 +
* '''Out of band events'''
 +
** Develop server to insert out-of-band events into the event stream.
 +
** estimate 6 man-week effort.
 +
** Status:
 +
*** Same idea as was done for CLAS.
 +
 
 +
 
 +
* '''Translation table'''
 +
** Implement translation table in JANA.
 +
** estimate 3 man-week effort
 +
** Status:
 +
*** Prototype translation table exists.
  
  
  
 
== Other (Low Priority) Projects Suitable for Outside Groups ==
 
== Other (Low Priority) Projects Suitable for Outside Groups ==
 +
 +
 +
* '''Process monitoring'''
 +
** Develop process monitoring system.
 +
** estimate 4 man-weeks effort.
 +
** Status:
 +
*** Have example from CLAS.
 +
 +
 +
* '''Hardware monitoring'''
 +
** Develop computer hardware monitoring system.
 +
** estimate 6 man-weeks effort.
 +
** Status:
 +
*** Vardan has many ideas.
  
  
Line 114: Line 142:
 
** estimate 12 man-weeks effort.
 
** estimate 12 man-weeks effort.
 
** Status:
 
** Status:
 +
  
 
* '''Info Server for generic information storage and retreival'''
 
* '''Info Server for generic information storage and retreival'''
Line 126: Line 155:
 
** Status:
 
** Status:
 
*** MIT group is interested and has experience from LHCb.
 
*** MIT group is interested and has experience from LHCb.
 +
 +
 +
* '''RootSpy development'''
 +
** Further develop RootSpy package, including mini-HBook feature.
 +
** estimate 6 man-weeks effort.
 +
** Status:
 +
*** See Dave L's note for suggested improvements.
 +
*** Summer student worked on mini-HBook.
 +
*** Northwestern Univ. interested.
  
  
Line 145: Line 183:
 
** Status:
 
** Status:
 
*** Not sure this is needed.
 
*** Not sure this is needed.
 +
 +
 +
 +
== In progress ==
 +
 +
* '''Event disentangler'''
 +
** Develop Hall D specific event disentangler capable of handling full luminosity.
 +
** Determine where it should run (ROC, EB, both?).
 +
** estimate 6 man-week effort.
 +
** Status:
 +
*** Carl best choice, he's done some work on this already.

Latest revision as of 13:19, 19 March 2013

Contact Elliott Wolin (wolin@jlab.org) for more details. Abbreviated descriptions of most of the 12GEV tasks can be found in the most recent BOE area (http://www.jlab.org/Hall-D/halld_secure/rebaseline/BOE).


12GeV (High Priority) Projects Suitable for Outside Groups

  • Event display
    • Fully develop online event display using bCNU, EVE or other framework.
    • estimate 22 man-weeks effort.
    • Status:
      • Have working (preliminary) version using bCNU framework (CNU students).
      • Have proof of concept using EVE (Dmitry).


  • Event monitoring
    • Develop JANA framework for RootSpy-enabled online monitoring, collect detector histogram plugins from detector groups.
    • estimate 8 man-weeks effort.
    • Status:
      • Elliott W has plugin templates.
      • Northwestern Univ. interested.


  • RootSpy Histogram archive/retrieval
    • Develop histogram archive/retrieval system for the RootSpy system.
    • estimate 5 man-weeks effort.
    • Status:
      • Prototype RootSpy system exists.
      • Northwestern University interested.


  • EPICS gui's using Control System Studio
    • Develop many EPICS gui's.
    • estimate 8 man-weeks effort.
    • Status:
      • A few developed by Hovanes, Nerses, Vanik and Beni.


  • SNS EPICS alarm system (BEAST)
    • Test and make recommendation for implementation.
    • estimate 4 man-weeks effort.
    • Status:


  • SCONS ("make" replacement)
    • Develop online build system using SCONS.
    • estimate 4 man-weeks effort.
    • Status:
      • Start with Maurizio's system for CLAS12.


12GeV (High Priority) Projects Suitable for Local Groups

  • Computer monitoring/alarm system
    • Learn about Ganglia, NAGIOS and similar systems, choose one and implement.
    • estimate 4 man-weeks effort
    • Status:
      • Paul Letta will probably do this.


  • Conditions database
    • Develop conditions database.
    • estimate 4 man-weeks effort
    • Status:
      • Mark has design, Dmitry will probably implement this.


  • Farm manager CODA component
    • Develop CODA component capable of managing monitoring of level 3 farm system.
    • estimate 7 man-weeks effort
    • Status:
      • Vardan will probably do this.


  • Front end readout lists
    • Develop a generic readout list scheme capable of detecting which boards are in a crate and reading them out efficiently.
    • Must implement only those boards listed in operator-chosen trigger configuration.
    • Must also document configuration in Hall D database.
    • estimate 6 man-week effort.
    • Status:
      • Bryan developed crate scan software.


  • Alarm system
    • Implement experiment alarm system based on recommendations (earlier task).
    • estimate 8 man-weeks effort.
    • Status:
      • Current best choice seems to be BEAST from SNS.


  • Run bookkeeping scripts
    • Develop scripts to store pre- and post-run information in online databases.
    • estimate 6 man-week effort.
    • Status:
      • Most if not all can be stored in the to-be-developed conditions database. Backup mechanism needs to be developed.


  • Archive run conditions
    • Collect relevant information from multiple sources during run and archive.
    • estimate 10 man-week effort.
    • Status:
      • Most if not all can be stored in the to-be-developed conditions database. Backup mechanism needs to be developed.


  • Out of band events
    • Develop server to insert out-of-band events into the event stream.
    • estimate 6 man-week effort.
    • Status:
      • Same idea as was done for CLAS.


  • Translation table
    • Implement translation table in JANA.
    • estimate 3 man-week effort
    • Status:
      • Prototype translation table exists.


Other (Low Priority) Projects Suitable for Outside Groups

  • Process monitoring
    • Develop process monitoring system.
    • estimate 4 man-weeks effort.
    • Status:
      • Have example from CLAS.


  • Hardware monitoring
    • Develop computer hardware monitoring system.
    • estimate 6 man-weeks effort.
    • Status:
      • Vardan has many ideas.


  • Remote monitoring of experiment
    • Develop system to allow remote monitoring of histograms, EPICS data, etc.
    • May be different mechanism for EPICS data, hist, etc.
    • estimate 12 man-weeks effort.
    • Status:


  • Info Server for generic information storage and retreival
    • Investigate and define role for generic cMsg-based info server (a la CLAS), implement if useful.
    • estimate 2 man-weeks effort design, 6 man-weeks implement.
    • Status:


  • Level 3 algorithm
    • Develop L3 rejection algorithm for use in JANA online framework.
    • estimate 26 man-weeks effort.
    • Status:
      • MIT group is interested and has experience from LHCb.


  • RootSpy development
    • Further develop RootSpy package, including mini-HBook feature.
    • estimate 6 man-weeks effort.
    • Status:
      • See Dave L's note for suggested improvements.
      • Summer student worked on mini-HBook.
      • Northwestern Univ. interested.


Other (Low Priority) Projects Suitable for Local Groups

  • Top-level experiment control control system and gui
    • Develop top-level experiment control configuration and associated gui.
    • Combines run control and slow controls into one interface.
    • estimate 6 man-week effort.
    • Status:
      • Vardan best suited to do this, not needed unti after 2015.


  • Event stream reorderer
    • Develop code to reorder events after monitoring or level 3 farm.
    • estimate 4 man-week effort.
    • Status:
      • Not sure this is needed.


In progress

  • Event disentangler
    • Develop Hall D specific event disentangler capable of handling full luminosity.
    • Determine where it should run (ROC, EB, both?).
    • estimate 6 man-week effort.
    • Status:
      • Carl best choice, he's done some work on this already.