Online telecon notes for February 5,
2003
Attending:
- Connie Houchens (GSFC/ACD)
- Sharon Orsborne (GSFC/ACD)
- Glen Ungar (GSFC/ACD)
- Byron Leas (NRL/CAL)
- Johann Cohen-Tanugi (INFN
Pisa/TKR)
- Luca Latronico (INFN
Pisa/TKR)
- Mike Huffer (SLAC/ELX)
- Larry Wai (SLAC/I&T-IFCT)
- Selim Tuvi
(SLAC/I&T-Online), minutes author
- Ric Claus
(SLAC/I&T-Online)
Topics:
q
Saving system state in the event data file that is
shared with CAL offline people
q
Online needs to support transporting collected data to SAS
1.
Official plan is to use FITS files
2.
In light of Byron’s Considering storing Meta data as part of the
FITS file
- Sharon:
Okay to use setReg/getReg instead of node.attr syntax?
q
Online tried to preserve the SCL way of writing
scripts/syntax.
q
Selim doesn’t consider setReg/getReg to be internal
methods, so okay to use them
q
Would like to have a preferences feature for configuring
RunControl
1.
The plan was to use the runControl.cfg file method Selim
provided
2.
Agreed that a GUI interface to this file from the RunControl
menu bar would be nice. Johann
volunteered to look into it
q
Would like the ability to run several applications
successively against a given hardware configuration without repeatedly loading
the schema/config file
1.
Online will look into this, but the expectation has been that this
would be handled through an application that comprises a suite of tests. Determining which test to run would be up to
the application (e.g. pop up a GUI to ask, loop over all of them, etc.)
q
Would like to make available on the TKR page of
RunControl a testsuite GUI and a per-test GUI
- Byron:
- Is
a schema attached to a specific instance of hardware elements or a
hardware configuration in which the individual elements can be exchanged
freely?
q
Intention was the latter: A schema would be applied to
a combination of hardware components, irrespective of the components’ serial
numbers. Expected serial numbers were
software readable to build the pedigree of individual parts.
q
Mike: Software readable serial numbers was floated and
shot down due to cost
q
Will have to depend on the tracking of parts
administratively (entry as script parameter and hand written on the associated
traveler)
q
Complicated by the fact that the serial number of some
parts, e.g. the TEM, is not visible in all cases and that there is no guarantee
that components and their enclosures will always be kept together
q
Serial numbers will need to go into the test reports
- TKR (Luca
L.)
- Testing
MCM from Santa Cruz. Using command
line scripts (vs. scripts written against the RunControl framework) are
working.
- Integrated
hippo with these scripts.
- One
script modified to work in the RunControl framework.
- Observed
bug mentioned above as well
- Test
results to be posted on the TKR web page (Link?)
- Final
script will be posted to CVS.
- CVS
problems from Italy. Will check permissions.
- Problems
compiling sip
- Should
not need to do this. All
relevant dlls are in the Online/DLLs directory. Likely that the PYTHONPATH
environment variable is missing an entry
- TKR
Bias current measuring zero. Mike/Leonid will check.
- Bias
current readout was shown to work at SLAC
- Readout
of bias current is per tower
- TKR (Johann)
- RunControl
code bug discovery.
- Bug
fixed
- Redo
design of the base class to interface more generically with RunControl
- Preferences,
mentioned above. Volunteered for this task
- GUI
that should come with the base class.
- Planning
to work on GUI for front-end configuration
- Byron:
Suggest that the state of the system be restored to the schema/config
file specified configuration after each run
- CAL (Byron)
- Has
Online looked into the Hippo problem he reported earlier? Low priority request.
- Working
on Calibration/Trends database information for SAS people.
- Hardware:
Coordinating with Jim Ampe
- Worked
on converting some scripts to the RunControl framework
- ACD
(Sharon)
- More
Qt and PyQt licenses needed for 2-3 developers.
- VS.NET
CDs shipped to Byron today.
- Distribution
of the software that ACD wrote.
- Glen:
- Asks
for ICD document. Online will
consider revisiting this after the iCDR.
- What
should the ACD tests do? Who is
the customer?
- Larry:
- Tests
will be run by IFCT
- End
item data should be provided.
- Pushing
on TKR, since they are expecting TKR engineering module to arrive at
SLAC.
- Byron
- First
requirements documentation should arrive and then the software
- Level
4 requirement for documentation
- Ric:
Post meeting note: See Eduardo’s presentation from the Online workshop
and his document LAT-MD-00446-04
for tests expected from the ACD
- Larry
expects subsystem scripts to show up incrementally for integration by
the IFCT group
- Byron: This is not the model he’s working
against
- Sharon:
People will be able to retrieve snapshots of subsystem software from CVS
- Asks
documentation on setting up CVS. Selim will provide instructions.
- ELX (Mike)
- 5
prototype LCBs arrived.
o
It hasn't been decided whether to send the DOA TEM back. Relevant people away until next week.
o
Due to lack of connectors, Mike requests that it be
sent back to SLAC
o
Test stand equipment sent to UCSC. Request for someone from UCSC to attend these
meetings
o
30 page memo sent to Dave Thompson. Received no response.
o
Heads up for G2 impending arrival. Goddard needs to
prepare for it because of the incompatibility with G1.
o
Glen: Connectors ordered.
o
Connie, Sharon & Bob Baker will use G2 hardware.
o
Expect to receive 4 instances. At odds with Gunther’s plan. Glen and Gunther to work it out.