0 Assigned ID: 254 ----- Attempting Submission 1 (Thu Apr 09 20:35:43 GMT 2015) ----- HST Phase I Proposal 254 (HSTK2Uranus.apt) successfully submitted. Receipt: # 254-1 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 POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. 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 FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. 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 FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. 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 FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. 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 FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. 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 FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. FLASH level may be too low for this exposure or a short subexposure. See extended explanation in the diagnostic browser POS TARG & PATTERN should be used carefully with ACS ramp or WFC3 quad filters as central wavelengths & transmission efficiencies vary within the apertures. 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 I have submitted the Phase II proposal for Program 14195, but I am writing these comments to raise the need for it to be carefully reviewed. The big picture is that, as promised in Phase I, the main design was copied from the OPAL Uranus observations (Program 13937, specifically the 2014 ones marked as 'completed'); this relates to filters, exposure times, and dithering pattern. You should also be aware that it has been a decade since my last HST observations and I have never observed a solar system target, so the chance of major blunders may be higher than usual! Remark on Target (Uranus): It seemed to me from the Phase II instructions on moving targets that I should list Uranus twice in the target list, once for the first set of visits in early January and once for the second set of visits, rather than once or six times. I hope this is correct and/or harmless. In all images the target is the planet. Dr. Simon, PI of OPAL and co-I here, explained to me that he "Do note that we used pos-targs to offset the pointing very slightly. That was to center Uranus in the UVIS quad filters." Please let me know if and how I need to adjust the pointing. Changes From OPAL related to unsupported modes: Two changes were made to the OPAL Phase II program design which I believe relate to unsupported/non-standard models. 1. OPAL has a "single" guide star specification for the first filter of each Uranus visit. This generated errors and I removed it. I don't know if it would be relevant to the 2016 observing. Dr. Simon explains "we [OPAL] were doing global maps, so we sometimes took a chance on guide stars to ensure we could get the orbit spacing we wanted (even more important for jupiter where we need consecutive orbits). We also loosen up the constraint on SAA impingement for that reason. So, once we know the plan windows, we usually optimize a bit." 2. OPAL had BLADE=A set for the F547M observation. This is not supported and therefore I removed it. I assume it has something to do with image quality. Dr. Simon does not have any record of why this was chosen in OPAL. Existing warnings: 1. There are a number of warnings about the FLASH levels. Because I have copied OPAL, and because we are imaging Uranus, I think this is fine. 2. I am hoping all the Q filter specifications are correct to get the planet, they are just copied over too. See above. Question on Optimization: I am satisfied with the plan, which is what we described in Phase I, but the orbit planner seems to show some extra time (226). Would it be possible to squeeze in one more image? 1263528697 ----- Attempting Submission 1 (Thu Jul 16 18:01:24 GMT 2015) ----- See submission comments for discussion. I believe the FLASH warnings are not an issue for Uranus. Cloud Evolution on Uranus with K2 and HST The Kepler K2 mission will monitor Uranus at high photometric precision for three months to determine its interior structure via seismology and to track cloud evolution.This will allow, for the first time, a direct comparison between the disk-integrated weather evolution of a planet and brown dwarfs, and eventually exoplanets. Hubble Space Telescope optical imaging taken during the K2 campaign is needed to anchor our understanding of the atmospheric cloud morphology. We propose observations that will allow us to map the cloud features with HST twice during the K2 campaign. As noted in the abstract, this proposal is aimed at imaging Uranus during the K2 monitoring campaign. We have chosen to copy the existing OPAL legacy program for the observing program; the main difference is the number and timing of the visits. The broad Kepler filter extends from 430nm to 900nm. In a single orbit, we can image Uranus with the WFC3/UVIS medium width lters F467M (14s), F547M (6s), and F845M (20s). This allows us to compare the HST map to the K2-derived map. In addition, we will observe in the methane Filters FQ619N (65s), FQ727N (200s), and FQ924N (100s); and the narrow filter F658N (144s) that maximizes the detectability of a dark spot (see Sromovsky et al. 2012). These filters probe dierent layers of the atmosphere to see cloud structure. An advantage of choosing these filters is that they are same as those used by the OPAL legacy program monitoring Uranus for the next several years (program 13937) . Examples of their images detecting clouds can be see in Wong et al. (2015). This should add to the long-term archival value of our program. We adopt the same exposure times as OPAL, given above, and take a pair of dithered images in each Filter. In a few cases, as in OPAL, only a single image is taken due to the time constraints of a single orbit; though this means cosmic rays will degrade the image, we believe our science goals can till be met. In order to construct a reliable map minimizing limb effects, we need three observations during a single Uranian day. Therefore, we request three orbits of observations, with each one following four orbits after the rest. We need two maps to anchor the light curve analysis; one relatively early in the K2 campaign and one near the mid-point. We therefore request six orbits. The second half of the K2 campaign is unobservable (at night) from Earth. SOLAR SYSTEM 12 false false false false SUPPORTED SOLAR SYSTEM PLANET First visit to Uranus STD=URANUS EARTH SOLAR SYSTEM PLANET Second visit to Uranus STD=URANUS EARTH WFC3/UVIS Imaging No No F845M WFC3/UVIS Imaging No No F467M WFC3/UVIS Imaging No No F547M WFC3/UVIS Imaging No No F658N WFC3/UVIS Imaging No No FQ924N WFC3/UVIS Imaging No No FQ727N WFC3/UVIS Imaging No No FQ619N WFC3/UVIS Imaging No No F845M WFC3/UVIS Imaging No No F467M WFC3/UVIS Imaging No No F547M WFC3/UVIS Imaging No No F658N WFC3/UVIS Imaging No No FQ924N WFC3/UVIS Imaging No No FQ727N WFC3/UVIS Imaging No No FQ619N POS-TARG DITHER 0.145 LINE false false 2 46.84 WFC3-UVIS-DITHER-LINE 1 false Timing link suitability includes constraints ([02 After 01 by 0.3 to 0.3 days]) The scheduling data was generated by CASM 23.2. CASM was run in Phase II mode. This is the first of a set of three visits to make a map of Uranus early in the K2 campaign. (Tic-Visit :proposal-id 14195 :visit-id "01" :proposal-version -1 :trans-version "20150609" :date "16-Jul-2015 13:57:49.0" :trans-errors '(:WARNINGS 0 :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 325232 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 14195 :visit-id "01" :obset-id "01" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 14195 :visit-id "01" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2651 :al-overhead-at-end 0 :internal-dur-at-end 392 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3210 :pcs-gap 0 ) false 1 0 Timing link suitability includes constraints ([02 After 01 by 0.3 to 0.3 days] [03 After 02 by 0.3 to 0.3 days]) The scheduling data was generated by CASM 23.2. CASM was run in Phase II mode. This is the second of a set of three visits to make a map of Uranus early in the K2 campaign. The timing of 4 orbits is later is for approximate a third of a Uranus rotation. (Tic-Visit :proposal-id 14195 :visit-id "02" :proposal-version -1 :trans-version "20150609" :date "16-Jul-2015 13:57:52.0" :trans-errors '(:WARNINGS 0 :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 325232 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 14195 :visit-id "02" :obset-id "02" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 14195 :visit-id "02" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2651 :al-overhead-at-end 0 :internal-dur-at-end 392 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3210 :pcs-gap 0 ) false 1 0 Timing link suitability includes constraints ([03 After 02 by 0.3 to 0.3 days]) The scheduling data was generated by CASM 23.2. CASM was run in Phase II mode. This is the third of a set of three visits to make a map of Uranus early in the K2 campaign. The timing of 4 orbits is later is for approximate a third of a Uranus rotation. (Tic-Visit :proposal-id 14195 :visit-id "03" :proposal-version -1 :trans-version "20150609" :date "16-Jul-2015 13:57:55.0" :trans-errors '(:WARNINGS 0 :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 325232 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 14195 :visit-id "03" :obset-id "03" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 14195 :visit-id "03" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2651 :al-overhead-at-end 0 :internal-dur-at-end 392 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3210 :pcs-gap 0 ) false 1 0 Timing link suitability includes constraints ([05 After 04 by 0.3 to 0.3 days]) The scheduling data was generated by CASM 23.2. CASM was run in Phase II mode. This is the first of a set of three visits to make a second map of Uranus in the middle of the K2 campaign. (Tic-Visit :proposal-id 14195 :visit-id "04" :proposal-version -1 :trans-version "20150609" :date "16-Jul-2015 13:57:59.0" :trans-errors '(:WARNINGS 0 :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 325232 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 14195 :visit-id "04" :obset-id "04" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 14195 :visit-id "04" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2651 :al-overhead-at-end 0 :internal-dur-at-end 392 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3210 :pcs-gap 0 ) false 1 0 Timing link suitability includes constraints ([05 After 04 by 0.3 to 0.3 days] [06 After 05 by 0.3 to 0.3 days]) The scheduling data was generated by CASM 23.2. CASM was run in Phase II mode. This is the second of a set of three visits to make a second map of Uranus in the middle of the K2 campaign. It is 4 orbits later to allow 1/3 of a rotation by the planet. (Tic-Visit :proposal-id 14195 :visit-id "05" :proposal-version -1 :trans-version "20150609" :date "16-Jul-2015 13:58:02.0" :trans-errors '(:WARNINGS 0 :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 325232 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 14195 :visit-id "05" :obset-id "05" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 14195 :visit-id "05" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2651 :al-overhead-at-end 0 :internal-dur-at-end 392 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3210 :pcs-gap 0 ) false 1 0 Timing link suitability includes constraints ([06 After 05 by 0.3 to 0.3 days]) The scheduling data was generated by CASM 23.2. CASM was run in Phase II mode. This is the third of a set of three visits to make a second map of Uranus in the middle of the K2 campaign. It is 4 orbits later to allow 1/3 of a rotation by the planet. (Tic-Visit :proposal-id 14195 :visit-id "06" :proposal-version -1 :trans-version "20150609" :date "16-Jul-2015 13:58:05.0" :trans-errors '(:WARNINGS 0 :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 325232 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 14195 :visit-id "06" :obset-id "06" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 14195 :visit-id "06" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2651 :al-overhead-at-end 0 :internal-dur-at-end 392 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3210 :pcs-gap 0 ) false 1 0