Blazar S5 1803+78 is rapidly brightnening. Observers in Spain and Germany have contributed recent observations, but the weather in Europe has been overcast and probably will be until at least this weekend. Observations outside of these areas are encouraged until the weather clears. The next several days may be critical as the blazar seems to be reaching a peak magnitude. Please make observations if possible and upload to light curve for S5 1803+78.
Against expectations, the sky cleared up and I'm currently taking frames .. I'm right at the edge of a cloud system ... not sure how long this will last, but the target is still bright so I a meaningful measurement is almost certainly possible already.
To be honest, Gianpiero Locatelli from Italy was the first to confirm the Blazar explosion.
The next day Jordi Berenguer was from Spain, he confirmed it even more.
I also appreciate the observations of Heinz-Bernd Eggenstein from Germany who also provided this confirmation of the Blazar S5 1803+78 explosion.
I sincerely thank all three for their confirmation and possible monitoring. It is really interesting to watch.
I thank Dave Hinzel for putting this thread in and getting us together so we can get ahead of NASA 4 days before his confirmation on his Atel.
All of this was triggered by a simple observation from David Lane a few days earlier. It had to be confirmed.
I wanted to do some observing but the iTelescope site in Nerpio, Spain has been shut down due to a combination of bad weather and problems of getting people to the site because of the pandemic. So, we might have to sit this one out unless there are observers in other locations that can do observations.
Here is another ATEL on "our" blazar:
The reoported data points are , IMHO, not as impressive as the light curve that was collected here, so I wonder if this group here should do its own ATELs in the future for similar events. I notified one of the ATEL's authors about the obsevartions collected here, but got no response so far.
Are ATEL and AAVSO normally in communications or is this a one time event? If there is good communications we should use them as much as possible, but if not then an AAVSO "internal ATEL" is a good idea since we published before they did. What do you think?
I think it's not uncommon that AAVSO amateur observers publish ATELs , e.g. Josch Hambsch and Tonny Vanmunster for CVs. I guess the threshold is "would other astronomers find it useful", as when responding to urgent observation requests in other ATELs or when observing something rare or unexpected. Here, the current flare seems to be pretty record-setting, even more than reported in ATEL 13711 because they observed one week after we observed the peak, so if their observations were "good" for an ATEL, I guess our's are even more so :-)
Just my 2 cents.
I've just finished measuring some image form iTel11 in New Mexico *last night* and it was back at 14.44 mag (V) . This night I'm trying to continue observing it from Germany but conditions are not optimal.
For comparison, the brightest V value in the light curve for the recent flare was close to 14.1 , the object made a "V shape recovery" :-)
S5 1803+78 is overlapping a 17.5 magnitude comp star, at least in my image anyway.
The aperture annulus is at 3 pixels with angular resolution of 2.54" per pixel. I can't separate the two without going to a higher focal length or smaller pixels. My question is should I just scrap my data?
I have a really hard time recognizing the field from your image, The image seems to be blurred or have JPEG artifacts in it, perhaps?
Are you really sure this is infact S5 1803+78? I take images which are a bit oversampled at 0.5" / pixel, so I resampled one of my images to 20% the resolution to simulate a 2.5"/pix resolution, and I get something like the attached image. It should still be possible to avoid overlap with the nearest star that is bright enough to affect the photometry, especially the 17.5 star on AAVSO finder charts (the one I placed in the inner annulus in my simulated image).
If you like you could upload the FITS image and have us look at it. I really think there is something going wrong here.
Ahhh ok, I see. The screenshot was from VPHOT with a single frame, and I got distracted by some bad pixels and mistook them for stars, Sorry for my ignorance,
Anyway, this is interesting!
The position that VPHOT tells you is comp star 175 is actually significantly wrong! I guess VPHOT just calculates where the star should be according to the plate solving, and then looks for the nearest centroid, allowing some very generous deviation from the calculated position, and ends up snapping the centroid to our target star (see the end of the post for a fix).
What is worse is that the "Measurement details " that VPHOT optionally displays for each comp star is misleading and wrong:
You get this (I did that for the stacked V image you sent me )
Huh??? Catalog location and estimated position are a perfect match in RA and Decl?? That's suspicious and actually wrong, because if you look it up in the finder chart table, the actual coordinates for 175 are :
So...that 175 star really isn't nearly as close to the target star as VPHOT makes you believe, and is indeed easily avoided by chosing the aperture wisely (e.g. radii 4-8-4 in the aperture settings) . That 175 comp star is just too faint to be detectable even in the stacked V frame (it's kind of visible in the stacked I frame, tho), so VPHOT just tries a bit too hard to identify it in your images and misidentifies it in the process.
How to fix this? Fortunately VPHOT allows you to configure the way it tries to identify stars on the frame ==> Tools ==> Settings > Centroid Determination,
When I went there, "it displayed Search-radius in Pixels" : 5 and "Initial FWHM (pixels)" : 5
Because your plate scale of 2.54" / pixel is a bit on the coarse end, 5 pixels is a bit too generous. If you try setting both to 3, then when you load the comp stars from the AAVSO, VPHOT will no longer even give you the 175 star because it fails to identify it on your frame with sufficient SNR, and this is the right thing to do. Because the limits for trying to identify the star near it's computed position are now less generous, VPHOT will no longer mistake the target star for star 175.
So mystery and (perceived) problem solved I guess, You can do photometry and submit it all right, just don't include the 175 star or configure VPHOT in the described way so VPHOT won't misidentify it.
The whole thing is captured in the attached screenshot. It shows the stacked I-filter frame you sent me.
I put a crosshair to the right of the 175 star to highlight it, I made the aperture avoid that star, and in the right top corner you see the config dialog that lets you pick the parameters for identifying stars in VPHOT.
Hope this helps,
I believe the AAVSO criteria for good data is as follows:
Star SNR >= 10 (which your measurement is).
Magnitude estimate error <0.05 good; <= 0.015 excellent; 0.05 to 0.100 still worth reporting to AAVSO; >0.100 probably shouldn't report.
Hope this helps.
More than two month after what must have been one of the brightest recorded flares of S5 1803+78, it still refuses to go back to its optical pre-flare state (at around 16.5 mag (V) ).
The weather is horrible in Germany now (I should not complain tho, the rain is much needed after a record braking dry spring). Even some iTelescope New Mexico observation was cancelled because of high winds :-( . I hope others have more luck, I'm sure the data will be useful .
Meanwhile there is a clear signal in the gamma ray lightcurve (the link above is for a daily updated lc), It shows some day to day variability so I guess it will be interesting for scientists later to compare the optical and gamma ray lightcurves ==> let's keep observing this one.
I'm new to this group and I have questions regarding the submission of observation to the AAVSO database. My setup is a 14" RC scope with STX16803 CCD camera in Spain.
I took an image of S5 1803+78 with a Luminance filter (I don't have photometric filters) and I am not sure what to do next. I navigated to the AAVSO "enter observations individually" page. Is it where to submit the observation? Do I need to stack multiple images or are you looking for a single image? Calibrated or not?...
Welcome! That is some impressive equipment, I'm sure this will be useful! Even without photometric filters, you can still submit datapoints for observations thru a clear filter (or no filter).
I see you already have an observer code...so you are good to go.
This will be the first observation you submit? I guess then this is a good starting point, it covers every aspect from taking the images to reducing the data to magnitude values to submitting to the AAVSO:
Note that if you are an AAVSO member, you can use the online tool VPHOT for reduction :
Thanks for your message. I am familiar with the raw images calibration process and also with photometry of exoplanet transits as I have observed over 40 such events as part of the Exoclock program. My question is not so much about how to reduce the raw images and what photometry is about but rather in the specific case of Blazar observation submission:
Whether you want to see raw images, calibrated or not
If images should be stacked to reach a specific S/N ratio
Ah sorry, from your AAVSO database record and your message it wasn't quite clear to me what your level of experience is. All the better that you are already familiar with the technique.
> Whether you want to see raw images, calibrated or not
That's usually not done here unless the result is so unusual that people want to investigate what could have caused the deviation. Just submitting the results to the DB is fine.
> if images should be stacked to reach a specific S/N ratio
I guess with a scope like yours, you'll need (say) just a few minutes of total exposure to get a good SNR ( say, 100), stacked or single frame. Runs of time series (as with exoplanet research but nowhere near the SNR needed for exoplanet transits, SNR 100 is good enough) might even be useful to capture variations on the timescales of minutes to hours.
My latest measurement has the V magnitude very close to the peak in April again (!!!)
The weather here is Germany is not good at the moment and using iTelescope is getting a bit expensive, I hope others have a clear sky to observe this new (re)brightening. I think this prolonged period of activity with now 3 distinct flares in a relatively short time is quite unprecedented in the data for this source.
Indeed, the webobs->Upload page iis for uploading AAVSO report files, text files containing the reduced magnitudes. The format is explained here:
put many photometry software packages can generate the files for you.
Which software are you using for the reduction?
If you arfe an AAVSO member, you can use VPHOT
as already mentioned, and there you can indeed upload a FITS file and perform the reduction in a web interface. There is no need (or storage) to upload FITS file for permanent archival, only the measurements are going to the database.
Does that answer your questions?
For ca past 160 days, S5 1803+78 has shown a roller coaster ride between multiple flare events, but never actually returned to its pre-flare level.
A week or so ago it looked like it was finally taking a dive, and maybe observers are now getting a bit of fatigue from this object (plus observers in California are having a hard time with fires and smoke at the moment.....) BUT observers should really try to stick to this object because .... it is now more or less stable again around 15.1 +/- 0.1 mag for the last 4 days or so. Hmm....what will it do next?
The AAVSO now has a very dense lightcurve for those last 160 days of activity, it would be great if we could keep it well sampled until it finally goes back to 16.5 ish or so.
P.S.: And as a reminder, BL Lac is also still having a flare!
Bummer ... I had hoped to get new data last night from an iTelescope, but it had a slight pointing error ... actually one hour in RA :-( .
Please, anybody who has a clear sky, have a look at S5 1803+78. The Fermi gamma ray Light curve indicates renewed activity as well and a full rebrightening in the next few days is a possibility , if the past light curve is any indication of the current behavior.
Happy New Year everyone!
Yeah I know, it's getting kinda old, but.... S51803+78 is flaring again, as some will have noticed already.
I just got a measurement with iTel's T11 (bad weather here in Germany), and it's at
EDIT : 15.3 V
Please keep observing this one as often as you can. It is totally unusual for this object to show that many flares in such a short time after it's first flare in 2020. Gamma ray observations also show an increase in flux.