Transcript ppt

Handling Bad Strips
Leon and Joanne
Requirements
•Use conversion services to get from persistent (XML) form to
TCDS; handle updates as event time increases “automatically”
•Little or no change to existing algorithmic code required
•Allow description to call an entire component bad or
enumerate individual strips (or both).
22 Jan 2003
2
data
Existing Architecture
control
algorithm
algorithm
Tkr Service
Ascii
file
22 Jan 2003
The persistent form of the data is an ascii
file listing bad strips. A Gaudi service is
responsible for reading in the file and
maintaining a corresponding in-memory
data structure which algorithms can access
3
data
Proposed Architecture
algorithm
control
Tkr Service
TCDS
classes
Metadata
rdbms
XML
files
22 Jan 2003
Calibration
conversion
services,
converters
algorithm
Persistent data is kept in XML files. Each file is
described with metadata. Metadata cnv service
searches for the ‘right’ dataset. Format-specific
cnv service invokes converter to create or
update TCDS information.
Once per event Tkr svc asks for update. If data
has been refreshed, it will then recreate its own
representation.
As before Tkr svc makes data available to
algorithms.
4
To do
•Design (round 2) XML format and TCDS hot/dead strips classes
[Joanne]
•Modify tkr service to fetch TCDS data and generate something
like current data structure [Leon]
Everything else (tkr service interface to algorithms, calibration
infrastructure underpinnings) is done, sort of.
22 Jan 2003
5