Asteca

Latest version: v0.5.9

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

Scan your dependencies

Page 8 of 8

0.1.2

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

- Likelihood method now supports `Dolphin
(2002) <http://adsabs.harvard.edu/abs/2002MNRAS.332...91D>`__
*Poisson likelihood ratio* function.
- Closed `120 <https://github.com/asteca/asteca/issues/120>`__,
`101 <https://github.com/asteca/asteca/issues/101>`__,
`129 <https://github.com/asteca/asteca/issues/129>`__,
`124 <https://github.com/asteca/asteca/issues/124>`__,
`102 <https://github.com/asteca/asteca/issues/102>`__.
- Minor `position
fix <https://github.com/asteca/asteca/commit/00538bda879009bae0a4e7565b124c8939c75d0f>`__
for synthetic cluster text box in output plot.
- Brute force algorithm now returns `correct
errors <https://github.com/asteca/asteca/commit/afe30cbdff561a90986a638c55a4b7247fd0bc53>`__.
- Some fixes for when unique values in the input parameter ranges are
used
(`[1] <https://github.com/asteca/asteca/commit/7cc383d799f2af5c1f1f8a6dcfc80e639461f02d>`__,
`[2] <https://github.com/asteca/asteca/commit/c6505025d4c3b6147a2913fad648dc18c125376b>`__).
- Replaced deprecated `compiler
package <https://github.com/asteca/asteca/commit/f9e8c5edba5f5ca8cc33ec1afb4d137f7167e8df>`__
used to flatten list.


**Caveats**

- Still not sure why *tolstoy* likelihood is biased towards high masses
:confused:

0.1.1

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

*More stable release.*

- Closed `113 <https://github.com/asteca/asteca/issues/113>`__,
`116 <https://github.com/asteca/asteca/issues/116>`__.
- Minor
`change <https://github.com/asteca/asteca/commit/3cffb4faa0c1dc6956aae2217c73afb4f392e53d>`__
to error function.
- Closed *Known issues* from previous version.


**Caveats**

- Same as previous version.

0.1.0

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

*First semi-stable buggy release*

- Closed `72 <https://github.com/asteca/asteca/issues/72>`__,
`99 <https://github.com/asteca/asteca/issues/99>`__,
`37 <https://github.com/asteca/asteca/issues/37>`__.
- Changed the way the IMF was
`sampled <https://github.com/Gabriel-p/asteca/commit/0671e74c52fbecde6bcbb1afb1c2624875156e57>`__,
now it should be faster and more precise.
- Some speed improvements (moved things around mainly).
- Binary fraction is now a free parameter.

**Known issues**

- **Serious bug**: if the DA is set to run but the *Best fit method*
isn’t, the final plot can’t be produced since the ``syn_cl_err``
function isn’t used
(`fixed <https://github.com/Gabriel-p/asteca/commit/3e806bd0af5d7fcd7c8f2940716df880f4c1b67d>`__
in next release).
- Forgotten ``print`` prints out mass values every time the E/I
operator is applied
(`fixed <https://github.com/Gabriel-p/asteca/commit/8b313ef60fddccc41fd6fb7b9746f75f3e867d39>`__
in next release).
- If the number of points (``n_left``) in the radius finding function
is smaller than 4, a very small radius is likely to be selected.
`Fixed <https://github.com/Gabriel-p/asteca/commit/c247fd7fa4cca4d6bb341263434a4a43a4778efd>`__
in next release.


**Caveats**

- The total initial mass can be set as a free parameter but the
likelihood function will select always synthetic clusters of high
mass. Thus it is advised to leave this parameter fixed to 1000 solar
masses.
- The binary fraction found is not stored in the output data file.
- Some density map plots for mass and binary fraction are missing.

Page 8 of 8

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.