- This topic has 5 replies, 3 voices, and was last updated 4 months, 2 weeks ago by
.
-
Posts
-
Hi folks,
Currently I upload my Exoplanet observations to the Exoclock website and I have just started adding it to the ETD too. My question is – should I also be uploading it to the BAA Photometry Database? I can see a few sets of data in there, but not much.
If so, would it be best to upload the magnitudes that come out of the HOPS software (which is my preferred software tool for Exoplanets).
Many thanks
Ian.Hi Ian,
If you can easily do it then yes. It can be useful to have it in more than one database to ensure longevity of the data. However, Exoclock is what matters, as the master database for this data.
The difficulty you may find is converting the output from HOPS into one of the file formats used by the BAA. If that is difficult, then don’t bother.
We have some Exoplanet data in the photometry database. This was uploaded a few years ago, prior to Exoclock.
Best wishes,
Andy Wilson, BAA Photometry Database ManagerThe difficulty you may find is converting the output from HOPS into one of the file formats used by the BAA. If that is difficult, then don’t bother.
Hi Andy,
Yes, quite tricky! It’s the comparison stars that are hard to deal with. As far as I can see, exploring the various output files, the pixel co-ords of the comp stars are stored in the log.yaml file, but no details about them. I could locate them on a chart and then enter that data but it will certainly be fiddly!
Cheers
Ian.Hi Ian,
In that case I would not bother. At this time, other BAA Exoplanet observers are just submitting to Exoclock.
Exoclock was not in existence when I made the amendments to allow the BAA Photometry Database to accept Exoplanet observations. As I understand it, the Exoclock project has plans in place to keep the data publicly available for at least 50 years. I’m not involved in Exoclock so I can’t guarantee this, but it appears they have a solid approach to data retention and accessibility.
Cheers,
AndyThe difficulty you may find is converting the output from HOPS into one of the file formats used by the BAA. If that is difficult, then don’t bother.
Hi Andy,
Yes, quite tricky! It’s the comparison stars that are hard to deal with. As far as I can see, exploring the various output files, the pixel co-ords of the comp stars are stored in the log.yaml file, but no details about them. I could locate them on a chart and then enter that data but it will certainly be fiddly!
Cheers
Ian.How I would deal with this is to write a few scripts. It’s what I did a few years ago to upload to the BAA database.
First make sure that at least one of the images showing the target and the comparisons has an accurate WCS. If none do, astrometry.net, either on-line or self-hosted (my solution).
The coordinates of the target star are presumably well known, what are not are those for the comparisons but if you have a list of (x,y) coordinates and a WCS, the xy2sky program from the WCS tools utilities will produce a list of (RA,Dec) coordinates. Easily scriptable.
Given those, from I download a subset of the GAIA catalogue centred on the target and wide enough to include all the comparisons. Quarter to half the FOV is a reasonable estimate. https://vizier.cds.unistra.fr/viz-bin/VizieR-3?-source=I/350&-out.max=50&-out.form=HTML%20Table&-out.add=_r&-out.add=_RAJ,_DEJ&-sort=_r&-oc.form=sexa is a starting point. Customize the search fields until you have nailed down the query you want, then copy the URL for use as a prototype in subsequent searches. I tend to ask for the J2000 coordinates, either G magnitude or RP magnitude (depending on whether the images were unfiltered or V for the former, R or SR for the latter) and its error, and the G-RP value. Ask for lots of lines in tsv format.
Given that data, filter out all stars which are more than a few magnitudes brighter or fainter than the target. Reject all stars which are markedly different colour from your target. Finally, search in the remainder for stars which lie within a few arcsec of the list of coordinates you produced earlier. Remember that stars have proper motions; I have been bitten by this one before!
After all that, you have a sequence of comparison stars ready to be fed into your regular photometry program.
This is my procedure for exoplanets where good sequences do not exist at, say, AAVSO, and for asteroids where they rarely do so.
If you speak Perl, there’s a good chance that much of the scripting required can be provided. Contact me off-list if you wish to give it a try.
Good luck!
If you speak Perl, there’s a good chance that much of the scripting required can be provided.
Thanks Paul,
I have all the tools I need in my Python/AA8 system I have developed. I can query APASS/AAVSO/GAIA/Vizier in my Python code and match the results to the plate solved images in AA8.
Cheers
Ian.
- You must be logged in to reply to this topic.