Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2006-07-14 09:12:32 →
Size: 6872
Editor: kleinplanet
Comment:
← Revision 3 as of 2006-07-14 09:15:14 → ⇥
Size: 6852
Editor: kleinplanet
Comment:
Deletions are marked like this. Additions are marked like this.
Line 144: Line 144:
  - some specific photometer tests, like the thermal behaviour
    measurements, start directly out of SAFE mode, while most
    of the tests will be executed after the '''PHOT_setup'''
  - the above mentioned CUS scripts (with a few exceptions) have been
    tested and are available in the CUS database and from the
    CVS library[[BR]]		   - some specific photometer tests, like the thermal behaviour measurements, start directly out of SAFE mode, while most of the tests will be executed after the '''PHOT_setup'''
  - the above mentioned CUS scripts (with a few exceptions) have been tested and are available in the CUS database and from the CVS library[[BR]]

TableOfContents(2)

PACS bolometer operation from the commanding point of view

T. Mueller, D. Cesarsky; 19-May-2006

1. Instrument switch-on and connection of the warm electronic boxes

- currently done with tcl-script PACS_Switch_On.tcl (maintained by FGB)BR - after execution: PACS is in SAFE mode

2. Cooler recycling (only at HeII temperatures)

- starting out of SAFE modeBR - CUS script: BOLO_cool_recycle (no sub-procedures are called)BR - ending up in SAFE modeBR

3. General Setup for Photometer Operation (at warm, HeI, HeII temperatures and after cooler recycling)

- starting out of SAFE modeBR - CUS script:BR

  • block PHOT_setup calling the following CUS procedures (will be renamed to PHOT_orbit_prologue):

    • - procedure PHOT_dpu_dmc_setupBR - procedure PHOT_dmc_setupBR

      • - procedure PHOT_fltw_conf (*)BR - procedure CONF_chopper (*)BR - procedure CONF_cs (*)BR

      - procedure PHOT_set_bias (*)BR - procedure PHOT_seq_setupBR - procedure PHOT_change_data_modeBR - procedure PHOT_change_seq_modeBR - procedure PHOT_set_gainBR - procedure PHOT_spu_setupBR

  • (*) certain parameter values depend on the temperature environment!BR

  • - ending up in PHOTOMETRY mode, but SPU processing has not yet startedBR - Note: filter is in position "A", chopper at position "0"BR - calibration sources are set to default values, but need 30-40 min stabilisation time!!!BR

4. Operation of the bolometers (starting out of PHOTOMETRY mode)

4.1. start/stop of bolometer data flow

  • CUS scripts:BR

    • - procedure PHOT_spu_setup ---> bolometer data flow running BR - procedure PHOT_spu_reset BR

4.2. Change of the bolometer data/sequence mode and gain

  • CUS scripts:BR

    • - procedure PHOT_change_data_modeBR - procedure PHOT_change_seq_modeBR - procedure PHOT_set_gainBR

4.3. Take data with manual chopper & filter movements

  • CUS scripts:BR

    • - procedure PHOT_spu_setup ---> bolometer data flow runningBR

      • - procedure PHOT_fltw_moveBR - command Pacs_DMC_MOVE_CHOP_ABSBR - command Pacs_DMC_MOVE_CHOP_RELBR

      - procedure PHOT_spu_resetBR

4.4. Take data with pre-defined OBCPs

  • CUS scripts:BR

    • - procedure PHOT_spu_setup ---> bolometer data flow runningBR

      • - block OBCP_chopped_photometryBR - block OBCP_chopped_photometry_ditherBR - block OBCP_phot_freezeframeBR - block OBCP_phot_cal_IBR - block OBCP_phot_cal_IIBR - block OBCP_phot_cal_IIIBR - block OBCP_phot_staringBR - block OBCP_phot_chopper_scanBR

      • - block PHOT_all_aots_OBSBR

      - procedure PHOT_spu_resetBR

4.5. Execute AOT observations

  • CUS scripts (to be finalised):BR

    • PHOT_AOTBR

      • - PacsPhotDefaultsBR - PacsPhotEstimatorOBCPnBR

        • - PacsDureeOBCP5BR

          • - DMC_phot_2_3_chopBR

          - PacsDureeOBCP7BR

          • - DMC_staring_photBR

        Logic chooses and issues a pointing mode out of:BR

        • - composite_noddingBR - repeated_raster_with_holdBR - line_scan_with_holdBR

        - WriteOBSIDBR - PacsPhotSlewCalBR

        • - PHOT_aot_prologueBR

          • - PHOT_spu_setupBR

          - PHOT_fltw_moveBR - OBCP_chopped_photometryBR

        - PacsPhotCommandOBCP7BR

        • - OBCP_staring_photometryBR

        - PacsPhotCommandOBCP5BR

        • - OBCP_chopped_photometry_ditherBR

        - PHOT_aot_epilogueBR - WriteEndIDBR - PacsPhotNoiseRMSBR - PacsMessageCenterBR

5. Reset after photometer operation

  • - PACS is in PHOTOMETRY or any other modeBR - going into SAFE mode:BR

    • CUS scripts:BR

      • - block OBCP_SAFEBR

    - after execution: PACS is in SAFE modeBR

6. Instrument switch-off

  • - currently done with the tcl-script PACS_Switch_Off.tcl (maintained by FGB)BR - after execution: PACS is switched offBR

7. NOTES

  • - there are more CUS scripts related to the SFT warm, HeI and HeII which are not mentioned here (see PACS-ME-TP-007)BR - some specific photometer tests, like the thermal behaviour measurements, start directly out of SAFE mode, while most of the tests will be executed after the PHOT_setup - the above mentioned CUS scripts (with a few exceptions) have been tested and are available in the CUS database and from the CVS libraryBR - the AOT related CUS-scripts are still under testing

Herschel: PACS/FM_ILT_Procedures/PhotOperations (last edited 2009-07-15 14:32:37 by localhost)