Astrophot

Latest version: v0.16.6

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

Scan your dependencies

Page 3 of 5

0.14.3

What's Changed
* use numpy variable instead of tensor in chunk_image_jacobian by ConnorStoneAstro in https://github.com/Autostronomy/AstroPhot/pull/150
* Adding continuous deployment to the project by ConnorStoneAstro in https://github.com/Autostronomy/AstroPhot/pull/152
* feat: Add gaussian quadrature integration option for initial sampling by ConnorStoneAstro in https://github.com/Autostronomy/AstroPhot/pull/154
* feat: Add minifit fitter to optimize on downsampled target by ConnorStoneAstro in https://github.com/Autostronomy/AstroPhot/pull/155

**Full Changelog**: https://github.com/Autostronomy/AstroPhot/compare/v0.14.2...v0.14.3

0.14.2

New deployment workflow, minor bug fixes:

- Bug fix for GPU on large images
- Multiple bug fixes in unit-tests on GPU
- Bug fix when loading PSF model for a model

0.14.1

Several updates and fixes. Some of the main changes are:

- More robust initialization for galaxies
- jacobian may now be computed for large images
- fix bug when loading models with PSFs
- fix some docs typos
- fix bug when setting uncertainty

0.13.4

Minor updates from tests on large fitting problems. Most `initialize` methods now account for masked pixels making them more robust. `Group_Model` objects will update the targets of their constituents if their target is updated. Edge case for LM is handled where it exits cleanly if asked to optimize a model with no free parameters.

The most visible update is that when plotting a `model_image` the models are not evaluated on the whole image, but instead only in their fitting windows. This is a better fit for the "principle of least surprise" in python. Users will expect these plots to be consistent with other parts of the code which only use the fitting windows.

0.13.3

Path update to handle some edge cases. If all parameters are locked for some branch of the DAG it is necessary for the vector functions to return empty tensors to properly propogate through other functions.

Another edge case discovered by wmwv is if the uncertainty tensor is None or has mismatched shape it can lead to errors. This is now handled correctly.

0.13.2

Bug fix where the LM fitter `update_uncertainty` function was not updating the uncertainties, now fixed. Also fixed a problem where it was possible to provide uncertainty tensors with a shape mismatch to the `value` tensor.

Thanks to wmwv for identifying and solving the issue!

Page 3 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.