Hello Han,
how to activate this? I just find the online link to the AAVSO page in the browser for a selected field, but no transfer of names. Also not later in the AAVSO report.
Regards Achim
Last edit: achim2205 2022-08-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
At the moment it is only available from the tab photometry. If you select "annotate...." in the tab and double click on a file in the tab it will annotate the reference stars and variables. See attached screenshot and the red marked settings.
It is not implemented in the viewer popup menu. Probably it is easy to implement there also. I will have a look today.
It is already implemented. If you select in the viewer under pulldown menu TOOLS, "Variable star annotation" it will download and annotate according the setting in tab "Photometry." I will update the hint of this menu as follows:
Annotate all variable stars and comparison stars from the local database or AAVSO online database. Database setting is in tab Photometry.
What is missing in the AAVSO report?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is set always set to 99, bright stars are of no interest for me ;-)..
I'm using Windows 10.
With Crtl K it worked once (!) but then not again even with 'annote ..' or Ctrl. K. Even not after restart the program and doing everything again until Var's magn. is calculated..
The file has 65 Mb, where shall I upload it?
Regards Achim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I found the problem. The link to AAVSO specified a negative FOV. This is because the CDELT2 keyword value is negative. . The image was solved by Pinpoint. Probably an effect by a flipped image. I will fix it and upload a new ASTAP version today.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
But now the next issue (use the same fits-file): As you see NSV 6690 is a PGC galaxy. And the issue is with the aperture / annulus and different results for the magnitude.
Aperture / Annulus / Magnitude
1 / 8 /17.295
2.4 / 8 / 16.785
3 / 8 / 16.617
3 / 10 / 16.594
max. / --- / 16.467
Regards Achim
Last edit: achim2205 2022-08-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I see. Yes the galaxy should be excluded. So something like 0.5 /12/ 17.43 or 0.25/12/ 17.54 seems the way to go. Note the diameter are expressed in hfd's The mean HFD is 3.9 so aperture of 0.25 is one pixel.
Hello Han,
I used AstroImageJ as a comparison:
--> max. / --- / 16.467 is the correct value
I'm afraid, how to find the correct annulus / aperture settings in ASTAP?
Regards Achim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The problem is that the galaxy is disturbing. AstroimageJ max aperture can't be the correct choice.
You should exclude the galaxy so in this case the aperture should be less then 1 HFD. The problem with your image is that the galaxy is very small. It would be better if you would have a better resolution but that is likely impossible with the seeing. The best you can do is to reduce the aperture to one pixel so 0.25 HFD. According the above link the error is still acceptible but we will never know how much the galaxy disturbs. Maybe it is good to have a look to Gaia data for this star.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Gaia only tells me the star has a magnitude of Bp=17.51125 this is equivalent to unfiltered visual. No variable flag found if you look into https://gea.esac.esa.int/archive/
pmRA pmDE G BP RP
Source RA_ICRS (deg) DE_ICRS (deg) Plx (mas) (mas/yr) (mas/yr) mag (mag) mag (mag) mag (mag)
How is it possible that Gaia Bp magnitude is 17.5 and AAVSO report is about V=16.25 ?
Are there any other older AAVSO reports? Could not find them.
This I found in Simbad annotation of the galaxy:
A paper on ArXiv suggest that the two supermassive black holes in this galaxy may merge in 2022 see https://arxiv.org/pdf/2201.11633.pdf for details.
Observations of the merger could be diagnostic of what happens when 2 SM Black Holes merge. The expected signal is expected to be outside the range of the Ligo / Virgo detectors but may be visible in the EM spectrum and possibly in Neutrinos.
The light curve in the above document indicates a magnitude between 17 and 17.5. The period and amplitude is more interesting the the absolute value.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Han,
how to activate this? I just find the online link to the AAVSO page in the browser for a selected field, but no transfer of names. Also not later in the AAVSO report.
Regards Achim
Last edit: achim2205 2022-08-01
At the moment it is only available from the tab photometry. If you select "annotate...." in the tab and double click on a file in the tab it will annotate the reference stars and variables. See attached screenshot and the red marked settings.
It is not implemented in the viewer popup menu. Probably it is easy to implement there also. I will have a look today.
Regards, Han
hmm, nothing happens, see screenshot. For reference the AAVSO chart of that area
Regards Achim
Hello Achim,
It is already implemented. If you select in the viewer under pulldown menu TOOLS, "Variable star annotation" it will download and annotate according the setting in tab "Photometry." I will update the hint of this menu as follows:
What is missing in the AAVSO report?
in tools and the photometric tab nothing happens, just 1 bing in each at the end.
AAVSO report, see attachment
The annotation using the tools menu CTRL+K works here. See attached for "Annotation online mag 99"
Are you using the Windows or Linux version?
I think you have to increase online setting to down to 99.
Can you attach one of the original FITS files?
Last edit: han.k 2022-08-02
It is set always set to 99, bright stars are of no interest for me ;-)..
I'm using Windows 10.
With Crtl K it worked once (!) but then not again even with 'annote ..' or Ctrl. K. Even not after restart the program and doing everything again until Var's magn. is calculated..
The file has 65 Mb, where shall I upload it?
Regards Achim
Strange, this must be fixed.
upload it to:
https://ufile.io/
and give me the link.
https://ufile.io/zcicnj94
did you get the link? "Post awaiting moderation' is shown
I got the FITS file after some trouble. I first it gave me an executable!!? Probably time to abandon this site.
I got an error and a beep with your file. Now I can find the cause....
I found the problem. The link to AAVSO specified a negative FOV. This is because the CDELT2 keyword value is negative. . The image was solved by Pinpoint. Probably an effect by a flipped image. I will fix it and upload a new ASTAP version today.
I'm checking some other things. The images only solves with H18 database. Not with the V17.
Okay fixed. Try this version:
http://www.hnsky.org/astap_setup.exe
ASTAP doesn't write files with negative cdelt2. For your files to solve the H18 is required.
I made today a very significant change in the code structure. Hopefully I didn't break anything. Please report any new problem.
Mit freundlichem Gruss
The file solves better with less stars since it goes pretty deep. Then you could still use the V17. Use this setting:
Thanks, Han, seems to work. AAVSO-report also.
But now the next issue (use the same fits-file): As you see NSV 6690 is a PGC galaxy. And the issue is with the aperture / annulus and different results for the magnitude.
Aperture / Annulus / Magnitude
1 / 8 /17.295
2.4 / 8 / 16.785
3 / 8 / 16.617
3 / 10 / 16.594
max. / --- / 16.467
Regards Achim
Last edit: achim2205 2022-08-02
I see. Yes the galaxy should be excluded. So something like 0.5 /12/ 17.43 or 0.25/12/ 17.54 seems the way to go. Note the diameter are expressed in hfd's The mean HFD is 3.9 so aperture of 0.25 is one pixel.
0.7 /10/ 17.38
0.7 /12/ 17.38
0.5 /12/ 17.43
0.3/12/ 17.53
0.25/12/ 17.54
Instead of scroll you could measure in the viewer with the cursor:
1) Change aperture/Annulus
2) recalibrate by pulldown menu tools, calibrate photometry.
3) Measure with mouse cursor
Do you have an other program to compare?
Regards, Han
Hello Han,
I used AstroImageJ as a comparison:
--> max. / --- / 16.467 is the correct value
I'm afraid, how to find the correct annulus / aperture settings in ASTAP?
Regards Achim
Aperture size is a choice by the "operator"
page 9:
http://burro.case.edu/Academics/Astr306/Lectures/Photometry.pdf
The problem is that the galaxy is disturbing. AstroimageJ max aperture can't be the correct choice.
You should exclude the galaxy so in this case the aperture should be less then 1 HFD. The problem with your image is that the galaxy is very small. It would be better if you would have a better resolution but that is likely impossible with the seeing. The best you can do is to reduce the aperture to one pixel so 0.25 HFD. According the above link the error is still acceptible but we will never know how much the galaxy disturbs. Maybe it is good to have a look to Gaia data for this star.
Gaia only tells me the star has a magnitude of Bp=17.51125 this is equivalent to unfiltered visual. No variable flag found if you look into https://gea.esac.esa.int/archive/
pmRA pmDE G BP RP
Source RA_ICRS (deg) DE_ICRS (deg) Plx (mas) (mas/yr) (mas/yr) mag (mag) mag (mag) mag (mag)
1254429624969681664 217.56683873932 +23.06237008752 1.9647 -2.262 2.044 19.091570 17.511250 16.038550
Hi Han,
the nature of this object is a Seyfert galaxy is described in https://en.wikipedia.org/wiki/SDSS_J1430%2B2303 . It's supposed to be binary supermassive black holes near to the merger "which could be observed before the end of 2022". That's why many astronomers are monitoring it's light curve behavior. The light curve can be found at https://www.aavso.org/LCGv2/index.htm?DateFormat=Julian&RequestedBands=&view=api.delim&ident=000-BPG-795&fromjd=2459594.502826588&tojd=2459793.389653&delimiter=@@@
Regards Achim
Last edit: achim2205 2022-08-03
How is it possible that Gaia Bp magnitude is 17.5 and AAVSO report is about V=16.25 ?
Are there any other older AAVSO reports? Could not find them.
This I found in Simbad annotation of the galaxy:
The light curve in the above document indicates a magnitude between 17 and 17.5. The period and amplitude is more interesting the the absolute value.