| PTCS Tests |
| Semester 08A - 1st Feb through 31th May |
|---|
| Band | Task | Shifts | Conditions | Hours/Month * | *Comments |
|---|
| Ka | PNT | 22:00-08:00 | A | 10 hrs | Pointing check under benign nighttime conditions |
| Ka | PNT | daytime | B | 8 hrs | Pointing check under benign daytime conditions |
| Q | HALFP | nighttime | C | 3 hrs | Tracking tests during nighttime, but varying wind conditions |
| none | TILT | nighttime | C | 5 hrs (can be backup proj.) | Slow azimuth scans to measure changes in track tilt |
| Ka/Q | OOF | nighttime | A | 1 * 4 hrs | Test new OOF techniques under thermally benign conditions |
| Ka/Q | OOF | daytime | B | 2 * 3 hrs | Test new OOF techniques under thermally extreme conditions |
| Ku | HOLO | anytime | B | 2 * 4 hrs Feb | Test traditional holography system integrity and phase stability |
| Ku | HOLO | evening | B | 2 * 4 hrs Mar | Coarse resolution holography maps |
| Ku | HOLO | nighttime | A | 2 * 6 hrs Apr/May | Intermediate resolution holography maps |
| X | SERVO | anytime | D | 4 * 3 hrs | Test servo improvements, need to move antenna. Slots should be spread out among the months |
| Total | | | | 76 hours | |
NOTE: if the month is not specified, it can be any.
A - clear skies (low opacity), low wind (less than 2.5 m/s), thermally stable (00:00 - 08:00)
B - clear skies (low opacity), low wind (less than 2.5 m/s).
C - clear skies (low opacity)
D - any observing weather.
E - can be done in parallel with maintenance, but needs antenna at access and M&C available.
When scheduled this work may exceed the time required for other maintenance activities.
Total 08A requirements: = hours.
|
| High Frequency Instrumentation (Ka, Q, Zpectrometer, CCB, Penn Array) Tests |
- 1 hour to test subreflector nodding for Q-band. (DjPisano - 01 Nov 2007)
|
| Tests for Phoenix Mars Lander Project |
- 4 hours with 450 MHz prime focus receiver, most likely in February. (FrankGhigo - 07 Nov 2007)
|
| Spectral Baseline Tests |
|
|
| Other Electronics Tests |
|
|
| Software Tests |
Planning cycles for 07C include:
- Cycle 1: - Requested release date: February 13, 2008
- Cycle 2: - Requested release date: April 2, 2008
- Cycle 3: - Requested release date: May 14, 2008
Approximately 6-10 days prior to release date:
- Two blocks of 4 hours each for integration tests; full system and antenna. Preferably during a weekday.
Approximately 2-6 days prior to release date:
- One block of 6 hours for regression tests (full system and antenna) followed by around 8 hours of commissioning time. Preferably during a weekday.
- Notes: The commissioning time could be used for calibration tests, pointing, etc. The theory is that if the six hours of regression tests went horribly wrong, we'd revert to the current M&C version, the commissioning tests would then use the old version, and we could re-schedule. If the six hours of regression testing went well, the next eight hours would be a "sympathetic" observer using the new version, and a chance to catch/fix trivial problems. We'd revert to the current M&C version at the end of the commissioning tests.
Within +/- 2 business days of end of development cycle:
- One block of 4 hours for integration tests (to resolve/test any issues/solutions found during regression testing).
- We will schedule our release for a scheduled maintenance day. No additional time required. Ideally, it would be good to have a "sympathetic" observer scheduled to use the system directly after maintenance that day. If we have a dedicated release time rather than releasing during maintenance, we only need 2 hours.
Averages 18 hours of time per cycle.
-- AmyShelton - 02 Nov 2007
|
| Receiver Maintenance |
- PF1 - Two weeks in the lab in fall.
|
| Pulsar Dream Machine Testing |
|
-- ScottRansom - 16 Jul 2007
|
| General Maintenance |
- Feb 1 - May 31
- One maintenance day (08:00-16:30) per week dynamically scheduled (Tue/Thu)
- scheduled on alternating weeks
- priority of paired day possibilities: Tue/Thu, Wed/Fri, Mon/wed
- Two maintenance days (08:00-16:30) per week dynamically scheduled
- scheduled on alternating weeks
- priority of paired day possibilities: Mon/Wed, Tue/Thu otherwise Tue/Thu, Wed/Fri
|
|
|
| SCAL Measurements |
|
No less than 2 hrs and no more than 4 hrs per month, dynamically scheduled. When possible, every other month should be during 'nightime', as defined by the PTCS memos. Could be beneficial to schedule one or two of these sessions adjacent to PTCS's Gain Calibration tests.
-- Ron Maddalena & Jules Harnett
|
| Gain Calibration Measurements |
12 hours at Ka band with the CCB, under excellent conditions
( < 5 MPH, tau <= 0.05.)
-- F. Ghigo
|
| Balancing |
|
|
| Scheduling Constraints |
- Avoid scheduling project changes exactly at 0700 or 1900 ET to minimize operator overload
- Attempt to have project changes around 0730 and 1930 ET instead of at 0700 and 1900 exactly
- If not possible, attempt a half hour earlier around 0630 and 1830 ET
|
)