Phases with a period of < 1 day do not impact schedulability and should not be specified in Phase I. 0 Assigned ID: 1682 ----- Attempting Submission 1 (Wed Mar 21 18:51:41 GMT 2018) ----- HST Phase I Proposal 1682 (wasp43_uvis_mid_cycle_apt_files.apt) successfully submitted. Receipt: # 1682-1 ----- Attempting Submission 2 (Wed Mar 21 20:50:23 GMT 2018) ----- HST Phase I Proposal 1682 (wasp43_uvis_mid_cycle_apt_files.apt) successfully submitted. Receipt: # 1682-2 ----- Attempting Submission 3 (Wed Mar 21 20:58:07 GMT 2018) ----- HST Phase I Proposal 1682 (wasp43_uvis_mid_cycle_apt_files.apt) successfully submitted. Receipt: # 1682-3 ----- Attempting Submission 4 (Wed Mar 21 21:00:11 GMT 2018) ----- HST Phase I Proposal 1682 (wasp43_uvis_mid_cycle_apt_files.apt) successfully submitted. Receipt: # 1682-4 ----- Attempting Submission 5 (Wed Mar 21 21:20:30 GMT 2018) ----- HST Phase I Proposal 1682 (wasp43_uvis_mid_cycle_apt_files.apt) successfully submitted. Receipt: # 1682-5 ----- Attempting Submission 6 (Thu Mar 22 00:10:24 GMT 2018) ----- HST Phase I Proposal 1682 (wasp43_uvis_mid_cycle_apt_files.apt) successfully submitted. Receipt: # 1682-6 ----- Attempting Submission 7 (Thu Mar 22 00:14:08 GMT 2018) ----- The error states that phase constraints are not required; but with exoplanet eclipse observations, the start of the observation is critical; thus we included the phase constraints as well. ORBITAL VISIBILITY OVERRUN ORBITAL VISIBILITY OVERRUN ORBITAL VISIBILITY OVERRUN ORBITAL VISIBILITY OVERRUN I was requested to reduce the integration times to facilitate schedulability with FGS visibility. Here is the email I was given: """ Since this is a spatial scan we will need 6+ minutes of unused FGS visibility at the end of each orbit as scheduled in our calendar builder, I wasn’t aware of this necessity until we tried to put in on the calendar. Also, your visit uses SCHED 30%. This is unlikely to give us the time at the end of each visibility. One of our calendar builders has recommended that spatial scans should use SCHED 100% and most of the time, that gives us the time we need for the gyro bias update. I have tried to change it from sched30 to sched100 at the behest of the calendar builders and there is an EXTREME overrun now (4-6 minutes per orbit). So I am requesting that you retrieve your APT file and cut down the exposure times so that it is no longer overrun. I tried to autoadjust the orbits using orbit planner but I was unable to do so successfully. """ -304947154 ----- Attempting Submission 1 (Thu May 31 17:45:47 GMT 2018) ----- The error is errant Observations of hot Jupiters have shown that aerosols (i.e. clouds/hazes) exist in their atmospheres, but their location and composition is not generally well known. WASP-43b is poised to become the most well characterized hot Jupiter to date, including several confirmed JWST GTO and ERS phase curve observations. However, previous observations of WASP-43b indicate that aerosol formation in its atmosphere could introduce degeneracy or spurious detections of gas phase chemistry - a major constrain on planet formation theories. In addition, optical reflectivity from these aerosols may be a dominant source of emission to constrain the total energy budget of this planet. Our proposed HST-UVIS observations will constrain the aerosol distribution and composition of WASP-43b, as well as provide essential context for interpreting the upcoming JWST-GTO and JWST-ERS results. We consulted with the STScI WFC3 instrument team for instrumental capabilities and calibration tests. STScI ISR 2017-06 details several calibration observations that reconstructed the stellar flux to <1% predicted by the WFC3-UVIS ETC at STScI. In particular, we will be using "the round trip" scan observations (scan forward, then scan back) to mitigate the unconstrained drift in the scan process; a "round trip" scan returns the detector and FGS to the same location at the beginning of every image. We chose the F350LP filter because it minimized contribution from H2 scattering, maximizing the contrast between the cloudy and the cloudless atmosphere, and thus the SNR on the aerosol composition. We expect negligible thermal contribution. Moreover, any such thermal contribution is expeted to be anti-correlated with the reflected-light contributions and, therfore, distinguishable. The details of our WFC3-UVIS instrument configuration are as follows. Because the WASP-43 is moderately bright (Vmag = 12.4), we will operate in spatial scan mode with a scan rate of 0.15 arcsec s^-1 perpendicular to the read direction -- for 93.1 seconds or 360 pixels -- located 100 rows (YPOS: 6.08) from the readout edge of the detector. This will result in a maximum pixel brightness of <12,500 DN (30,000 e), with minimum read noise contribution. The total scan length will be 360 pixels, which affords the use of the 512x512 sub-array mode -- with an additional 75 pixels before and after the scan. We consulted the STScI WFC3 team for geometric parameters to maximize stability of the observation along the detector's physical rows. APT 25.4.4 determined that our observations will contain 19 frames per orbit (10 forward scan and 9 reverse scan) -- culminating in over 75 frames for the entire program. Using STScI's WFC3-UVIS ETC, we expected an SNR~7800 per frame -- coinciding with a photometric precision per frame of 128 ppm. Planets and Planet Formation 0 false false false false true false false AVAILABLE STAR EXTRA-SOLAR PLANET EXTRA-SOLAR PLANETARY SYSTEM K V-IV NO This object was generated by the targetselector and retrieved from the SIMBAD database. J2000 J2000 WFC3/UVIS Imaging No No F350LP 1552674186120 Phase windows are not calculated when the gap between schedulable intervals is less than 1 days, assuming no scheduling restrictions for constraint Phase 0.307/0.324. The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. /private/var/folders/5c/qcbcp0_97rxd6vyk7cyg_1cw0000gn/T/OPVisit5629533508185767138.xml (Tic-Visit :proposal-id 15473 :visit-id "01" :proposal-version -1 :trans-version "20181130" :date "15-Mar-2019 20:23:05.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 4 :saa-model "29" :si-bright-earth-limb-angle 20.0 :data-volume 486016 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15473 :visit-id "01" :obset-id "01" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15473 :visit-id "01" :orbit-number 1 :pcs-time 393 :si-vis-utilization 2498 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2922 :pcs-gap 0 ) (Tic-Orbit :proposal-id 15473 :visit-id "01" :orbit-number 2 :pcs-time 302 :si-vis-utilization 2603 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2922 :pcs-gap 0 ) (Tic-Orbit :proposal-id 15473 :visit-id "01" :orbit-number 3 :pcs-time 302 :si-vis-utilization 2603 :al-overhead-at-end 0 :internal-dur-at-end 0 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2922 :pcs-gap 0 ) (Tic-Orbit :proposal-id 15473 :visit-id "01" :orbit-number 4 :pcs-time 302 :si-vis-utilization 2603 :al-overhead-at-end 0 :internal-dur-at-end 568 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 2922 :pcs-gap 0 ) true 4 0