-
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
Relation to CDS, SIMBAD, VIZIER #11
Comments
@GernotMaier I've written up a first draft of the https://github.com/gammapy/adass2016-gamma-cat-poster/blob/master/paper/P6-7.pdf I currently have this:
For me it's hard to see how SIMBAD and Vizier could be a working solution to collect TeV gamma-ray data at this point. A separate project driven by gamma-ray astronomers, with community feedback about what data / formats are wanted, iterating on the data archive and formats for a while seems best. @GernotMaier @cboisson - Do you agree? Or do you think pursuing a collaboration with CDS at this time, trying to get them to add more information on TeV sources as well as TeV spectra and lightcurves makes sense? |
We had a discussion on this on VERITAS, and will now build a VERITAS source catalogue at HEASARC (pre-discussion have taken place with them). This is certainly kind of orthogonal to your effort, although it will give exactly what you want: open access in a clearly defined format. The latter will be FITS, but the details have to be discussed with HEASARC. This will also give gamma-cat free and easy access to all published high-level VERITAS results. |
Dear Christoph, Your statement on Vizier and SIMBAD is misleading. SIMBAD is a collection of all sources published in refereed papers (with Vizier is a compilation of all published catalogs with access to the This beeing said, I think there are 2 aspects to the question you are It is certainly worth pursuing asking CDS to add more info on sources, The other thing is to have a dedicated "gamma" catalog, in a format that Cheers, Catherine https://www.mpi-hd.mpg.de/hfm/HESS/pages/publications/auxiliary/auxinfo_SNRG349 Le 14/10/2016 à 11:19, Christoph Deil a écrit :
|
@cboisson - I submitted the pre-conference version for ADASS an hour ago: I expect OK? @GernotMaier - It would be nice if data format and data collection efforts aren't duplicated. So if you think it's worth talking to someone from VERITAS or HEASARC working on this, please point them to https://github.com/gammapy/adass2016-gamma-cat-poster/blob/master/adass2016-gamma-cat-poster.pdf and put us in touch via email. |
Le 14/10/2016 à 11:46, Christoph Deil a écrit :
|
Agreed (and I am part of the VERITAS effort). |
I'm closing this old issue discussing the relationship of gamma-cat to CDS, SIMBAD, VIZIER . There isn't much overlap in the data collection or scope, and I think there is agreement that it's good to have gamma-cat as a separate project, trying to integrate it at CDS doesn't seem possible / useful to me. @GernotMaier - Is the separate VERITAS / HEASARC effort still alive? If yes, would it make sense to have a short call to exchange ideas / look for possible collaboration to avoid duplicated effort? There has been a lot of progress on gamma-cat in the past months, and we should really make an effort to expose the data and status at https://gamma-cat.readthedocs.io/index.html . I'll try to find time to work on this, but I'm not sure I will ... |
@GernotMaier suggested to look into the possibility to use SIMBAD or VIZIER from CDS instead of making a separate project.
E.g. some of the VERITAS data is found / available there:
http://simbad.u-strasbg.fr/simbad/sim-id?Ident=VER&NbIdent=cat&Radius=2&Radius.unit=arcmin&submit=submit+id
Most TeV data isn't available there though, and I'd be surprised if they want it all there.
It needs someone to collect, reformat and maintain it for every existing and future publication.
However, we should talk to them and at least interoperate as much as possible (e.g. on source identifiers) and document on our side what is available at CDS and how to find it.
The text was updated successfully, but these errors were encountered: