-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add VERITAS data #10
Comments
Apparently there are plans to collect VERITAS data at HEASARC. See #11 (comment) by @GernotMaier . @GernotMaier -- Do you know if there's an ETA for this? Is this coming soon or is this something that might come in a year or two or never? |
You know how collaborations work: we form a working group now, we discuss with the HEASARC the format, and then we need to collect all the data from the publications. So I wouldn't expect anything before Spring. |
OK. So just if someone else comes across this issue:
|
@GernotMaier - FYI: Since yesterday, @pdeiml is doing data entry for gamma-cat. He's doing the CTA 1 VERITAS publication now: Can you provide spectral points for this paper? Actually I haven't been able to find any VERITAS spectral point data in electronic format yet. |
The spectral points are in Table 1 in the paper. I completely agree that VERITAS is very bad in providing their data in electronic format. We have in principle that rule, but somehow it does not seem to work. |
OK, I'll copy & paste the spectral points from the PDF now. I've looked around a bit on the http://veritas.sao.arizona.edu/veritas-science page and haven't been able to find any data in electronic format. So if you could point out data that is available in electronic format to us, we'll reformat it and add to gamma-cat. Otherwise, we'll but the VERITAS corresponding authors or you from time to time. |
Some results have FITS or text files (e.g. http://veritas.sao.arizona.edu/veritas-science/veritas-results-mainmenu-72/423-template). But we don't have a well defined file format, most of the data is anyway a simple table. |
Thanks for this link!
That doesn't matter much. We have to reformat and add some meta info on data entry anyways. |
@GernotMaier added a lot of VERITAS data in the past months and plans to add more. Gernot - I'm assigning this general reminder issue to "add VERITAS data" to you. |
Good - this will still take a while (about 50% done). Below the current statistics ('done' means includes in gamma-cat; not counting proceedings):
|
@GernotMaier - Could you please add folders and very small Examples: 7586417 If we have those I'll try to find the time to add the missing publications / info.yaml files for HESS soon. Let me know if you have any questions or comments about the info.yaml files. |
Will do - but will take a while. |
I see that info.yaml files have been added to the existing VERITAS papers: is it correct that you set by default for all of them status: incomplete I just want to know what my starting point is. |
Yes, we put reviewed: no for all of them. It's not used for now, but at some point there might be a review of data entry completeness or accuracy. Or maybe never, there it's not clear if this will be useful. The status is supposed to be set in a useful way, with the following logic:
There is a single "notes:" entry that can be added for a given paper, where you can leave notes if you think it'll be useful to your future self or others, e.g. "spectral points missing" or "this paper has no spectral points" or "have to check value XYZ with Jimbo". This is just a starting point, of course we're open to feedback and improvements to |
An update on the status of the VERITAS papers:
|
Progress table(please ignore the last column)
|
VERITAS has published a lot of results (images, lightcurves, spectra) in FITS format:
http://veritas.sao.arizona.edu/veritas-science/veritas-results-mainmenu-72
We should add it here.
Ideally this should be done via Python scripts that download and re-format the data to our formats, so that it's reproducible. Or course contributions that manually add the data in our format would be welcome as well.
The text was updated successfully, but these errors were encountered: