Tue, 05/31/2022 - 19:35
From File>Open>AVSOnet epoch photmetry database I enter the coordinates (279.46354 +47.3899), pick B and V filter bands, ignore "Populate Parameters from VSX URL", ignore "VeLa filter" and "Additive Load", then click OK .
I get a red stopsign with the message "for input string "<html>.". If I click Okay here, nothing happens.
If I repeat the process, click the "Populate Parameters from VSX URL" then enter the URL for the VSX page:
https://www.aavso.org/vsx/index.php?view=detail.top&oid=49778 I get "Invalid URL".
What am I doing wrong?
The front door to the Epoch data base is https://www.aavso.org/search-aavsonet-epoch-photometry-database
I was able to use it on your coordinates, though I had to open search radius quite a bit.
Thanks very much George. That is a big help, and I'll work with that for now.
I would still hope for some advice from this forum on how to open the epoch database directly into Vstar.
I just repeated the problem you saw, but I think that the issue is that there isn't any AAVSOnet Epoch Photometry for V742 Lyr. You can see that if you go to that star's VSX record: https://www.aavso.org/vsx/index.php?view=detail.top&oid=49778 then scroll down to "External Links" and select "AAVSOnet EPD" or even "APASS". No data is found.
If you try U Men for example, it works well whether you enter its coordinates into VStar or use the link to the data from VSX.
I hope that helps.
Thanks for your comment. According to the Epoch Photometry list there is data on NSV 11154. This was the designation before it became V0742 Lyr. The NSV designation is shown in the VSX under Other Names, but it might be necessary to Log In to VSX to see it. Since I used the coordinates for the Vstar query, I thought this would not be an issue.
VSX does a coordinate search to display AAVSOnet Epoch data so the fact that the primary name has changed doesn't have anything to do with the empty result.
You say there are observations for NSV 11154 in the AAVSOnet archives, how do you know that?
Also, you don't need to be logged in to VSX to see the cross-identifications. These are visible for the general public.
Thanks for those clarifications.
"You say there are observations for NSV 11154 in the AAVSOnet archives, how do you know that?
I thought I saw it in the list of targets for the Wright 28 telescope, but now I don't see it there, nor V0742 Lyr as Sara commented. I'll rummage around to see if I can find it. It seems I was wrong about that. I apologize to everyone for the wild goose chase.
Have you tried removing "+" from the start of the Declination value?
George, can you say what search radius was used? The plugin allows only a discrete set of radii.
I put in a fov of 0.01 deg and got lots of hits.
The VStar plugin only allows a maximum of 0.005 deg right now, so that may be consistent with what you see and Sara's comment.
This may or may not be related to the radius thing, but I think I have found something odd...
Take the star T UMi and find it in VSX: https://www.aavso.org/vsx/index.php?view=detail.top&oid=37377
Then look at the "External Links" files for both "APASS" and "AAVSOnet EPD". You will see just four observations in the APASS file:
and a whole lot of records in the AAVSOnet file:
When you use the VStar APASS plugin with the link to the APASS data from VSX it works fine.
But if you use the VStar AAVSOnet plugin with the link to the AAVSOnet data from VSX you get "Invalid URL".
However if you use the AAVSOnet plugin with the APASS data URL from VSX, it seems to be working.
Am I doing something wrong?