0 Assigned ID: 170 ----- Attempting Submission 1 (Wed Apr 05 21:13:04 GMT 2017) ----- HST Phase I Proposal 170 (HST24 proposal gj436 spi+transit - full.pdf.apt) successfully submitted. Receipt: # 170-1 ----- Attempting Submission 2 (Fri Apr 07 23:50:58 GMT 2017) ----- HST Phase I Proposal 170 (HST24 proposal gj436 spi+transit - full.pdf.apt) successfully submitted. Receipt: # 170-2 ----- Attempting Submission 3 (Fri Apr 07 23:53:55 GMT 2017) ----- HST Phase I Proposal 170 (HST24 proposal gj436 spi+transit - full.pdf.apt) successfully submitted. Receipt: # 170-3 ----- Attempting Submission 4 (Fri Apr 07 23:55:17 GMT 2017) ----- HST Phase I Proposal 170 (HST24 proposal gj436 spi+transit - full.pdf.apt) successfully submitted. Receipt: # 170-4 For the best data quality, it is strongly recommended that the maximum number of allowed FP-POS positions is used when observing at a given COS CENWAVE setting. See full description for details. For the best data quality, it is strongly recommended that the maximum number of allowed FP-POS positions is used when observing at a given COS CENWAVE setting. See full description for details. For the best data quality, it is strongly recommended that the maximum number of allowed FP-POS positions is used when observing at a given COS CENWAVE setting. See full description for details. For the best data quality, it is strongly recommended that the maximum number of allowed FP-POS positions is used when observing at a given COS CENWAVE setting. See full description for details. For the best data quality, it is strongly recommended that the maximum number of allowed FP-POS positions is used when observing at a given COS CENWAVE setting. See full description for details. For the best data quality, it is strongly recommended that the maximum number of allowed FP-POS positions is used when observing at a given COS CENWAVE setting. See full description for details. For the best data quality, it is strongly recommended that the maximum number of allowed FP-POS positions is used when observing at a given COS CENWAVE setting. See full description for details. For the best data quality, it is strongly recommended that the maximum number of allowed FP-POS positions is used when observing at a given COS CENWAVE setting. See full description for details. For the best data quality, it is strongly recommended that the maximum number of allowed FP-POS positions is used when observing at a given COS CENWAVE setting. See full description for details. For the best data quality, it is strongly recommended that the maximum number of allowed FP-POS positions is used when observing at a given COS CENWAVE setting. See full description for details. Coordinating with 14767 -------------------- If possible, please coordinate observations to occur in tandem with the transit observations of program 14767, which also has three G130M visits scheduled (two remaining). We are not affiliated with that proposal group, but such scheduling would be to our mutual benefit. Visit groups that are coordinated with 14767 can use that program's transit visit in place of the "peak" visit in the visit group. However, the >20 day separation between visit 1 and 5 of this program must be preserved. Flare safety --------- GJ 436 has been cleared for observation with the same mode for program 14767. Comments still apply 2017 Dec 28. -1433731134 ----- Attempting Submission 1 (Sat Jul 15 05:24:20 GMT 2017) ----- ----- Attempting Submission 2 (Tue Jul 18 21:50:50 GMT 2017) ----- ----- Attempting Submission 3 (Fri Oct 06 18:12:25 GMT 2017) ----- ----- Attempting Submission 4 (Fri Nov 03 20:13:23 GMT 2017) ----- ----- Attempting Submission 5 (Thu Dec 28 21:22:25 GMT 2017) ----- ----- Attempting Submission 6 (Fri Dec 29 05:29:22 GMT 2017) ----- Single FP-POS used because science goals favor relative photometric accuracy (no dithering) over absolute accuracy (dithering). Investigating an SPI and Measuring Baseline FUV Variability in the GJ 436 Hot-Neptune System Closely-orbiting, massive planets can measurably affect the activity of their host star through tides, magnetic disturbances, or even mass transfer. Observations of these star planet interactions (SPIs) provide a window into stellar and planetary physics that may eventually lead to constraints on planetary magnetic fields. Recently, the MUSCLES Treasury Survey of 11 exoplanet host stars revealed correlations providing the first-ever evidence of SPIs in M dwarf systems. This evidence additionally suggests that N V 1238,1242 Angstrom emission best traces SPIs, a feature that merits further investigation. To this end, we propose an experiment using the M dwarf + hot Neptune system GJ 436 that will also benefit upcoming transit observations. GJ 436 is ideal for an SPI experiment because (1) escaped gas from its known rapidly evaporating hot Neptune could be funneled onto the star and (2) it displays a tentative SPI signal in existing, incomplete N V observations. The proposed experiment will complete these N V observations to constrain a model of modulation in N V flux resulting from a stellar hot spot induced by the planet. The results will provide evidence for or against hot spot SPIs producing the correlations observed in the MUSCLES Survey. Furthemore, the acquired data will establish a broader FUV baseline to constrain day-timescale variability and facular emission in FUV lines, needed for the interpretation of upcoming transit observations of GJ 436b. For this reason, we waive our proprietary rights to the data. Establishing GJ 436's baseline FUV variability and testing the hot spot hypothesis are only possible through the FUV capabilities of HST. The proposed observations will sample two timescales to constrain the SPI signal and place a limit on facular flux. Each of two separate four-exposure SPI observation sets will sample a single planetary orbit (2.6 d). These observations will be separated by a significant fraction of the stellar rotation period (39.9 d) to sample changes due to the appearance/occultation of stellar faculae. The feasibility of observing FUV emission lines from GJ 436b has already been established by the 2015 MUSCLES observations that motivated this proposal. These observations yielded ~5% per orbit precision in N V that is sufficient to meet this program's science goals. Therefore, the driving requirement for these observations is phase coverage. For each of the two sets of four-orbit SPI observations that sample an orbit of GJ 436b - One orbit should occur within the interval [-3.3, 3.4] of mid-transit of GJ 436b, to sample the hot-spot flux near full. - One orbit should occur 9.8 h to 5.2 h before mid-transit, to sample intermediate hot- spot flux in the rising phase. - One orbit should occur 5.6 h to 11.0 h after mid-transit, to sample intermediate hot- spot flux in the declining phase. - One orbit should occur in the 37.9 h window either >11.9 h before mid-transit or >13.7 h after mid-transit, to sample stellar flux when the hot spot is not on the visible hemisphere. The slight asymmetry in these numbers is due to the eccentricity, 0.16, of GJ 436b's orbit. Because the science goals are based on relative photometric measurements of line flux, we will employ a single FPPOS position of the grating to maximize photometric precision. This will ensure that any systematic flat-fielding errors will be identical (or as close as possible) between each exposure, minimizing any impact fixed-pattern noise could have on relative photometric measurements. Optionally, the observations could be combined with upcoming transit observations of GJ 436b to enhcance their scientific return. Three five-orbit visits to GJ 436 are currently scheduled for January and March of 2018 for program 14767 "The Panchromatic Comparative Exoplanetary Treasury Program," PI David Sing. If the two SPI observations are scheduled to coincide with the transit visits, then the SPI orbits can also be used to provide a firmer out-of transit baseline and an estimate of the astrophysical noise that is contemporaneous with the observed transits. This would yield greater confidence in the transit results. Meanwhile, the SPI program will benefit from the increased sampling of the hot-spot flux near peak. Planets and Planet Formation Stellar Physics 0 false true false false false false SUPPORTED STAR M V-IV NO This object was generated by the targetselector and retrieved from the SIMBAD database. J2000 J2000 COS/FUV Spectroscopic No No G130M 1291 COS/FUV Spectroscopic No No G130M 1291 COS/FUV Spectroscopic No No G130M 1291 COS/FUV Spectroscopic No No G130M 1291 COS/FUV Spectroscopic No No G130M 1291 COS/FUV Spectroscopic No No G130M 1291 COS/FUV Spectroscopic No No G130M 1291 COS/FUV Spectroscopic No No G130M 1291 Timing link suitability includes constraints ([Group (01 02 03 04) Within 5.0 days] [05 After 01 by 20.0 to 10000.0 days]) The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. /private/var/folders/8k/sxlgy5ts2xdbykzf_vw6jrfw0001c5/T/OPVisit4851449205187386031.xml The "orbit" in the label of these visits refers to the orbit of GJ 436b, not HST. If possible, please coordinate observations to occur in tandem with the transit observations of program 14767, which also has two G130M visits scheduled. Visit groups that are coordinated with 14767 can use that programs transit visit in place of the "peak" visit in the visit group. If the two 14767 transit visits occur sequentially, then only one should be conducted in tandem with these observations to preserve the > 20 d spacing between the two visit groups of this program. Will not do acquisition search because GAIA coordinates are extremely accurate. Will not do peakxd or peakd because target count rate is prohibitively low. Wavelength accuracy is not a driving requiremet, so as long as the target is in the aperture all should be well. planet GJ 436b phase during visit: 0.8455203068350099 < PHASE < 0.9175704888725785 1514063177000 289.0 (Tic-Visit :proposal-id 15174 :visit-id "01" :proposal-version -1 :trans-version "20171009" :date "23-Jan-2018 09:53:09.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 34880 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15174 :visit-id "01" :obset-id "01" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15174 :visit-id "01" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2693 :al-overhead-at-end 0 :internal-dur-at-end 360 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3225 :pcs-gap 0 ) true 1 0 PeakXD and PeakD S/N = 30 tolerated because only photometric accuracy is needed, not wavelength accuracy for the science goals. PeakXD and PeakD S/N = 30 tolerated because only photometric accuracy is needed, not wavelength accuracy for the science goals. Timing link suitability includes constraints ([Group (01 02 03 04) Within 5.0 days]) The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. /private/var/folders/8k/sxlgy5ts2xdbykzf_vw6jrfw0001c5/T/OPVisit4854050262259474830.xml planet GJ 436b phase during visit: 0.9486410507731764 < PHASE < 0.05361732560975 1514105277000 291.0 (Tic-Visit :proposal-id 15174 :visit-id "02" :proposal-version -1 :trans-version "20171009" :date "23-Jan-2018 09:53:10.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 34880 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15174 :visit-id "02" :obset-id "02" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15174 :visit-id "02" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2693 :al-overhead-at-end 0 :internal-dur-at-end 360 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3225 :pcs-gap 0 ) true 1 0 Timing link suitability includes constraints ([Group (01 02 03 04) Within 5.0 days]) The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. /private/var/folders/8k/sxlgy5ts2xdbykzf_vw6jrfw0001c5/T/OPVisit1962432753030576924.xml planet GJ 436b phase during visit: 0.08825406807815696 < PHASE < 0.17396741862295528 1514131833000 289.0 (Tic-Visit :proposal-id 15174 :visit-id "03" :proposal-version -1 :trans-version "20171009" :date "23-Jan-2018 09:53:10.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 34880 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15174 :visit-id "03" :obset-id "03" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15174 :visit-id "03" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2693 :al-overhead-at-end 0 :internal-dur-at-end 360 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3225 :pcs-gap 0 ) true 1 0 Timing link suitability includes constraints ([Group (01 02 03 04) Within 5.0 days]) The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. /private/var/folders/8k/sxlgy5ts2xdbykzf_vw6jrfw0001c5/T/OPVisit5987614318167214791.xml planet GJ 436b phase during visit: 0.2155416491853716 < PHASE < 0.8119885297114802 1513977353000 289.0471930818935 (Tic-Visit :proposal-id 15174 :visit-id "04" :proposal-version -1 :trans-version "20171009" :date "23-Jan-2018 09:53:11.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 34880 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15174 :visit-id "04" :obset-id "04" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15174 :visit-id "04" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2693 :al-overhead-at-end 0 :internal-dur-at-end 360 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3225 :pcs-gap 0 ) true 1 0 Timing link suitability includes constraints ([Group (05 06 07 08) Within 5.0 days] [05 After 01 by 20.0 to 10000.0 days]) The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. /private/var/folders/8k/sxlgy5ts2xdbykzf_vw6jrfw0001c5/T/OPVisit8477590034468799027.xml planet GJ 436b phase during visit: 0.8455203068350099 < PHASE < 0.9175704888725785 1516352413000 274.87026895076787 (Tic-Visit :proposal-id 15174 :visit-id "05" :proposal-version -1 :trans-version "20171009" :date "23-Jan-2018 09:53:12.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 34880 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15174 :visit-id "05" :obset-id "05" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15174 :visit-id "05" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2817 :al-overhead-at-end 0 :internal-dur-at-end 360 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3225 :pcs-gap 0 ) true 1 0 Used previous ETC values multiplied by (40/30)^2 to update to the required TA S/N due to the urgency of the required change. Used previous ETC values multiplied by (40/30)^2 to update to the required TA S/N due to the urgency of the required change. Timing link suitability includes constraints ([Group (05 06 07 08) Within 5.0 days]) The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. /private/var/folders/8k/sxlgy5ts2xdbykzf_vw6jrfw0001c5/T/OPVisit9179132669190737432.xml planet GJ 436b phase during visit: 0.9486410507731764 < PHASE < 0.05361732560975 1516374264000 274.70016808008194 (Tic-Visit :proposal-id 15174 :visit-id "06" :proposal-version -1 :trans-version "20171009" :date "23-Jan-2018 09:53:12.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 34880 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15174 :visit-id "06" :obset-id "06" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15174 :visit-id "06" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2817 :al-overhead-at-end 0 :internal-dur-at-end 360 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3225 :pcs-gap 0 ) true 1 0 Used previous ETC values multiplied by (40/30)^2 to update to the required TA S/N due to the urgency of the required change. Used previous ETC values multiplied by (40/30)^2 to update to the required TA S/N due to the urgency of the required change. Timing link suitability includes constraints ([Group (05 06 07 08) Within 5.0 days]) The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. /private/var/folders/8k/sxlgy5ts2xdbykzf_vw6jrfw0001c5/T/OPVisit3749486630847040637.xml planet GJ 436b phase during visit: 0.08825406807815696 < PHASE < 0.17396741862295528 1516402864000 274.4758440220655 (Tic-Visit :proposal-id 15174 :visit-id "07" :proposal-version -1 :trans-version "20171009" :date "23-Jan-2018 09:53:13.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 34880 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15174 :visit-id "07" :obset-id "07" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15174 :visit-id "07" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2817 :al-overhead-at-end 0 :internal-dur-at-end 360 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3225 :pcs-gap 0 ) true 1 0 Used previous ETC values multiplied by (40/30)^2 to update to the required TA S/N due to the urgency of the required change. Used previous ETC values multiplied by (40/30)^2 to update to the required TA S/N due to the urgency of the required change. Timing link suitability includes constraints ([Group (05 06 07 08) Within 5.0 days]) The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. /private/var/folders/8k/sxlgy5ts2xdbykzf_vw6jrfw0001c5/T/OPVisit1303284290699070177.xml planet GJ 436b phase during visit: 0.2155416491853716 < PHASE < 0.8119885297114802 1516455708000 274.0586325303611 (Tic-Visit :proposal-id 15174 :visit-id "08" :proposal-version -1 :trans-version "20171009" :date "23-Jan-2018 09:53:14.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 34880 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15174 :visit-id "08" :obset-id "08" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15174 :visit-id "08" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2817 :al-overhead-at-end 0 :internal-dur-at-end 360 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3225 :pcs-gap 0 ) true 1 0 Used previous ETC values multiplied by (40/30)^2 to update to the required TA S/N due to the urgency of the required change. Used previous ETC values multiplied by (40/30)^2 to update to the required TA S/N due to the urgency of the required change. The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. /private/var/folders/8k/sxlgy5ts2xdbykzf_vw6jrfw0001c5/T/OPVisit439888058842380129.xml planet GJ 436b phase during visit: 0.08825406807815696 < PHASE < 0.17396741862295528 (Tic-Visit :proposal-id 15174 :visit-id "57" :proposal-version -1 :trans-version "20171009" :date "23-Jan-2018 09:51:59.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 34880 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15174 :visit-id "57" :obset-id "57" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15174 :visit-id "57" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2817 :al-overhead-at-end 0 :internal-dur-at-end 360 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3225 :pcs-gap 0 ) true 1 0 Used previous ETC values multiplied by (40/30)^2 to update to the required TA S/N due to the urgency of the required change. Used previous ETC values multiplied by (40/30)^2 to update to the required TA S/N due to the urgency of the required change. The scheduling data was generated by CASM 25.2. CASM was run in Phase II mode. /private/var/folders/8k/sxlgy5ts2xdbykzf_vw6jrfw0001c5/T/OPVisit4340612084817986232.xml planet GJ 436b phase during visit: 0.2155416491853716 < PHASE < 0.8119885297114802 (Tic-Visit :proposal-id 15174 :visit-id "58" :proposal-version -1 :trans-version "20171009" :date "23-Jan-2018 09:52:02.0" :trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0 :FATAL-ERRORS 0 :CONTINUABLE-FATALS 0) :number-of-orbits 1 :saa-model "31" :si-bright-earth-limb-angle 20.0 :data-volume 34880 :tdrss-contact-duration 0 :coron NIL ) (Tic-Obset :proposal-id 15174 :visit-id "58" :obset-id "58" :pcs-mode "FGS" ) (Tic-Orbit :proposal-id 15174 :visit-id "58" :orbit-number 1 :pcs-time 333 :si-vis-utilization 2817 :al-overhead-at-end 0 :internal-dur-at-end 360 :dark-offset NIL :dark-utilization 0 :max-dark-utilization 1920 :low-sky "N" :pcs-visibility 3225 :pcs-gap 0 ) true 1 0 Used previous ETC values multiplied by (40/30)^2 to update to the required TA S/N due to the urgency of the required change. Used previous ETC values multiplied by (40/30)^2 to update to the required TA S/N due to the urgency of the required change.