Differences between revisions 1 and 2
Revision 1 as of 2006-07-14 08:04:53
Size: 6315
Editor: kleinplanet
Comment:
Revision 2 as of 2006-07-14 09:12:32
Size: 6872
Editor: kleinplanet
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= PACS bolometer operation from the commanding point of view = #pragma section-numbers on
[[TableOfContents(2)]]

'''
PACS bolometer operation from the commanding point of view'''
Line 4: Line 7:
T. Mueller, D. Cesarsky T. Mueller, D. Cesarsky;
Line 9: Line 12:
 1. Instrument switch-on and connection of the warm electronic boxes = Instrument switch-on and connection of the warm electronic boxes =
Line 11: Line 14:
  - currently done with tcl-script "PACS_Switch_On.tcl" (maintained by FGB):
  - after execution: PACS is in SAFE mode
- currently done with tcl-script '''PACS_Switch_On.tcl''' (maintained by FGB)[[BR]]
- after execution: PACS is in SAFE mode
Line 16: Line 19:
 2. Cooler recycling (only at HeII temperatures) = Cooler recycling (only at HeII temperatures) =
Line 18: Line 21:
  - starting out of SAFE mode
  - CUS script: BOLO_cool_recycle
                
(no sub-procedures are called)
  - ending up in SAFE mode
- starting out of SAFE mode[[BR]]
- CUS script: '''BOLO_cool_recycle''' (no sub-procedures are called)[[BR]]
- ending up in SAFE mode[[BR]]
Line 25: Line 27:
 3. General Setup for Photometer Operation
    
(at warm, HeI, HeII temperatures and after cooler recycling)
= General Setup for Photometer Operation (at warm, HeI, HeII temperatures and after cooler recycling) =
Line 28: Line 29:
  - starting out of SAFE mode
  
- CUS script:
        block  PHOT_setup calling the following CUS procedures
    (will be renamed to PHOT_orbit_prologue):
               - procedure PHOT_dpu_dmc_setup
               - procedure PHOT_dmc_setup
                              - procedure PHOT_fltw_conf (*)
                              - procedure CONF_chopper (*)
                              - procedure CONF_cs (*)
               - procedure PHOT_set_bias (*)
               - procedure PHOT_seq_setup
               - procedure PHOT_change_data_mode
               - procedure PHOT_change_seq_mode
               - procedure PHOT_set_gain
               - procedure PHOT_spu_setup

    (*) certain parameter values depend on the temperature
       
environment!
- starting out of SAFE mode[[BR]]
- CUS script:[[BR]]
        block '''PHOT_setup''' calling the following CUS procedures
        (will be renamed to PHOT_orbit_prologue):
               - procedure PHOT_dpu_dmc_setup[[BR]]
               - procedure PHOT_dmc_setup[[BR]]
                              - procedure PHOT_fltw_conf (*)[[BR]]
                              - procedure CONF_chopper (*)[[BR]]
                              - procedure CONF_cs (*)[[BR]]
               - procedure PHOT_set_bias (*)[[BR]]
               - procedure PHOT_seq_setup[[BR]]
               - procedure PHOT_change_data_mode[[BR]]
               - procedure PHOT_change_seq_mode[[BR]]
               - procedure PHOT_set_gain[[BR]]
               - procedure PHOT_spu_setup[[BR]]

    (*) certain parameter values depend on the temperature environment![[BR]]
Line 46: Line 46:
  - ending up in PHOTOMETRY mode, but SPU processing has not yet
    started. Note: filter is in position "A", chopper at position "0",
    calibration sources are set to default values, but need 30-40 min
   
stabilisation time!!!
  - ending up in PHOTOMETRY mode, but SPU processing has not yet started[[BR]]
  - 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]]
Line 53: Line 52:
 4. Operation of the bolometers (starting out of PHOTOMETRY mode) = Operation of the bolometers (starting out of PHOTOMETRY mode) =
Line 56: Line 55:
     A) start/stop of bolometer data flow
        CUS scripts:
               - procedure PHOT_spu_setup
            
---> bolometer data flow running
               - procedure PHOT_spu_reset
== start/stop of bolometer data flow ==
        CUS scripts:[[BR]]
               - procedure '''PHOT_spu_setup''' ---> bolometer data flow running [[BR]]
               - procedure '''PHOT_spu_reset''' [[BR]]
Line 63: Line 61:
     B) Change of the bolometer data/sequence mode and gain
        CUS scripts:
               - procedure PHOT_change_data_mode
               - procedure PHOT_change_seq_mode
               - procedure PHOT_set_gain
== Change of the bolometer data/sequence mode and gain ==
        CUS scripts:[[BR]]
               - procedure '''PHOT_change_data_mode'''[[BR]]
               - procedure '''PHOT_change_seq_mode'''[[BR]]
               - procedure '''PHOT_set_gain'''[[BR]]
Line 70: Line 68:
     C) Take data with manual chopper & filter movements
        CUS scripts:
               - procedure PHOT_spu_setup
             ---> bolometer data flow running
                   - procedure PHOT_fltw_move
                   - command Pacs_DMC_MOVE_CHOP_ABS
                   - command Pacs_DMC_MOVE_CHOP_REL
               - procedure PHOT_spu_reset
== Take data with manual chopper & filter movements ==
        CUS scripts:[[BR]]
               - procedure '''PHOT_spu_setup''' ---> bolometer data flow running[[BR]]
                   - procedure '''PHOT_fltw_move'''[[BR]]
                   - command '''Pacs_DMC_MOVE_CHOP_ABS'''[[BR]]
                   - command '''Pacs_DMC_MOVE_CHOP_REL'''[[BR]]
               - procedure '''PHOT_spu_reset'''[[BR]]
