UCSB Module Checklists

The UCSB Module Checklist application is a CGI program that queries the TrackerDB for information about a module, accepts some input from the ARCS test operator, and saves the data locally.

• Purpose

  The checklists are useful for two reasons:

  1. The ARCS test operator records the channel faults for the module. This diagnosis need not match the ARCS diagnosis. Remember that the faults determined by ARCS are only as accurate as the fault finding algorithm implemented in the code. For example, every once in a while a good channel will be flagged as a one sensor open. ARCS will flag this channel as a one sensor open, but the test operator can choose not to enter it in the checklist. The checklists can be used in this way to provide a check against the ARCS algorithm. Comments can also be recorded, and are very useful for strange cases. Of course, the information recorded in the checklists is only as good as the operator who entered it.
  2. Checklists are saved locally and can be accessed without need for the TrackerDB. If the TrackerDB was working properly when the checklists was loaded, then all the information is saved locally. If the TrackerDB is down when the checklist is loaded there will be missing data, but the checklist will still load. In either case the bad channels and comments can be recorded, so testing can function without the TrackerDB in an emergency situation.
• Creating a new checklist

  New checklists can only be created from inside the clean room. the URL is:

  	http://128.111.0.13

• Searching existing checklists

  Existing checklists can be accessed inside the clean room from the URL:

  	http://128.111.0.13

  They can also be accessed outside the clean room from the URL:

  	http://smuon.physics.ucsb.edu

• Checklist Versions

  The checklist format was changed at some point in time, so there are version 1 checklist and version 2 checklists. All production modules should have a version 2 checklist. Some older modules have version 1 checklists.