0Assigned ID: 658
----- Attempting Submission 1 (Fri Apr 08 18:25:24 GMT 2016) -----Resubmission with smaller checkbox on STIS ACQ (visit 4) (3/24/16).-1670495778----- Attempting Submission 1 (Wed Jul 13 20:35:17 GMT 2016) -----
HST Phase II Proposal 14631 (prop_m87_phase2.apt) successfully submitted.
Receipt: # 14631-1
----- Attempting Submission 2 (Wed Jul 20 16:58:09 GMT 2016) -----
----- Attempting Submission 3 (Mon Nov 28 23:29:19 GMT 2016) -----
----- Attempting Submission 4 (Wed Mar 01 18:54:59 GMT 2017) -----
----- Attempting Submission 5 (Fri Mar 24 18:53:39 GMT 2017) -----Resolving the Nuclear Structure of the Canonical Radio Galaxy M87The nearby galaxy M87 is the prototype for low-power radio-loud FR1-type AGN, the parent population of BL Lac type blazars. Despite its proximity, brightness, and nearly a century of observations, the physical picture of how the AGN emission is fueled and what is causing the bright and variable emission in the core of M87 is still mysterious. Recent COS observations show a complex and variable line profile and weak UV continuum with hints of spatial structure (Danforth et al. 2016). Consistent with recent X-ray observations, we find little accreting gas inside the Bondi radius. We propose to resolve and precisely locate the ionizing continuum and Ly alpha line-emitting structures with long-slit far-UV STIS spectra of the nucleus. These observations will also allow us to confirm (or not) the density-bounded nature of the line emission. Along with the spatially-resolved spectroscopy, we will use multi-epoch, high-S/N COS aperture spectroscopy to address the mystery of what powers this common yet poorly-understood class of active galaxies.We request two visits of five orbits each to observe the nucleus of M87. The two visits will be planned such that the STIS slit is placed along the axis of the relativistic jet during one visit and perpendicular to it on the other. Four orbits of each five-orbit visit will be devoted to spatially-resolved STIS/G140M spectroscopy with the 52x0.2" slit. The final orbit for each case will aquire sensitive COS/G130M data to obtain high-S/N measurements of the Lya profile and wings as well as metal-line emission.
We base our exposure time requirements on the lowest flux component of the Cycle 21 COS spectrum. In that spectra (as well as those obtained by FOS in 1997), the continuum flux was approximately 10^-15 erg/cm2/Ang. The STIS ETC gives a S/N~4 per unbinned pixel for a 10 ksec exposure (~4 orbits). The red and blue Lya emission components were observed at (3-5)x10-15 in 2014. Four orbits at this level should provide S/N=7-10 per unbinned resel. Even if the line emission varies considerably, we will have usable data. The data will be extracted at full spatial and spectral resolution though for some applications, we will resample the line spread function to better match the COS/G130M resolution. Line profile fitting will be accomplished in much the same manner as was used for our Cycle 21 COS data.
Based on the observed continuum and line fluxes from our Cycle 21 COS observations, a single exposure of ~2500 seconds with the sensitive COS/G130M grating will give S/N~5 per resolution element.Massive Black Holes and their HostsIntergalactic Medium and Cosmology6falsetruefalsefalsefalsefalseSUPPORTEDGALAXYELLIPTICALJETNUCLEUSRADIO GALAXYNOThis object was generated by the target selector and retrieved from the SIMBAD database. Coords from VLBI centroid.J2000J2000STIS/FUV-MAMASpectroscopicNoNoG140M1222COS/FUVSpectroscopicNoNoG130M1291COS/FUVSpectroscopicNoNoG130M1300COS/FUVSpectroscopicNoNoG130M1309COS/FUVSpectroscopicNoNoG130M1318COS/FUVSpectroscopicNoNoG130M1327STIS/FUV-MAMASpectroscopicNoNoG140M1222COS/FUVSpectroscopicNoNoG130M1291COS/FUVSpectroscopicNoNoG130M1300COS/FUVSpectroscopicNoNoG130M1309COS/FUVSpectroscopicNoNoG130M1318COS/FUVSpectroscopicNoNoG130M1327Timing link suitability includes constraints ([Group (01 02) Within 0.5 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode./private/var/folders/7m/_r88cxcn2vnftcvq56mk6y_40000gw/T/OPVisit2508968628224881461.xml1484406100000288.1453514255408(Tic-Visit
:proposal-id 14631
:visit-id "01"
:proposal-version -1
:trans-version "20170109"
:date "24-Mar-2017 12:52:15.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 243648
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 14631
:visit-id "01"
:obset-id "01"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14631
:visit-id "01"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2884
:al-overhead-at-end 0
:internal-dur-at-end 388
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3218
:pcs-gap 0
)true10Steve Penton's recommended approach from Cy22/13489
Updated per de Rosa email 11/21/16Updated per de Rosa email 11/21/16The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode./private/var/folders/7m/_r88cxcn2vnftcvq56mk6y_40000gw/T/OPVisit5040065499509746075.xmlRepeat of visit 01. Visit 01 lost due to SIC & DH safing event on Jan 13, 2017.1484439956000288.02961422073383(Tic-Visit
:proposal-id 14631
:visit-id "05"
:proposal-version -1
:trans-version "20170109"
:date "24-Mar-2017 12:52:16.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 243648
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 14631
:visit-id "05"
:obset-id "05"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14631
:visit-id "05"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2884
:al-overhead-at-end 0
:internal-dur-at-end 388
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3218
:pcs-gap 0
)true10Steve Penton's recommended approach from Cy22/13489
Updated per de Rosa email 11/21/16Updated per de Rosa email 11/21/16Timing link suitability includes constraints ([Group (01 02) Within 0.5 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode./private/var/folders/7m/_r88cxcn2vnftcvq56mk6y_40000gw/T/OPVisit5937314080623692373.xmlSlit position parallel to M87 Jet axis.1484417098000265.0(Tic-Visit
:proposal-id 14631
:visit-id "02"
:proposal-version -1
:trans-version "20170109"
:date "24-Mar-2017 12:52:19.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 4
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 904992
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 14631
:visit-id "02"
:obset-id "02"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14631
:visit-id "02"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2885
:al-overhead-at-end 0
:internal-dur-at-end 178
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3218
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14631
:visit-id "02"
:orbit-number 2
:pcs-time 222
:si-vis-utilization 2996
: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 3218
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14631
:visit-id "02"
:orbit-number 3
:pcs-time 222
:si-vis-utilization 2996
: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 3218
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14631
:visit-id "02"
:orbit-number 4
:pcs-time 222
:si-vis-utilization 2996
:al-overhead-at-end 0
:internal-dur-at-end 622
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3218
:pcs-gap 0
)true40Nucleus is close to a point source, but may be extended. I'm using checkbox=11 (0.5 arcsec box) to avoid possible confusion by HST knot 1.
Assuming V=9 here.
Can I get away with using ACQTYPE=POINT here? PC image shows marginally-resolved source.Timing link suitability includes constraints ([Group (03 04) Within 1.0 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode./private/var/folders/7m/_r88cxcn2vnftcvq56mk6y_40000gw/T/OPVisit2483849206178272006.xml(Tic-Visit
:proposal-id 14631
:visit-id "03"
:proposal-version -1
:trans-version "20170109"
:date "24-Mar-2017 12:52:21.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 243648
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 14631
:visit-id "03"
:obset-id "03"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14631
:visit-id "03"
:orbit-number 1
:pcs-time 333
:si-vis-utilization 2884
:al-overhead-at-end 0
:internal-dur-at-end 388
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3218
:pcs-gap 0
)true10Steve Penton's recommended approach from Cy22/13489
Updated per de Rosa email 11/21/16Updated per de Rosa email 11/21/16Timing link suitability includes constraints ([Group (03 04) Within 1.0 days])The scheduling data was generated by CASM 25.0.CASM was run in Phase II mode./private/var/folders/7m/_r88cxcn2vnftcvq56mk6y_40000gw/T/OPVisit2254982679902320206.xmlSlit position parallel to M87 Jet axis.(Tic-Visit
:proposal-id 14631
:visit-id "04"
:proposal-version -1
:trans-version "20170109"
:date "24-Mar-2017 12:52:27.0"
:trans-errors '(:WARNINGS 0 :ERRORS 0 :HEALTH-AND-SAFETY 0
:FATAL-ERRORS 0 :CONTINUABLE-FATALS 0)
:number-of-orbits 4
:saa-model "24"
:si-bright-earth-limb-angle 20.0
:data-volume 906304
:tdrss-contact-duration 0
:coron NIL
)
(Tic-Obset
:proposal-id 14631
:visit-id "04"
:obset-id "04"
:pcs-mode "FGS"
)
(Tic-Orbit
:proposal-id 14631
:visit-id "04"
:orbit-number 1
:pcs-time 241
:si-vis-utilization 2977
:al-overhead-at-end 0
:internal-dur-at-end 178
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3218
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14631
:visit-id "04"
:orbit-number 2
:pcs-time 176
:si-vis-utilization 3042
:al-overhead-at-end 0
:internal-dur-at-end 178
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3218
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14631
:visit-id "04"
:orbit-number 3
:pcs-time 176
:si-vis-utilization 3042
:al-overhead-at-end 0
:internal-dur-at-end 178
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3218
:pcs-gap 0
)
(Tic-Orbit
:proposal-id 14631
:visit-id "04"
:orbit-number 4
:pcs-time 176
:si-vis-utilization 3042
:al-overhead-at-end 0
:internal-dur-at-end 440
:dark-offset NIL
:dark-utilization 0
:max-dark-utilization 1920
:low-sky "N"
:pcs-visibility 3218
:pcs-gap 0
)true40Nucleus is close to a point source, but may be extended. Can I get away with using ACQTYPE=POINT? PC image shows marginally-resolved source.
Based on advice from STIS team, I'm choosing a 5x5 pix search box.
Assuming F(5500)=4e-16 erg/cm/s/AngNucleus is close to a point source, but may be extended. Can I get away with using ACQTYPE=POINT? PC image shows marginally-resolved source.
Based on advice from STIS team, I'm choosing a 5x5 pix search box.
Assuming F(5500)=4e-16 erg/cm/s/AngNucleus is close to a point source, but may be extended. Can I get away with using ACQTYPE=POINT? PC image shows marginally-resolved source.
Based on advice from STIS team, I'm choosing a 5x5 pix search box.
Assuming F(5500)=4e-16 erg/cm/s/AngNucleus is close to a point source, but may be extended. Can I get away with using ACQTYPE=POINT? PC image shows marginally-resolved source.
Based on advice from STIS team, I'm choosing a 5x5 pix search box.
Assuming F(5500)=4e-16 erg/cm/s/Ang