astropy / astroquery

Functions and classes to access online data resources. Maintainers: @keflavich and @bsipocz and @ceb8
http://astroquery.readthedocs.org/en/latest/
BSD 3-Clause "New" or "Revised" License
695 stars 396 forks source link

LIGO/VIRGO/GW module? #1260

Open bsipocz opened 5 years ago

bsipocz commented 5 years ago

I'm not sure whether it would make any sense to provide access to it here, but it seems that they are making the data public via https://www.gw-openscience.org/

@duncanmmacleod what do you think?

duncanmmacleod commented 5 years ago

@bsipocz, yes, there is an increasing quantity of data being made available on gw-openscience.org, but mainly in the format of 'raw' data files. I don't have much experience with astroquery, but what could be made available fairly easily is a query interface to the 'event database'.

There is a JSON API to gw-openscience.org that allow for querying simple information about the published events, so I could throw something together if you can point me at the docs for what the output of an astroquery query should look like.

(apologies for the delay, travelling.)

duncanmmacleod commented 5 years ago

Ok, after a long delay, I'm ready to think about this properly. There exists a python API to the Gravitational-wave Open Science Center (GWOSC) data releases, gwosc, so I would wrap that into an astroquery module. Is it kosher to add (optional) dependencies to astroquery? (that package is itself pure python and only depends on six).

I will have a go at following the template and see what I can come up with.

keflavich commented 5 years ago

Generally, we like to avoid additional dependencies, but we can allow some module-specific runtime dependencies. They should be imported at the class or method level, though, not at the module level, so they don't become global dependencies of astroquery.

bsipocz commented 5 years ago

Thank you @duncanmmacleod, this sounds great. As @keflavich said we prefer the dependencies the other way around (that packages depend on astroquery for their data access), but starting off the way you've suggested is also good for now.