Mocpy

Latest version: v0.13.1

Safety actively analyzes 628969 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 4

0.11.0

Added

* Add `MOC.from_ring`
* Option `include_indirect_neighbours` to `split` and `split_count`

Changed

* Extend the `moc.fill` and `moc.border` to directly accept an astropy wcs object. This solves the issue <https://github.com/cds-astro/mocpy/issues/69>
* Addresses the plotting artefacts when plotting big HEALPix cells. Cells of depth < 3 are subdivided to the depth 3 before being plotted
* Set the default `time_order` from 29 to 61, i.e. to `max_order` in `stmoc.from_spatial_coverages` (29 was the `max_order` in the previous MOC V2.0 version).

Improvement

* More robust FITS UNIQ deserialization (ignoring 0 values)

0.10.0

Changed

* Rename `TimeMOC` logical operations taking a deltaT constraint adding the sufix `_with_timeresolution`
* WARNING logical `TimeMOC` logical operations are now at the deepest depth (no time resolution parameter)

Added

* Deprecate `from_fits`, ... methods
* Add `MOC.spli_count`, `MOC.split`, `MOC.from_multiordermap_fits_file`
* Add support for u16 and u32 fits MOC and TMOC in 'load'

Bug correction

* Replace empty moc shape (1, 0) by (0, 2)
* Fix `tmoc.max_time`
* Fix doc (due to an evolution of sphinx)

0.9.0

Changed

* Add compatibility with MOC2.0: Time depth in now in `[0, 61]` instead of `[0, 29]`
* Add `from_time_ranges_in_microsec_since_jd_origin` in `temporal_coverage.rs`
* Time operations now precise to the microseconds, see:
* `utils.times_to_microseconds`
* `utils.microseconds_to_times`
* Add several options to `moc.from_valued_healpix_cells`
* Add `load` and `save` methods for serialization/deserialization in pure Rust (ensuring
MOC2.0 compatibility).
* Improve performance and some operations (like intersection and union)
* Improve `to_uniq` performances (x5 according to a bench in pure Rust)
* Improve `add_neighbours` and `remove_neighbours` performances (now in pure Rust)

Internal Python changes

* `complement()`: remove from AbstractMoc / IntervalSet, and add it in Moc and TimeMoc (because complement now depends on the qty)

Internal changes

* Remove the `moc` crate from MOCPy and publish it as a standalone [here](https://github.com/cds-astro/cds-moc-rust)
(with a lot of added stuff)
* Add FITS serialization/deserialization on the Rust code.
* Add ASCII and JSON serialization/deserialization on the Rust code.
* Move `rand` from dependencies to dev-dependenciies
* Generalize the code to support various quantities with different dimensions (HEALPix indices, Time, ...)
* create `MocableQty` and `MocQty` implemented by `Hpx` and `Time`
* Remove depth/qty dependent operations from `Ranges` (depth/complement/degrade), create a trait for generic operations
* Add `MocRange(s)` since we introduced `MocQty` for depth dependent operations, and introduce both: `HpxRange(s)` and `TimeRange(s)`
* Add `MocRanges2D` for depth dependent operations
* Rename `NestedXX` in `HpxXX` to possibly support Ring indices (the code should be the same as far as the NSIDE is a power of 2)
* ...

0.8.5

Changed

* change the CI: replace travis and appveyor by github actions
* replace setuptools rust by maturin
* update dependencies

0.8.2

Changed

* remove ',' separator when deserializing MOC from ascii (this follows the MOC 1.1 standard [http://ivoa.net/documents/MOC/20191007/REC-MOC-1.1-20191007.pdf](http://ivoa.net/documents/MOC/20191007/REC-MOC-1.1-20191007.pdf))

0.8.1

Added

* from_valued_healpix_cells

Changed

* API Breaking change! from_image -> from_fits_image(hdulist, max_norder)
* WCS -> World2ScreenMPL. It's a context manager class

Page 2 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.