0 Assigned ID: 796 ----- Attempting Submission 1 (Fri Apr 08 20:39:30 GMT 2016) ----- HST Phase I Proposal 796 (jupiter_cy24.apt) successfully submitted. Receipt: # 796-1 ----- Attempting Submission 2 (Fri Apr 08 23:19:16 GMT 2016) ----- HST Phase I Proposal 796 (jupiter_cy24.apt) successfully submitted. Receipt: # 796-2 ----- Attempting Submission 3 (Fri Apr 08 23:28:00 GMT 2016) ----- HST Phase I Proposal 796 (jupiter_cy24_2.apt) successfully submitted. Receipt: # 796-3 ----- Attempting Submission 4 (Fri Apr 08 23:45:28 GMT 2016) ----- MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING POS TARG OUTSIDE OF APERTURE FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING POS TARG OUTSIDE OF APERTURE FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING MERGING RULE VIOLATED DURING AUTOMATIC MERGING FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser This is the updated version for Visits 5 and 6. Extra exposures were added because of unused visibility. Visit 6 is expected to take place during the visibility period ending August 16 at 14:11 UT. -1682395658 ----- Attempting Submission 1 (Fri Jul 22 14:31:49 GMT 2016) ----- HST Phase II Proposal 14666 (14666.apt) successfully submitted. Receipt: # 14666-1 ----- Attempting Submission 2 (Fri Feb 24 23:27:06 GMT 2017) ----- ----- Attempting Submission 3 (Tue Feb 28 22:35:57 GMT 2017) ----- ----- Attempting Submission 4 (Fri Apr 14 19:37:08 GMT 2017) ----- HST Phase II Proposal 14666 (prop_14666_test_visit34.apt) successfully submitted. Receipt: # 14666-4 ----- Attempting Submission 5 (Thu Apr 27 15:05:03 GMT 2017) ----- HST Phase II Proposal 14666 (prop_14666_visit34_final.apt) successfully submitted. Receipt: # 14666-5 ----- Attempting Submission 6 (Fri Jul 21 18:14:02 GMT 2017) ----- The merging rule violations are still present - assume they are not an issue. As noted before, we prefer to avoid preflashing due to the fact that we are interested in bright targets. The FLASH warnings can be safely ignored. Einstein's theory of General Relativity is a key component of our understanding of cosmology, underlying the interpretation of cosmic acceleration in terms of Dark Energy. Gravitational lensing is a major element of modern observational cosmology, used both in reconstructing the mass distribution of galaxies and clusters of galaxies, and in predicting the magnification of sources behind massive clusters. An astrometric verification of gravitational lensing was historically the first experimental test of General Relativity, yet there has been to date no verification of the deflection predicted for a non-spherical source. We propose to use the astrometric capabilities of WFC3 in spatial scan mode to observe the apparent shift in position of several stars in three separate fields during their near-occultation by Jupiter. These measurements will provide two fundamental tests of General Relativity: (1) one of the most precise light-deflection tests ever conducted, and the most precise in the visible, verifying the GR prediction with a precision of 0.04%, and (2) the first measurement of the differential deflection due to the flattening of Jupiter's gravitational potential, verifying the GR prediction of deflection by a *non-spherical* mass with a precision of 5%. The proposed observations consist of WFC3/UVIS spatial scans of three target fields, each observed at two separate times: one (near-transit) when Jupiter is very close to the edge of the field, with at least one bright star as close to Jupiter's limb as possible; and the other (off-transit) a few days earlier or later, when Jupiter is several arcminutes away. At that time the light deflection due to Jupiter will be < 200 muas, and can be predicted to much better than 1 muas. Each observation will consist of one orbit, with four or five separate scans depending on available visibility, typically conducted in F606W, and as nearly perpendicular to Jupiter's motion as feasible at that time, taking into account the position and motion of the Galilean satellites, so that their trails do not interfere with the target stars. The pointing will be chosen so that Jupiter remains outside the field of view, at a distance of several arcseconds, but that bright target stars are as close as possible to Jupiter, taking into account Earth occultation, SAA passages, and other orbital constraints. Because of the impact of HST's orbital position on the event timing, it is possible that as accurate HST ephemeris become available, some of the field selections might change. The program also includes direct observations of the field in two filters, F547M and F467M, using 2x2 binning to reduce constraints due to buffer transfers. These observations will provide initial positions and colors for the stars in the field, and form the first step for the analysis of scan data (Riess et al. 2014, Casertano et al. 2016). The color information will also be useful to constrain the parallax of target stars; very red stars could be nearby, less than a few hundred parsecs from the Sun, in which case they would experience a significant parallactic motion during the observing period, and may need to be excluded from the analysis. Intergalactic Medium and Cosmology Solar System 6 false false false false false false SUPPORTED EXT-STAR UNDESIGNATED J2000 J2000 EXT-STAR UNDESIGNATED Magnitude of brightest star in the fied J2000 J2000 EXT-STAR UNDESIGNATED J2000 J2000 WFC3/UVIS Imaging No No F606W WFC3/UVIS Imaging No No F467M WFC3/UVIS Imaging No No F547M WFC3/UVIS Imaging No No F606W WFC3/UVIS Imaging No No F467M WFC3/UVIS Imaging No No F547M WFC3/UVIS Imaging No No F606W WFC3/UVIS Imaging No No F467M WFC3/UVIS Imaging No No F547M 1500660745820 The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. 2900 Visit coordinates updated to match Visit 2 (on-Jupiter) which will execute shortly after Jupiter occultation. ORIENT 300 is chosen for schedulability reasons. The goal is to stay as far away from jupiter as possible, while including the bright stars closest to Jupiter. Execution in the first of the two windows is preferred if possible. 1490637950000 300.0 (Tic-Visit :proposal-id 14666 :visit-id "01" :proposal-version -1 :trans-version "20170613" :date "21-Jul-2017 14:12:25.0" :trans-errors '(:WARNINGS 8 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 1588080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 14666 :visit-id "01" :obset-id "01" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 14666 :visit-id "01" :orbit-number 1 :pcs-time 241 :si-vis-utilization 2448 :al-overhead-at-end 65 :internal-dur-at-end 510 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2982 :pcs-gap 0 ) true 1 0 1500660747714 The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. This visit is expected to occur in the visibility period 2017.091:04:33:58- 2017.091:05:32:29. This is shortly after Jupiter crosses the target area. Jupiter center at 2017.091:04:35:00 is 13 12 02.88 -05 55 37.8 (from the JPL Ephemeris) with an angular diameter of 44.2 arcsec. With the current settings, it is expected that the edge of Jupiter will be approximately 8 arcsec off the field of view at the beginning of the visibility period, increasing by an additional 15 arcsec by the end of the exposure. These settings are chosen to reduce light contamination, raised as a potential issue during proposal review. The orient of 300 is chosen for schedulability considerations; only single GS is available at the selected ORIENT and POS TARGs. Coordinates may be slightly updated if HST ephemeris changes visibility period by more than 2 minutes. 1491021227000 300.0 (Tic-Visit :proposal-id 14666 :visit-id "02" :proposal-version -1 :trans-version "20170613" :date "21-Jul-2017 14:12:27.0" :trans-errors '(:WARNINGS 8 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 1588080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 14666 :visit-id "02" :obset-id "02" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 14666 :visit-id "02" :orbit-number 1 :pcs-time 241 :si-vis-utilization 2445 :al-overhead-at-end 65 :internal-dur-at-end 510 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2982 :pcs-gap 0 ) true 1 0 1500660749692 The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. This visit targets the same field as Visit 4, but a few days before or after Jupiter crosses the star field. It needs to occur at least 2 days before or after Visit 4, as given in the Between requirements. amd at the same Orient, as specified in the visit orientation requirements. 1495352886000 130.0 (Tic-Visit :proposal-id 14666 :visit-id "03" :proposal-version -1 :trans-version "20170613" :date "21-Jul-2017 14:12:29.0" :trans-errors '(:WARNINGS 7 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 1588080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 14666 :visit-id "03" :obset-id "03" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 14666 :visit-id "03" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2740 :al-overhead-at-end 0 :internal-dur-at-end 510 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3137 :pcs-gap 0 ) true 1 0 1500660751631 The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. This visit targets a star field just befor Jupiter crosses it, on May 17, 2017. The visit will optimally be executed on May 17 in the last visibility period available before the SAA impact, ending about 15:52 UT (this is an SAA hider). If necessary, it can execute the previous orbit. It cannot execute any later than May 17 at 18:00 UT, otherwise Jupiter will be too close to the field of view. The ORIENT has been chosen to optimize the placement of the bright stars in the field on the detector. 1495032633000 130.0 (Tic-Visit :proposal-id 14666 :visit-id "04" :proposal-version -1 :trans-version "20170613" :date "21-Jul-2017 14:12:31.0" :trans-errors '(:WARNINGS 7 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 1588080 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 14666 :visit-id "04" :obset-id "04" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 14666 :visit-id "04" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2779 :al-overhead-at-end 0 :internal-dur-at-end 510 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3137 :pcs-gap 0 ) true 1 0 1501085949870 /private/var/folders/8k/sxlgy5ts2xdbykzf_vw6jrfw0001c5/T/OPVisit3576395289007889657.xml The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. Update to Visit 5 based on SAA passages. Impacted time on 2017.228 (August 16) starts at 15:00. This is the Jupiter off-visit, thus can execute before or after that time. (Tic-Visit :proposal-id 14666 :visit-id "05" :proposal-version -1 :trans-version "20170613" :date "26-Jul-2017 12:19:09.0" :trans-errors '(:WARNINGS 7 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 1732400 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 14666 :visit-id "05" :obset-id "05" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 14666 :visit-id "05" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2798 :al-overhead-at-end 65 :internal-dur-at-end 667 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3134 :pcs-gap 0 ) true 1 0 Requires updated HST ephemeris with better than 5 min knowledge of start and end of visibility period in order to optimize timing and orientation of observations. Target stars are intrinsically bright and are not expected to be adversely affected by the low background level. Target stars are intrinsically bright and are not expected to be adversely affected by the low background level. Target stars are intrinsically bright and are not expected to be adversely affected by the low background level. Target stars are intrinsically bright and are not expected to be adversely affected by the low background level. 1501085952507 /private/var/folders/8k/sxlgy5ts2xdbykzf_vw6jrfw0001c5/T/OPVisit657382152830888241.xml The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. Update to Visit 6 based on SAA passages. Impacted time on 2017.228 (August 16) starts at 15:00. This is the Jupiter on-visit, thus must execute at the specified time. (Tic-Visit :proposal-id 14666 :visit-id "06" :proposal-version -1 :trans-version "20170613" :date "26-Jul-2017 12:19:12.0" :trans-errors '(:WARNINGS 7 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 1732400 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 14666 :visit-id "06" :obset-id "06" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 14666 :visit-id "06" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2795 :al-overhead-at-end 65 :internal-dur-at-end 667 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3134 :pcs-gap 0 ) true 1 0 Requires updated HST ephemeris with better than 5 min knowledge of start and end of visibility period in order to optimize timing and orientation of observations. Target stars are intrinsically bright and are not expected to be adversely affected by the low background level. The background in this image will actually be abnormally high because of the proximity of Jupiter. Target stars are intrinsically bright and are not expected to be adversely affected by the low background level. The background in this image will actually be abnormally high because of the proximity of Jupiter. Target stars are intrinsically bright and are not expected to be adversely affected by the low background level. The background in this image will actually be abnormally high because of the proximity of Jupiter. Target stars are intrinsically bright and are not expected to be adversely affected by the low background level. The background in this image will actually be abnormally high because of the proximity of Jupiter.