Line 80: Line 77:
     D) Take data with pre-defined OBCPs
        CUS scripts:
               - procedure PHOT_spu_setup
             ---> bolometer data flow running
                       - block OBCP_chopped_photometry
                       - block OBCP_chopped_photometry_dither
                       - block OBCP_phot_freezeframe
                       - block OBCP_phot_cal_I
                       - block OBCP_phot_cal_II
                       - block OBCP_phot_cal_III
                       - block OBCP_phot_staring
                       - block OBCP_phot_chopper_scan
                        (not yet available!!!)
                   - block PHOT_all_aots_OBS
               - procedure PHOT_spu_reset
== Take data with pre-defined OBCPs ==
        CUS scripts:[[BR]]
               - procedure '''PHOT_spu_setup''' ---> bolometer data flow running[[BR]]
                       - block '''OBCP_chopped_photometry'''[[BR]]
                       - block '''OBCP_chopped_photometry_dither'''[[BR]]
                       - block '''OBCP_phot_freezeframe'''[[BR]]
                       - block '''OBCP_phot_cal_I'''[[BR]]
                       - block '''OBCP_phot_cal_II'''[[BR]]
                       - block '''OBCP_phot_cal_III'''[[BR]]
                       - block '''OBCP_phot_staring'''[[BR]]
                       - block '''OBCP_phot_chopper_scan'''[[BR]]
                   - block '''PHOT_all_aots_OBS'''[[BR]]
               - procedure '''PHOT_spu_reset'''[[BR]]
Line 97: Line 92:
     E) Execute AOT observations
        CUS scripts (to be finalised):
== Execute AOT observations ==
        CUS scripts (to be finalised):[[BR]]
Line 100: Line 95:
            PHOT_AOT
               - PacsPhotDefaults
               - PacsPhotEstimatorOBCPn
                  - PacsDureeOBCP5
                     - DMC_phot_2_3_chop
                  - PacsDureeOBCP7
                     - DMC_staring_phot
               Logic chooses and issues a pointing mode out of:
                  - composite_nodding
                  - repeated_raster_with_hold
                  - line_scan_with_hold
               - WriteOBSID
               - PacsPhotSlewCal
                  - PHOT_aot_prologue
                     - PHOT_spu_setup
                  - PHOT_fltw_move
                  - OBCP_chopped_photometry
               - PacsPhotCommandOBCP7
                  - OBCP_staring_photometry
               - PacsPhotCommandOBCP5
                  - OBCP_chopped_photometry_dither
               - PHOT_aot_epilogue
               - WriteEndID
               - PacsPhotNoiseRMS
               - PacsMessageCenter
            PHOT_AOT[[BR]]
               - PacsPhotDefaults[[BR]]
               - PacsPhotEstimatorOBCPn[[BR]]
                  - PacsDureeOBCP5[[BR]]
                     - DMC_phot_2_3_chop[[BR]]
                  - PacsDureeOBCP7[[BR]]
                     - DMC_staring_phot[[BR]]
               Logic chooses and issues a pointing mode out of:[[BR]]
                  - composite_nodding[[BR]]
                  - repeated_raster_with_hold[[BR]]
                  - line_scan_with_hold[[BR]]
               - WriteOBSID[[BR]]
               - PacsPhotSlewCal[[BR]]
                  - PHOT_aot_prologue[[BR]]
                     - PHOT_spu_setup[[BR]]
                  - PHOT_fltw_move[[BR]]
                  - OBCP_chopped_photometry[[BR]]
               - PacsPhotCommandOBCP7[[BR]]
                  - OBCP_staring_photometry[[BR]]
               - PacsPhotCommandOBCP5[[BR]]
                  - OBCP_chopped_photometry_dither[[BR]]
               - PHOT_aot_epilogue[[BR]]
               - WriteEndID[[BR]]
               - PacsPhotNoiseRMS[[BR]]
               - PacsMessageCenter[[BR]]
Line 128: Line 123:
 5. Reset after photometer operation = Reset after photometer operation =
Line 130: Line 125:
  - PACS is in PHOTOMETRY or any other mode
  - going into SAFE mode:
        CUS scripts:
               - block OBCP_SAFE
  - PACS is in PHOTOMETRY or any other mode[[BR]]
  - going into SAFE mode:[[BR]]
        CUS scripts:[[BR]]
               - block '''OBCP_SAFE'''[[BR]]
Line 135: Line 130:
  - after execution: PACS is in SAFE mode   - after execution: PACS is in SAFE mode[[BR]]
Line 139: Line 134:
 6. Instrument switch-off = Instrument switch-off =
Line 141: Line 136:
  - currently done with a dedicated tcl-script (maintained by FGB)
  - after execution: PACS is switched off
  - currently done with the tcl-script '''PACS_Switch_Off.tcl''' (maintained by FGB)[[BR]]
  - after execution: PACS is switched off[[BR]]
Line 146: Line 141:
 7. NOTES = NOTES =
Line 148: Line 143:
  - there are more CUS scripts related to the SFT warm, HeI and HeII
   
which are not mentioned here (see PACS-ME-TP-007)
  - there are more CUS scripts related to the SFT warm, HeI and HeII which are not mentioned here (see PACS-ME-TP-007)[[BR]]
Line 152: Line 146:
    of the tests will be executed after the "PHOT_setup"     of the tests will be executed after the '''PHOT_setup'''
Line 155: Line 149:
    CVS library     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)