! File: 5253C.PROP ! Database: PEPDB ! Date: 24-FEB-1994:03:10:39 coverpage: title_1: INITIAL FHST/RGA SCALE-FACTOR-ALIGNMENT DETERMINATION proposal_for: SME/PCS pi_fname: MARTIN pi_lname: GAKENHEIMER pi_inst: ALLIED-SIGNAL TECHNICAL SERVICES pi_country: USA pi_phone: (301)286-3932 hours_pri: 12.00 num_pri: 6 realtime: Y ! end of coverpage abstract: line_1: Starting from a specific attitude, HST will line_2: be commanded to perform a series of maneuvers line_3: around three mutually orthogonal axes in order to line_4: acquire RGA data and FHST attitudes to compute the line_5: initial FHST/RGA scale-factor-alignment line_6: matrices. The results of the analysis will line_7: be used to update the PDB and the flight line_8: software, and are necessary for future line_9: observations. ! ! end of abstract general_form_proposers: lname: BRADLEY fname: ART inst: ALLIED-SIGNAL AEROSPACE country: USA ! lname: GAKENHEIMER fname: MARTIN inst: ALLIED-SIGNAL TECHNICAL SERVICES country: USA ! lname: HALLOCK fname: LOU inst: GODDARD SPACE FLIGHT CENTER country: USA ! lname: KIMMER fname: ED inst: ALLIED-SIGNAL TECHNICAL SERVICES country: USA ! lname: WELTER fname: GARY inst: COMPUTER SCIENCES CORPORATION country: USA ! ! end of general_form_proposers block general_form_text: question: 2 section: 1 line_1: This activity is a required step in the line_2: determination of the RGA alignment and line_3: calibration parameters necessary for the line_4: proper processing of attitude sensor data in line_5: the onboard Pointing Control System and in line_6: the ground PASS software. ! question: 3 section: 1 line_1: Two sets of slews, separated by 24 hours for line_2: PASSOPS processing, are required. The first line_3: set will provide data to perform the line_4: calibration and the second set is intended to line_5: validate the initial set of results. For line_6: each slew in both sets, contiguous RGA data line_7: is required encompassing an initial FHST map line_8: scheduled as close to the slew as possible, line_9: the slew, and a final FHST map generated line_10: as close to the slew as possible. No FHST line_11: updates or other intervening activities line_12: should be scheduled. Minimally all FHST line_13: maps require 2 FHSTs concurrently mapping for line_14: at least 5 minutes. Continuous ETR coverage line_15: is required for each slew encompassing both line_16: the FHST maps and the slew. Realtime data line_17: is used as a backup to the ETR data. ! question: 3 section: 2 line_1: Each slew starts from the end of the previous line_2: slew and is specified by its destination in line_3: ecliptic coordinates. The current targets line_4: are specified relative to the sun's position line_5: with azimuth angles defined in a counter- line_6: clockwise ascending order as viewed from the line_7: north ecliptic pole and with positive line_8: elevations in the hemisphere north of the line_9: ecliptic plane. The targets have been line_10: selected with a 5 degree pad to avoid line_11: the solar and anti-sun constraints that line_12: reflect magnetometer and SADE constraints. line_13: Each slew target should be implemented to line_14: within 1 degree of the coordinates specified line_15: with HST in an optimal roll orientation. line_16: The padded constraint cones are 62 degrees line_17: and 40 degrees from the solar and anti-sun line_18: regions, respectively. The slew sequence line_19: follows. ! question: 3 section: 3 line_1: Calibration sequence: line_3: Proposal-preparation slew to an azimuth of line_4: 180 degrees and an elevation of 40 degrees. line_6: Slew to azimuth of 140 degrees and an line_7: elevation of 0 degrees. line_9: Slew to an azimuth of 62 degrees and an line_10: elevation of 0 degrees. line_12: Slew to an azimuth of 0 degrees and an line_13: elevation of 62 degrees. line_15: In three steps slew back to the starting line_16: points of the fourth slew, then the third line_17: slew and then the second slew. (HST should line_18: now be pointing to an azimuth of 180 degrees line_19: and an elevation of 40 degrees.) ! question: 3 section: 4 line_1: Verification slews: line_3: Repeat the proposal-preparation slew assuming line_4: other users are slewing HST during the 24 hour line_5: period between the calibration and line_6: verification slews. line_8: Similar to the 6 calibration slews, slew line_9: to (220,0), then (298,0) and then (0,62), line_10: then slew to (298,0), (220,0) and (180,40) line_11: where (220,0) represents an azimuth of 220 line_12: degrees and an elevation of 0 degrees. ! question: 3 section: 5 line_1: In lieu of points with positive elevations line_2: referenced to the ecliptic plane, positive line_3: declinations in celestial coordinates line_4: will suffice. (As a rsult the roll-yaw line_5: maneuvers around the constraint regions will line_6: typically not be 90 degrees.) If a starting line_7: point off the ecliptic plane is difficult, line_8: specific slew ordering is not important. ! question: 3 section: 6 line_1: At least four of the calibration slews, including line_2: a rotation in the ecliptic plane, a rotation line_3: about the anti-sun constraint region and a line_4: rotation about the sun constraint region are line_5: required for processing. PASSOPS requires line_6: 24 hours to compute the RGA alignments and line_7: scale factors for the operational gyros and line_8: to uplink tables to the DF224. The line_9: verification slews will be used to confirm line_10: these results and to provide additional data line_11: to refine these results. ! question: 5 section: 1 line_1: ETR data is required continously for each line_2: data interval of a pair of FHST maps and slew line_3: in between. ETR dumps need to be scheduled line_4: with MOC personnel to avoid track changes line_5: because they cause gaps in the data intervals. line_6: An ETR dump needs to be scheduled soon after line_7: the 6 calibration slews and soon after the line_8: 6 verifications slews to expedite the ground line_9: processing. The real-time data, scheduled to line_10: the maximum possible extent, will be used to line_11: fill in any unexpected gaps in the ETR data. line_12: Telemetry format of PN is required during the line_13: data intervals. At other times AN format is line_14: acceptable. For the attitude computation, it line_15: is important that at least 2 FHST's be line_16: simultaneously unocculted both before and after line_17: the slew with telemetry in PN format being line_18: recorded on the ETR for the entire intervals line_19: of simultaneous FHST maps. ! question: 5 section: 2 line_1: Targets are specified as offsets in celestial line_2: coordinates from the sun, however, ecliptic line_3: offsets are desired. ! question: 7 section: 1 line_1: Data reductionwill be performed in the PASS line_2: system. The initial FHST/RGA scale-factor- line_3: alignment tables for use on HST are expected line_4: to be available within 24 hours after the line_5: completion of the calibration slews. Within line_6: 12 hours after the verification slews, the line_7: implementation of the intial tables will be line_8: confirmed and possibly a refined result will line_9: be available. ! question: 8 section: 1 line_1: This proposal requires a reasonable estimate line_2: of the FHST/FHST alignments for the attitude line_3: determination. For the servicing mission, line_4: map data from this proposal can be combined line_5: with map data from the FHST/FHST alignment line_6: activity (G034) to refine FHST/FHST alignment line_7: estimate prior to computing the FHST/RGA line_8: alignment. The results of this proposal are line_9: required before HST can be accurately slewed. ! !end of general form text general_form_address: lname: Bradley fname: Art inst: Allied-Signal Aerospace addr_1: mail code 440.8; Bldg 3 addr_2: Goddard Space Flight Center city: Greenbelt state: MD zip: 20771 country: USA phone: (301)286-2874 ! lname: Gakenheimer fname: Martin category: PI inst: Allied-Signal Technical Services addr_1: mail code 519.1; Bldg 3 addr_2: Goddard Space Flight Center city: Greenbelt state: MD zip: 20771 country: USA phone: (301)286-3932 ! lname: Hallock fname: Lou inst: Goddard Space Flight Center addr_1: mail code 510.1; Bldg 3 addr_2: Goddard Space Flight Center city: Greenbelt state: MD zip: 20771 country: USA phone: (301)286-4863 ! lname: Kimmer fname: Ed inst: Allied-Signal Technical Services addr_1: mail code 519.1; Bldg 3 addr_2: Goddard Space Flight Center city: Greenbelt state: MD zip: 20771 country: USA phone: (301)286-3932 ! ! end of general_form_address records ! No fixed target records found solar_system_targets: targnum: 1 name_1: FHST1 descr_1: OTHER lev1_1: STD = SUN lev2_1: TYPE = POS_ANGLE, lev2_2: RAD = 223200, lev2_3: ANG = 0, lev2_4: REF = NORTH comment_1: AT ECLIPTIC LONGITUDE OF SUN comment_2: 62 DEGREES NORTH OF THE ECLIPTIC comment_3: IN ECLIPTIC LATITUDE ! targnum: 2 name_1: FHST2 descr_1: OTHER lev1_1: STD = SUN lev2_1: TYPE = POS_ANGLE, lev2_2: RAD = 223200, lev2_3: ANG = 90, lev2_4: REF = NORTH comment_1: LEAD SUN BY 62 DEGREES comment_2: IN THE ECLIPTIC ! targnum: 3 name_1: FHST3 descr_1: OTHER lev1_1: STD = SUN lev2_1: TYPE = POS_ANGLE, lev2_2: RAD = 504000, lev2_3: ANG = 90, lev2_4: REF = NORTH comment_1: LEAD SUN BY 140 DEGREES comment_2: IN THE ECLIPTIC ! targnum: 4 name_1: FHST4 descr_1: OTHER lev1_1: STD = SUN lev2_1: TYPE = POS_ANGLE, lev2_2: RAD = 504000, lev2_3: ANG = 0, lev2_4: REF = NORTH comment_1: 180 DEGREES FROM SUN comment_2: IN ECLIPTIC LONGITUDE comment_3: 40 DEGREES NORTH comment_4: IN ECLIPTIC LATITUDE ! targnum: 5 name_1: FHST5 descr_1: OTHER lev1_1: STD = SUN lev2_1: TYPE = POS_ANGLE, lev2_2: RAD = 223200, lev2_3: ANG = 270, lev2_4: REF = NORTH comment_1: LAG SUN BY 62 DEGREES comment_2: IN THE ECLIPTIC ! targnum: 6 name_1: FHST6 descr_1: OTHER lev1_1: STD = SUN lev2_1: TYPE = POS_ANGLE, lev2_2: RAD = 504000, lev2_3: ANG = 270, lev2_4: REF = NORTH comment_1: LAG SUN BY 140 DEGREES comment_2: IN THE ECLIPTIC ! ! end of solar system targets ! No generic target records found exposure_logsheet: linenum: 1.000 targname: FHST4 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, req_1: CYCLE 3 / 1-12; req_2: SEQUENCE 1-12 NO GAP; req_3: CRITICAL OBS / 1-2; req_4: PCS MODE G / 1-12; comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. comment_3: CONTINUOUS PN FORMAT DATA FROM comment_4: FROM BEGINNING OF THIS LINE comment_5: THROUGH END OF NEXT LINE. ! linenum: 2.000 targname: FHST3 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. ! linenum: 3.000 targname: FHST3 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, req_1: CRITICAL OBS / 3-4; comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. comment_3: CONTINUOUS PN FORMAT DATA FROM comment_4: FROM BEGINNING OF THIS LINE comment_5: THROUGH END OF NEXT LINE. ! linenum: 4.000 targname: FHST2 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. ! linenum: 5.000 targname: FHST2 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, req_1: CRITICAL OBS / 5-6; comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. comment_3: CONTINUOUS PN FORMAT DATA FROM comment_4: FROM BEGINNING OF THIS LINE comment_5: THROUGH END OF NEXT LINE. ! linenum: 6.000 targname: FHST1 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. ! linenum: 7.000 targname: FHST1 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, req_1: CRITICAL OBS / 7-8; comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. comment_3: CONTINUOUS PN FORMAT DATA FROM comment_4: FROM BEGINNING OF THIS LINE comment_5: THROUGH END OF NEXT LINE. ! linenum: 8.000 targname: FHST2 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. ! linenum: 9.000 targname: FHST2 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, req_1: CRITICAL OBS / 9-10; comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. comment_3: CONTINUOUS PN FORMAT DATA FROM comment_4: FROM BEGINNING OF THIS LINE comment_5: THROUGH END OF NEXT LINE. ! linenum: 10.000 targname: FHST3 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. ! linenum: 11.000 targname: FHST3 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, req_1: CRITICAL OBS / 11-12; comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. comment_3: CONTINUOUS PN FORMAT DATA FROM comment_4: FROM BEGINNING OF THIS LINE comment_5: THROUGH END OF NEXT LINE. ! linenum: 12.000 targname: FHST4 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. ! linenum: 21.000 targname: FHST4 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, req_1: CYCLE 3 / 21-32; req_2: SEQUENCE 21-32 NO GAP; req_3: CRITICAL OBS / 21-22; req_4: PCS MODE G / 21-32; req_5: AFTER 12 BY 26H +/- 2H; comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. comment_3: CONTINUOUS PN FORMAT DATA FROM comment_4: FROM BEGINNING OF THIS LINE comment_5: THROUGH END OF NEXT LINE. ! linenum: 22.000 targname: FHST6 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. ! linenum: 23.000 targname: FHST6 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, req_1: CRITICAL OBS / 23-24; comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. comment_3: CONTINUOUS PN FORMAT DATA FROM comment_4: FROM BEGINNING OF THIS LINE comment_5: THROUGH END OF NEXT LINE. ! linenum: 24.000 targname: FHST5 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. ! linenum: 25.000 targname: FHST5 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, req_1: CRITICAL OBS / 25-26; comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. comment_3: CONTINUOUS PN FORMAT DATA FROM comment_4: FROM BEGINNING OF THIS LINE comment_5: THROUGH END OF NEXT LINE. ! linenum: 26.000 targname: FHST1 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. ! linenum: 27.000 targname: FHST1 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, req_1: CRITICAL OBS / 27-28; comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. comment_3: CONTINUOUS PN FORMAT DATA FROM comment_4: FROM BEGINNING OF THIS LINE comment_5: THROUGH END OF NEXT LINE. ! linenum: 28.000 targname: FHST5 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. ! linenum: 29.000 targname: FHST5 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, req_1: CRITICAL OBS / 29-30; comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. comment_3: CONTINUOUS PN FORMAT DATA FROM comment_4: FROM BEGINNING OF THIS LINE comment_5: THROUGH END OF NEXT LINE. ! linenum: 30.000 targname: FHST6 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. ! linenum: 31.000 targname: FHST6 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, req_1: CRITICAL OBS / 31-32; comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. comment_3: CONTINUOUS PN FORMAT DATA FROM comment_4: FROM BEGINNING OF THIS LINE comment_5: THROUGH END OF NEXT LINE. ! linenum: 32.000 targname: FHST4 config: S/C opmode: DATA aperture: V1 num_exp: 1 time_per_exp: 30M priority: 1 param_1: FORMAT=PN, comment_1: FHST MAPPING IN 2 OR MORE comment_2: FHSTS SIMULTANEOUSLY. ! ! end of exposure logsheet ! No scan data records found