Skip to main content

HST campaign on TCP J21040470+4631129 - Alert Notice 714

14 posts / 0 new
Last post
weo
weo's picture
HST campaign on TCP J21040470+4631129 - Alert Notice 714

AAVSO Alert Notice 714 announces an observing campaign on the WZ Sge-type variable TCP J21040470+4631129. Please see the notice for details and observing instructions.

Many thanks, and Good observing,

Elizabeth O. Waagen, AAVSO HQ

BorisGaensicke
2nd attempt

Here just a bit of background...

We were planning to obtain ultraviolet spectroscopy of this  unique CV (you may think we say that about each and every CV, but this one is truly fascinating!) on April 10th, which was thwarted by the superoutburst that was detected on March 31st. Observing the system in outburst would have, in the best case, shut HST down into a safe mode, which takes a few days to recover. In the worst case - it would fry the detector of the COS instrument. That's why the ground-based monitoring is so important.

Because real-time communication with Hubble is limited, the telescpoe runs automously, executing a week's worth of commands that get up-linked in advance. So how do we deal with CVs going into outburst? The trick is to have two sets of co-ordinates in the observation: one is the CV, the other one a blank spot a few arc-sec away. The default position is the blank field.

On the day of the observations, we communicate the results of the latest observations to STScI - if they are satisfied that it is safe to observe the CV, they up-link a single command to HST which swaps the two pairs of co-ordinates, so the CV is observed. If that command is not sent ... HST stares at a blank piece of sky - which gets you a very expensive spectrum of the sky background at ~340 miles above sea level!

In April, thanks to the alerto to the superoutburst, we immediately got in touch with STScI. They were just about to up-link the program for the next week, but, with one hour left to go, managed to pull the observations of TCP J21040470+4631129 from the schedule! So we avoided wasting precious Hubble time, and got a 2nd chance.

Fingers crossed the star co-operates this time!

Clear skies,

Boris

 

 

 

 

tiburd
"Fainter than" guidance?

Recent entries in the AAVSO database include several "fainter than" observations for this star, with thresholds ranging from "fainter than 15" up to "fainter than 12.5."  A friend of mine raised the question of just how bright a "fainter than" observation could be and still be adequate to protect the Hubble?  For instance, I'm confident that a "fainter than 8.0" observation would not be helpful, but I don't really know the answer to his question.  Any guidance on that would be appreciated, and would also be helpful for any future alerts involving the Hubble.

BorisGaensicke
To allow the HST observations

To allow the HST observations to go ahead, STScI requires  an actual detection of the target at the quiescent level within 24h prior to scheduled time of the HST observations. However, fainter than reports that are close to the quiescent level (a few tenth of a magnitude, i.e. "V<15" for TCP J21040470+4631129), are still very useful in case that there are gaps in the detections, or some discrepant magnitudes among the detections in the last few days before the HST observations.

 

Coles44
Collected data on TCP J21040470+4631129

Stella Kafka was our presenter on The Astro Imaging Channel last night. At the end of the session I told her that my imaging setup at the Sierra Remote Observatories was sometimes (including Sunday night) available to collect data for an AAVSO project. Your project was suggested.

Last night I collected six hours of subs for that target using the suggested G filter. Each sub was 300 sec long. The data is calibrated (not registered), in FITS format and waiting for instructions as to what to do next. Please advise.

Eric

weo
weo's picture
Hello Eric,

Hello Eric,

Thank you for observing TCP J21040470+4631129 for this campaign! Your images need to be reduced to magnitudes for the target and the magnitudes and their dates/times (and other information) submitted to the AAVSO International Database. I will email you privately to connect you with the necessary resources.

Best wishes,

Elizabeth Waagen, AAVSO HQ

 

weo
weo's picture
HST date/time set for TCP-J21040470+4631129 observations

The HST observations of TCP-J21040470+4631129 (AAVSO Alert Notice 714) have been scheduled for

Sep 12, 2020 07:16:37 to 13:07:28 UT

For the HST observations to take place, it is essential to have a positive observation 24 hours before this time showing the system in quiescence, so the night of September 10-11 UT is crucial.

Please continue nightly V snapshots through September 8, then more intensive monitoring September 9 through 12, then nightly snapshots through September 15. Please report observations promptly, especially from September 9 through 12.

Many thanks, and Good observing,

Elizabeth

Coles44
HST date/time set for TCP-J21040470+4631129 observations

Elizabeth,

Get back to me an advise what to do with my subs. Also the next day or two are full moon time and not good for imaging. My setup is available.

