GLAST The Gamma Ray Large Area Space Telescope

T&DF System Test Group

Electronics Test Group meeting minutes (5/24/04)

In attendance:

Susan Becker, Rama Chirayathumadom, Van Clark, Ric Claus, Erick Delage, Eric Hansen, Mike Huffer, Suchit Kaul, Igor Kouzmenko, Larry LeCrone, Mark McDougald, Amedeo Perazzo, Gregg Thayer, Jana Thayer

New meeting time:

Monday, 10-11 AM, every two weeks. Next meeting is in Group C conference room on June 7, 2004.

Things discussed:

1) Group structure:

There exists an ELX/hardware test group formerly lead by Mike and now lead by Jana and a FSW test group led by Eric Hansen. Both groups fall into the System Test Group formerly lead by Mike and now lead by Jana. The system test group is responsible for delivering to I&T a working set of hardware and software including the test scripts and test hardware that will allow I&T to verify that the delivered system works.

2) Introductions:

People said who they were and what they were working on.

Susan Becker -Technical writing (Mike's documents binder)

Rama - Python test scripts, TEM and GEM

Van Clark - Technical writing

Ric Claus - Visiting from I&T

Erick - GUI interface, python test scripts for AEM, PDU

Eric - Flight Software Test Lead

Mike - Grand Pooh-Bah of hardware

Suchit - GUI interface, python test scripts

Igor - FSW tester

Larry - Technical writing

Mark - Testing the great GASU

Amedeo - GASU testing

Gregg - Environmental monitoring and testbed development

Jana - ELX test; System test

3) New room 101 practices:

  • For those developing python test scripts (for ELX group), the V:/ drive has been restructured. Each user now has a personal area in v:/glast/electronics/users for code development. All of their present code should be copied to this area and all further development will be done here.

  • The ELX directory is no longer a valid place to develop code. It's usage will become more clearly defined when CVS is implemented. More on that in two weeks...for now, nobody panic. I will consult with the I&T guys before doing anything, and I will give specific "how-to" instructions to the developers who will need to put their code into CVS.

  • Anyone that wants to run one of the teststands in room 101 needs to learn the new "system" for starting RunControl. To start run control, go to the directory for your particular test stand and double click on the StartRunControl icon: V:\glast\Electronics\teststands\<teststand>\StartRunControl. Alternatively, you can run it from the command line by typing v:\glast\Electronics\teststands\<teststand>\runcontrol.bat -c v:\GLAST\Electronics\teststands\<teststand>\runcontrol.cfg

Contact Jana or Amedeo if you experience any problems with this.

  • Anyone who has not used a teststand in room 101 in the last two weeks, should ask Jana for a personalized tour of how to turn on the test bed in a safe manner. If you don't know how to do something or aren't sure or don't remember, please ask!

4) Resource sharing:

Yes, we have limited resources. Yes, we need to figure out how to share them. The low-tech solution is a white board in room 101 with the days of the week and the hours of the day blocked off; people can sign up for time slots. HOWEVER, until the configuration in the room is stable and the hardware is verified to be working, the room is an ELX lab, NOT a generic test lab.

Minutes submitted by Jana Thayer.

Home | Mike's Binder |Members | FAQs

Page owner: Susan Becker
Last modified: 02/06/2006 3:58 PM

 

SLAC