Suggestions for work

 A summary of e-mail suggestions. I have tried to organise the various suggestions by "themes", I hope
it reflects the original suggestions.


 1) Architecture 

	- Collection of parameters and standard values of interest to TDAQ.

	- Description of the current (as of July 2002) TDAQ architecture starting from material
	  submitted to and results from the TDAQ July review. 

		+ Follow data & control from ROD down to mass storage
		+ Identify major components (hardware and software)
		+ Describe component requirements (functional, performance, etc.)
		+ Identify relationships between components (boundaries & interfaces)

	- Exploit the architecture description to detect problems, inconsistencies, etc. Boundaries
	  and interfaces are a common concern
	
	- Fault tolerance: model, requirements on components

	- Diagnostics and error recovery (distribute responsibility for diagnostics & recovery to components?)

	- Network requirements from online software

	- External dependencies (e.g. where there is dependence on offline sw)

	- Cost model, global cost/performance optimisation

	- Mass storage (clarify with offline)

	- geographical layout of components



 2) Use cases

	Develop operational use cases/scenarios

		- TDAQ operations within/outside a run
		- detector/experiment commissioning
		- experiment start up
		- fault conditions (power failure, storms , faulty element). Effect on performance & physics
		- maintenance
		- physics/non physics runs
		- calibration runs (including where calibration s/w interfaces to DAQ)
		- Change of runs (physics to calibration, etc.)
		- TDAQ partition operations (defining, splitting, joining partitions etc.)
		- monitoring scenarios (ROD crate level, ROS level, full event, after EF, etc.)
		- Histogramming scenarios (ROD crate level, ROS level, after event builder etc.)

 3) Common base libraries and software

	Identify areas where common software solutions may be applied system wide (viz. buffer management)


 4) Common issues related to online sw

	- Control & supervision of farms (L2 and EF) as well as other components (ROS, DFM, etc.)
	- Database: configuration, conditions, online bookkeeping, others(?). What are the contents, what is used
	  when by whom. 
	- Access to data bases (direct, via run control, etc.)
	- Access to online services: common to all components?

 5) Test beds

	- Suggest measurements to be done on test beds/vertical slice prototypes in order to validate the
	  architecture

 6) Contribution to TDR

	- which one?