lorentz:marki:builds> pwd
lorentz:marki:builds> find . -maxdepth 3 -name \*x312



b1pi runs successfully on lorentz at low statistics


Suggestions from committee, software review

  • look into clang: it has a thread-unsafe finder, and a stack analyzer

Questions from committee, software review


All Halls:

What # times to reprocess was assumed in the storage and CPU estimates?

Discuss your tools for software quality assurance.

Hall B/D:

Describe your system for cataloging and managing the data (including data quality)?

Hall D:

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?

Hall B:

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?


software review preparation, April 27, 2012

Not sure about the date.

According to Matt:

  • 20 kHz raw event rate
  • 1/10 of that is data we analyze
  • 1/100 of that is what we fit for a single channel


  • I: 1 PAC month, hardware check-out, see beam, 10^6 photons/s
  • II: 1 PAC month, commissioning
  • III: 2 PAC months, physics
  • IV: high intensity, with level 3 trigger

error trying to upload pptx to mediawiki

Here is the error:

Files of the MIME type “application/x-opc+zip” are not allowed to be uploaded

Lots of advice on the web, but not much help.


Software Review Planning Meeting, January 27, 2012

Responses to Manpower estimate request:

Curtis: PaulM WillL CurtisM
Franz: Franz
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