Releases: alercebroker/alerce_client
Releases · alercebroker/alerce_client
1.3.0
What's Changed
- Maintenance by @ignacioreyes in #41
- Exposing Forced Photometries by @AlxEnashi in #46
Full Changelog: v1.2.0...1.3.0
Release 1.2.0
Added the ability to query the HTTP API with a postgres query.
Detail
- Use new HTTP API to access the database by @ASHuenchuleo in #25
- Continous Integration workflows by @ASHuenchuleo in #28
- Version commits are now tagged properly. by @ASHuenchuleo in #29
Minor requirements change
To avoid package dependency error, the requirements for dev and normal use are split.
Release 1.0.0
Major changes to the ALeRCE Database and ALeRCE ZTF Pipeline.
Added new documentation structure as tutorials.
- To query ZTF data now the parameters can be passed as named parameters.
- Objects can now be queried as a list of object ids (oids).
Release 0.2.4
Added deprecation warnings
API client refactoring
New Documentation
The client documentation is now public here
Major Changes in client
- Now every table returned by the methods are by default
astropy.table.Table
following the VO standard, also there is a retrocompatibility to previous versions usingformat="pandas"
to get apandas.DataFrame
orpandas.Series
- There are simple tests to validate changes in the client.
Whats new?
- Added
get_stamps()
method toAlerceAPI()
. This method can be used to download the stamps for an alert directly to python.