Forum Replies Created
-
Posts
-
From ATel 16050:
We searched the HST archival data for the progenitor of SN 2023ixf. A clear
source can be seen at the SN position (https://antares.noirlab.edu/loci/ANT2023l4lgj6bhp4rt)
in the F814W image from the HST program 9490 (PI: Kuntz), which was observed
on UT 2002-11-16. The source is, however, not visible in the bluer bands
(F435W and F555W). We measure a preliminary F814W magnitude of 24.39+/-0.08
for the source. Considering it as the candidate progenitor of SN 2023ixf
and using a distance modulus of 29.05 for M101 (Shappee and Stanek, 2011,
ApJ, 733), we obtain an approximate absolute magnitude (no extinction correction)
of -4.66, which is in line with a supergiant progenitor.Payment now successful via PayPal. My thanks to Andy and the BAA Office for their assistance.
I have not posted the BAA’s PayPal account name because of a specific request not to,
Paul
Hi Andy.
Received your mail, thanks.
When that link is clicked the browser still shows an endlessly spinning arc of a circle inside the large blue button. This with “Firefox 113.0.1 (64-bit) Mozilla Firefox Snap for Ubuntu canonical-002 – 1.0”.
Oh well.
Paul
Ian: this sounds most interesting!
Can your driver be used under EKOS?
Perhaps we could discuss this in greater detail by email rather than clogging up the BAA fora.
If you feel up for a real challenge, you could write an INDI driver for the Velleman K8055 series of boards.
This would be a highly non-trivial undertaking but one which would win you kudos with a wide selection of the amateur community. People have been asking for one for years.
At the moment domes with a Velleman controller, mine included, can use only the LesveDome ASCOM controller. The problems with LesveDome is that the source code is unavailable, it is Windows only, and is ASCOM instead of the much more portable INDI.
Yesterday I purchased a Velleman WPI110N (the latest release of the K8055 series) with a view to seeing whether I can persuade it to play ball without having to perform potentially dangerous tests on a live dome.
I call the AAVSO API to get me the VS data and the candidate comparison stars in a requested mag. range and chart width. I use the B-V from SIMBAD to give me a guide to any major differences that there might be in the B-V values of the comparison stars. It’s more of a sanity check
So there is a Sanity Clause after all!
I use it to get the B-V of the target star. I couldn’t find that in the AAVSO data.
Ah.
When I add a new star to my program, I go to https://app.aavso.org/vsp/ and fill in the appropriate fields (Star, FOV, orientation, limiting magnitude, and more) and first get a finder chart, which I print for use at the telescope.
Next the photometry for the sequence in the filters required is downloaded. The B-V values and their errors are provided whether you want them or not, in line with the bottom of the VSP page where we find the words: “V and (B-V) magnitudes are always displayed. Select any other bands you wish displayed below.” A Perl script subsequent mungs the photometry data into a format useful for my current processing pipeline.
I never take a given B-V of the target star as gospel because it can itself vary as the brightness changes. If I want to know a colour index of a VS at a particular epoch I measure it for myself.
Paul,
The sequences for the BAAVSS visual charts have all been entered into the database. When you try to upload a visual observation, it’s checked against the sequence.
[Deletia
If you use an AAVSO chart, our DB doesn’t have any sequence information for these charts.Ah, there’s a thing.
In principle the AAVSO sequences could also be added to the BAAVSS database (assumng they are not there already – I don’t know). Those of us doing ensemble photometry generally include the (instrumental,catalogued) values for the (magnitude, error) of those sequence members which are measurable.
In principle, the BAA database could run sanity checks using those sequences too. Either that, or I am missing something.
Further, the AAVSO database could be scraped occasionally (once a year perhaps) to see what comparison stars have changed. What to do after a change should be obvious — pretty much what happens for BAA sequence changes.
Personally I like the AAVSO charts and lists of comparison stars because it’s easy to query via my Python code via the AAVSO API. I combine that with SIMBAD/VIZIER data to get other parameters of the target star and I can then create a good list comparison stars for ensemble photometry.
That is essentially what I do, though my code is wrotten in Perl rather than in Python.
By and large I download only the V photometry but include B and R as required. B-V, which is provided regardless, give B magnitudes but not, alas, their errors. My ensemble photometry code does The Right Thing with reported errors, which is to add in quadrature.
Out of interest, what SIMBAD/VIZIER data do you use? For my purposes all that is required is the magnitudes and the coordinates, all of which is provided in a single download from AAVSO.
My concern is that perfectly good data elicits a warning. I freely accept that the important stuff (magnitudes and their errors, star ids, date-time. filter, explen) goes through after checking. It’s the appearance and untidiness of an essentially useless warning that irritates me.
Perhaps if the chart ID was in a standard format (/^AAVSO X.+$/ for those who recognize Perl-style regexps, the database checking software could avoid issuing a warning.
Paul
Sure.
I mentioned it because I am thoroughly sick of being admonished by the VSS database for using non-kosher chart IDs.
Big hint there 😉
No thanks are due to me!
I never met Bob, sadly, but have visited the Hacienda San Jorge many times. I was hoping to jog memories of people who were on that expedition.
I think Charles’ Wain predates our monarchs of that name but it’s most appropriate for this weekend.
It undoubtedly does so. The Wikipedia article goes into at least as much detail as you are likely to want. In particular, it has the same name in essentially all Germanic languages.
I think Charles’ Wain predates our monarchs of that name but it’s most appropriate for this weekend.
It undoubtedly does so. The Wikipedia article goes into at least as much detail as you are likely to want. In particular, it has the same name in a number of North Germanic languages.
…and there is Cor Caroli…
https://earthsky.org/brightest-stars/cor-caroli-heart-of-charles/
Now well-placed for images of the starfield.
Tucked inside the handles of Charles’ Wain. You can’t miss it.An equivalent way of saying this, though it needs considerably deeper understanding of QM, is that the uncertainty principle follows inexorably from the properties of the Fourier Transform.
The linkage is that a quantum state is fundamentally a function of complex numbers, whereas in classical mechanics everything is purely real.
Some of you may know why that the question of the existence of uncertainty principle relating energy to time, and why it has the same value as position-momentuum relation is very far from obvious, largely because time is not a quantum operator. A fascinating journey down a rabbit hole finally gives a good answer to that question, but the reasoning is very far from obvious.
Hacienda San Jorge in Los Concajos perhaps?
The architecture and colour scheme look rather familiar.
On my last trip to La Palma I took some images in Sloan i’, r’ and Johnson V (I don’t have any other JC filters nor Sloan g’) of the M67 Landolt field. The primary interest is photometry calibration but I also realised that tri-colour images should be possible, even though they may look odd.
The images have not yet been processed but I will report back later.
Paul