Thanks.

Eric

BorisGaensicke
Entering the critical last week

Dear All,

thanks so much for all the observations of TCP J21040470+4631129, its been very reassuring to see it nice and calm.

But.

I am a little nervous, for the following reason: the timespan between the first and the second-super-outburst were ~105d, and between the second and third one ~111d. Since then, another ~156d have passed, with no more sign of activity. Has this star exhausted its "fuel", i.e. material that has been stored up in the accretion disk over who-knows-how-long (we don't know how long the outburst recurrence time is ... decades, or more?), or is it merely taking a bit more time to build up steam towards another super-outburst? The behaviour of this system is unique so far, in having had an initial mega-outburst(*), followed by a few echo-outbursts, and then three super-outbursts, so we don't really know what to expect.

Thus, please keep an extra close eye on our TCP J2104+4631 throughout the next week, to make sure the COS spectrograph remains safe!

We will have to report a detection of the system at its quiescent magnitude to STScI on noon (EDT) Friday Sept. 11th. Therefore observations Thursday night, pushing as far into Friday morning as visibility allows are particularly important (US observers will have an advantage here). And please report the data as soon as you get them.

Thanks so much for supporting the HST observations of this CV!

Boris

(*) what is the right terminology for the different types of outbursts that TCP J2104+4631 displayed? I just made up the term "mega-outburst", to set it apart from the three super-outbursts.

 

 

 

 

 

weo
weo's picture
Tonight critical for TCP J21040470+4631129 coverage

Tonight (2020 Sep 10-11) is critical for coverage of TCP J21040470+4631129 - please see Boris' post above; quoting from it: "We will have to report a detection of the system at its quiescent magnitude to STScI on noon (EDT) Friday Sept. 11th. Therefore observations Thursday night, pushing as far into Friday morning as visibility allows are particularly important (US observers will have an advantage here). And please report the data as soon as you get them."

Also, please continue your coverage through at least Sep 12 (see the Alert Notice).

Many thanks and Good observing,

Elizabeth

BorisGaensicke
Decision point: 9am EDT

We have had an update from STScI that they need to anticipate the decision whether they consider it safe to observe TCP J21040470+4631129 with Hubble by three hours. That means the need to have the latest measurements of the brightness of the system by 9am EDT on Friday, Sept. 11th.

Thanks for your help with this, and clear skies!

Boris

Bikeman
Bikeman's picture
FWIW, it was still near 15.8

FWIW, it was still near 15.8 mag (V) at  2020/09/11 03:56:11 (UTC) when I lost it in twilight and clouds. 

Over to observers in North America.

Good luck!

http://bikeman.selfhost.eu/astro/aavso_alerts/a714_20200911_last.png

BorisGaensicke
We are go for tomorrow's COS observations

STScI approved the COS observations for tomorrow. What happens next is that the flight engineers at NASA Goddard will send a tiny command to Hubble to swap the two sets of co-ordinates stored in the on-board observing program, so that TCP-J21040470+4631129 will go into the aperture of COS, rather than the blank sky position that was the safety default.

Thanks so much for all your observations, without which this HST program would not have been possible. 

BorisGaensicke
Success - almost!

First of all, thanks so much for your detailed observations of TCP J21040470+4631129 that were the key to get the HST observations through the final approval stage.

The HST ultraviolet observations of this CV went ahead, and the spectra we got reveal a fantastic amount of detail: the white dwarf totally dominates at ultraviolet wavelengths, and is still rather hot, in fact, hotter than any similar system a year into cooling from the outburst.  That is consistent with the outburst having been tremendously large and long, and we will be able to work, among a number of things, out how much energy was dumped into the white dwarf during the outburst. What is clear is that it will take the star many years to cool back into quiescence.

But, as mentioned, in the subject, there is a "but": during two of the six exposures, the COS shutter remained closed. It took a few days to figure out the reason - and to our relief, it wasn't the star misbehaving, or a mistake in the observing sequence: Hubble struggled for some time to acquire the guide stars it needs for the precision pointing, and for safety reasons the COS shutter remains closed in that case.

We're still establishing how much the loss of data affects the goals of this program, and there is a possiblity that the failed observations may be repeated. For that reason, it would be very helpful to continue  monitoring of TCP J21040470+4631129, though at a less intense level, maybe a few snapshots per week.

I'll get back in touch in a week or two.

Boris

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Log in to post comments
AAVSO 49 Bay State Rd. Cambridge, MA 02138 aavso@aavso.org 617-354-0484