NRAO Home  >  Green Bank  |  Wiki Topic:    GB > Software > PlanOfRecordC32006 > ModificationRequest10C306
   Changes | Index | Contents | Search | Statistics | Go

Implement CCB Self-Test

Modification Request #10 (C03 2006)



1. Introduction

Backends that have the capability of producing stable, internally-generated signals provide the opportunity to implement end-to-end self-tests to validate the unit's signal processing. Such tests are invaluable for operations, engineers, and observers by providing go/no-go status for backends. The intent is to write a self test for the CalTech Continuum Backend similar to the self tests for the SpectralProcessor and Spectrometer.

2. Background

See CCB Gap Analysis

3. Requirements

A project description, version 1.6, provides details.

4. Design

A Python program, CCBtest, which takes one command-line argument specifying the unit to be tested, either CCB26_40 or CCB68_92 will autonomously run the test, write to standard error a message summarizing of the results, return the number of errors detected, and write a file detailing the errors in /tmp/device_name.unique_id which will be specified in the error message. This design facilitates the implementation of a "self-test" button on the CLEO interface, as well as allowing the program to be run directly from the command line.

Only mismatches between the canonical FITS file and the generated FITS files in fields which are dependent on the generated data or device configuration will generate a failure.

5. Deployment Checklist

Because the program will be part of the CCB control code in Ygor and installed in apps as are other python applications, standard Ygor build and install procedures should be sufficient.

RonMaddalena has indicated that the requirements and architecture are satisfactory, and he will integrate the self test into CLEO as feasible some time before the beginning of high frequency season.

From past experiences with both the Spectral Processor and the Spectrometer self tests, no observer documentation is required. However a wiki page describing the running of the CCB self test from a command line will be written and a link to it will be created in the ElectronicsKnowledge page.

6. Test Plan

The program will be verified by repeating the test with no failures and then generating a failure by removing a daughter card. The device should return to the previous configuration after each test.

The CCB will be operational in the receiver lab for the summer, therefore no problem is anticipated in acquiring needed test time.


Signatures

APPROVED: I acknowledge that my request is fully contained in this MR, and if the SDD delivers exactly what I specified, I will be happy.

ACCEPTED: I acknowledge that I have validated the completed code according to the acceptance tests, and I am happy with the results.

Written DONE MarkClark - 19 May 2006
Checked DONE MelindaMello - 23 May 2006
Approved by Sponsor DONE BrianMason - 25may06
Approved by CCC DONE AmyShelton - 03 Jun 2006
Accepted/Delivered by Sponsor DONE Brian Mason 22jun06

Symbols:


CCC Discussion Area

Topic ModificationRequest10C306 . { Edit | Attach | Ref-By | Printable | Diffs | r1.14 | > | r1.13 | > | r1.12 | More }
Revision r1.14 - 22 Jun 2006 - 15:34 GMT - BrianMason
Parents: PlanOfRecordC32006
Content copyright © 1999-2007 by the contributing authors.
All material on this collaboration platform is the property of the contributing authors.