project management updates to timeline
mock data challenge
daq Sergey B.:
install oct nov
beam mid nov
next year spring, real data
how is pilelined read-out handled
Bruce would like to delay from March 1. We discussed the following Fri., March 8 as a good day. Paul said Fridays are good for him.
0. in production now, problems hsould be addressed soon
1. software button
proceed with current procedure for now
JLab: fix this, resources should be found
2. Auto analysis
3. board end-to-end with one cres
4. schedule needs to be developed
5. board 9
6. 10 board run through, including shipping
7. shipping concern: size of evelope
8. work schedule
9. problem boards sent quickly to JLab
Recommendations: 2, 6, 9
What # times to reprocess was assumed in the storage and CPU estimates?
Discuss your tools for software quality assurance.
Describe your system for cataloging and managing the data (including data quality)?
At what level of parallelism will serial l/O R/W hit a limit?
What is the planned latency between data acquired and completed calibrated reconstruction?
Provide a written outline of a plan for data challenges including scaling up end-to-end processing to a reasonable fraction of production running.
What information is included in the large amount of reconstructed data? Why do you need the reconstructed data for the full sample?
Responses to Manpower estimate request:
Curtis: PaulM WillL CurtisM
Richard: prof, staff scientist, grad studentX5 (3 on analysis)
Volker: Volker, Nathan, possible new student
online vs offline in review: Curtis noticed this in Sandy’s slides check into this
Possible sources of manpower
ryan: framework for dst analysis
regina: now that construction is over
software development, not analysis in manpower estimate
put next meeting on the calendar