>
> |
%META:TOPICINFO{author="CarlBignell" date="1178889480" format="1.0" version="1.1"}%
%META:TOPICPARENT{name="WebHome"}%
- 1 June: Call for Proposal Deadline
- 10 June: Proposals distributed to scientific and technical referees
- 5 July: Test (hardware, software, etc) and Commissioning trimester time estimates due
- 16 July: Proposal reviews (scientific and technical) deadline
- 7 August: Proposal Selection Committee meets
- 17 August: Proposal dispositions emailed
- 1 September: Draft call for 08A proposals
- 1 September: Start constructing October through January astronomical schedule
- 7 September: 08A Call for proposals released
- 30 September: January schedule finalized
|
All activities which will impact the amount of astronomical time available for this
trimester should be briefly outlined below. This includes commissioning, specific equipment tests, and
all maintenance requirements as well as receiver and backend availability during this period.
|
| PTCS Tests |
| Semester 07C - 1st October through 31th January |
|---|
| Band | Task | Shifts | Conditions | Tentative Dates | Comments |
|---|
| X | PNT | | A | Pref | Pointing checks under benign conditions, schedule ~ two weeks apart. |
| X | PNT | | C | Pref | Pointing checks under all conditions, schedule after above, and ~ two weeks apart. |
| Ka/Q | OOF | | A | Pref | Test new OOF techniques under thernally benign conditions |
| Ka/Q | OOF | | B | Pref | Test new OOF techniques under thernally extreme conditions |
| X | SERVO | 0.5 * 4 | D | Any | Four hour chunks to test servo improvements, need to move antenna |
NOTE: in the above table "1 shift" means one 8 hour observing shift, on average.
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 07C requirements: 0 hours.
|
| High Frequency Instrumentation (Ka, Q, Zpectrometer, CCB, Penn Array) Tests |
|
|
| Spectral Baseline Tests |
|
|
| Other Electronics Tests |
|
|
| Software Tests |
Planning cycles for 07B include:
- Cycle 7: - *Requested release date: *
- Cycle 8: - *Requested release date: *
- Cycle 9: - *Requested release date: *
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.
- Notes: The commissioning time could be used for calibration tests, pointing, etc. The theory is that if the four 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 four 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.
Only assign integration and regression testing outside of maintenance hours during the track shutdown if telescope motion is allowed. Otherwise, we will do our integration and regression testing during maintenance days.
-- AmyShelton - 11 May 2007
|
| Receiver Maintenance |
- PF1 - Two weeks in the lab in fall.
|
| General Maintenance |
- Oct 1 - Jan 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
|
|
|
| Gain Calibration |
|
?
-- Frank Ghigo and Ron Maddalena
|
| 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
|
-- CarlBignell - 11 May 2007 |
), Oct 1 (