| PTCS Tests |
| Semester 08B |
|---|
| Band | Task | Shifts | Conditions | Hours required * | *Comments |
|---|
| Q | HALFP | nighttime | B | 2 * 3 hrs | QD/Tracking tests during nighttime, but varying wind conditions |
| none | TILT | midnight-5 | C | 5.2 hrs (can be backup proj.) | Slow azimuth scans to measure changes in track tilt |
| Ka/Q | OOF | evening | A | 1 * 3 hrs | Test new OOF script automation under thermally moderate conditions |
| Ka/Q | OOF | daytime | B | 1 * 6 hrs | Test new OOF script automation under thermally extreme conditions |
| Ku | HOLO | anytime | B | 2 * 4 hrs (early June) | Test holo reference receiver (no turret slot needed) |
| Ku | HOLO | nighttime | windless, overcast | 3 * 8 hrs (July) | Intermediate resolution holography maps (w/turret slot for ~2weeks) |
| Ku | HOLO | nighttime | windless, overcast | 3 * 8 hrs (August) | High resolution holography maps (w/turret slot for ~2weeks) |
| X | SERVO | anytime | D | 4 * 4 hrs | Test servo improvements, need to move antenna. Slots should be spread out among the months |
| X | SERVO | anytime | D | 2 * 4 hrs (late Aug) | Test servo improvements, need to move antenna |
| Total | | | | 100 hours | |
NOTE: if the month is not specified, it can be any. Please avoid June 9-22 and Sep 24-28.
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.
|
| Calibration Project Tests |
- 3 sessions of 4 hours each (12 total hours) are requested. Will use either S, C or X-band depending on availability and weather. (ToneyMinter - 07 Nov 2007)
|
| Spectral Baseline Tests |
|
|
| Other Electronics Tests |
|
|
| Software Tests |
Planning cycles for 08B include:
- Cycle 4: - Requested release date: June 25, 2008
- Cycle 5: - Requested release date: August 13, 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 - 17 Mar 2008
|
| Receiver Maintenance |
- PF1 - Two weeks in the lab in fall.
|
| Pulsar Dream Machine Testing |
|
-- ScottRansom - 16 Jul 2007
|
| General Maintenance |
- Jun 1 - Aug 30
- Four fixed maintenance days per week, Mon through Thu 07:00 - 17:30 EDT
- Sep 1 - Sep 30
- 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 |
|
|
| 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
|
)