Differences between revisions 1 and 27 (spanning 26 versions)
⇤ ← Revision 1 as of 2009-07-12 10:41:34 →
Size: 749
Editor: visitor4
Comment:
← Revision 27 as of 2009-09-21 10:18:36 → ⇥
Size: 4185
Editor: visitor9
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Line 5: Line 4:
Intended Audience: IRAM staff astronomers

Schedules: [[http://www.iram.es/IRAMES/mainWiki/AstronomerOnDutySchedule|AoDs]], [[http://www.iram.es/IRAMES/groups/operator/opesched.htm|Operators]], [[http://www.iram.fr/IRAMFR/PV/sche/sche.html|Projects]]
Line 7: Line 9:
   * Check the observing schedule. If there are any TBD intervals, please contact Clemens Thum to clarify their usage.
   * Do test observations after the Tuesday maintenance period (T02-09): Let the operators tune to the frequencies of the following project. Do a quick calibration and pointing. Connect the spectrometers and do a quick position switched test observation (onoff).		    * Make yourself familiar with the present '''system status''' by reading the [[http://www.iram.es/IRAMES/mainWiki/TelescopeSystemStatus|status page]], previous reports, and by asking staff, in particular also Juan Penalver. Which backends are available ? Had there been receiver related problems lately ? When was the last pointing session ?
   * Check the '''[[http://www.iram.fr/IRAMFR/PV/sche/sche.html|observing schedule]]'''. If there are any TBD intervals, please contact Clemens Thum or the station manager to clarify their usage.
   * Do test observations after the Tuesday maintenance period ('''T00-09'''): Let the operators tune to the frequencies of the following project. Do a quick calibration and pointing. Connect some spectrometers (at least WILMA and VESPA), and do a quick position switched test observation (onoff). Use a strong line calibrators (e.g. from the Mauersberger catalogue) for this. Test the band combinations used by the next project. Check that Nasmyth offsets are correctly set. Beware that during one hour, only a brief test of the basic functionality can be done.
Line 10: Line 13:
 * The weekly report to be send at the end of each AoD week, should address the following topics:
   * Pointing/Focus
   * Receiver
   * Backend
   * Computers
   * Other remarks		  * During the week:
   * Speak with the observers and operators to check and discuss any problems. Do not hesitate to contact other staff.
   * Remind the observers to check the frequency tuning by observing a line calibrator with strong and known lines (e.g. DR21, W3OH, !OriIrc2, etc.).
   * Get an idea of the pointing situation.
     * How large are the observed offsets ?
     * Are pointing & focus affected by anomalous refraction ?
     * In case of large pointing jumps:
       * If the jump is only in elevation, check that the relative humidity is read from the weather station. This is used to calculate the refraction correction.
       * Check that the pointing constants p4/p5 do not show jumps [[https://gra-lx1.iram.es/munin/iram.es/telescopeStatus/antennaInclinometer.html|here]]. These may indicate problems of the inclinometers.
   * Update the [[http://www.iram.es/IRAMES/mainWiki/TelescopeSystemStatus|status page]].
   * Take a look at the cable spiral, telescope tower, and receiver cabin at least once during the AoD week.
   * In case MAMBO2 is used: please check the dedicated [[http://www.iram.es/IRAMES/mainWiki/BoloChkList|MAMBO2 Checklist]].

 * The weekly report to be send at the end of each AoD week, should address the following topics. Please add eps files to your report, to better explain any problematic spectra, etc.. Better start writing the report already on the first day of the AoD week, and not at the very last moment. Report what is not working, but also changes to the positive. There is no need to repeat any daily operator reports. The report shall be send to '''aodreportlist AT iram.es''' .
   1. '''Pointing/Focus'''
   1. '''Receiver'''
   1. '''Backend'''
   1. '''Computers'''
   1. '''Software/Documentation'''
   1. '''Scheduled projects (T00, other technical projecxts (TT), Astronomy)'''
   1. '''Other remarks'''

 * The above list assumes that you are familiar with the system:
   * Computers, Printers
   * Basic working of pako, odp/mira, class, greg
   * Basic security rules (Operators, Juan)
   * Observatory information for the guest observers
   * Basic IRAM web pages, wikis.
   * See the [[http://www.iram.es/IRAMES/groups/astronomy/ChecklistAoD.pdf|AoD Training Checklist]] maintained by Manolo
   * See the [[https://mrt-lx1.iram.es/mainWiki/OperationNotesAod|NCS Operations Notes]] maintained by Hans
   * To create the pointing and focus corrections distribution see: [[https://gra-lx1.iram.es/mainWiki/MopsicPointingMonitor]] and [[https://gra-lx1.iram.es/mainWiki/MopsicFocusMonitor]] maintained by Carsten and Robert





   

Weekly Checklist of Astronomers of Duty

This is page http://www.iram.es/IRAMES/mainWiki/AstronomerOfDutyChecklist maintained by CK. Intended Audience: IRAM staff astronomers

Schedules: AoDs, Operators, Projects

  • At the begin of the AoD week:

    • Make yourself familiar with the present system status by reading the status page, previous reports, and by asking staff, in particular also Juan Penalver. Which backends are available ? Had there been receiver related problems lately ? When was the last pointing session ?

    • Check the observing schedule. If there are any TBD intervals, please contact Clemens Thum or the station manager to clarify their usage.

    • Do test observations after the Tuesday maintenance period (T00-09): Let the operators tune to the frequencies of the following project. Do a quick calibration and pointing. Connect some spectrometers (at least WILMA and VESPA), and do a quick position switched test observation (onoff). Use a strong line calibrators (e.g. from the Mauersberger catalogue) for this. Test the band combinations used by the next project. Check that Nasmyth offsets are correctly set. Beware that during one hour, only a brief test of the basic functionality can be done.

  • During the week:
    • Speak with the observers and operators to check and discuss any problems. Do not hesitate to contact other staff.

    • Remind the observers to check the frequency tuning by observing a line calibrator with strong and known lines (e.g. DR21, W3OH, OriIrc2, etc.).

    • Get an idea of the pointing situation.
      • How large are the observed offsets ?

      • Are pointing & focus affected by anomalous refraction ?

      • In case of large pointing jumps:
        • If the jump is only in elevation, check that the relative humidity is read from the weather station. This is used to calculate the refraction correction.

        • Check that the pointing constants p4/p5 do not show jumps here. These may indicate problems of the inclinometers.

    • Update the status page.

    • Take a look at the cable spiral, telescope tower, and receiver cabin at least once during the AoD week.

    • In case MAMBO2 is used: please check the dedicated MAMBO2 Checklist.

  • The weekly report to be send at the end of each AoD week, should address the following topics. Please add eps files to your report, to better explain any problematic spectra, etc.. Better start writing the report already on the first day of the AoD week, and not at the very last moment. Report what is not working, but also changes to the positive. There is no need to repeat any daily operator reports. The report shall be send to aodreportlist AT iram.es .

    1. Pointing/Focus

    2. Receiver

    3. Backend

    4. Computers

    5. Software/Documentation

    6. Scheduled projects (T00, other technical projecxts (TT), Astronomy)

    7. Other remarks

  • The above list assumes that you are familiar with the system:

AstronomerOfDutyChecklist (last edited 2016-12-06 13:48:19 by CarstenKramer)