Solarmach

Latest version: v0.4.1

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

Scan your dependencies

Page 1 of 4

0.4.1

<!-- Release notes generated using configuration in .github/release.yml at v0.4.1 -->

What's Changed
* Fix how DataFrames are addressed in `get_sw_speed` so that the function won't fail in the future if the keys of the DataFrame change (https://github.com/jgieseler/solarmach/commit/7293b7fb46e0a2f22fb2f0b449965fed02ca5d37)
* Add Europa Clipper mission to list of supported spacecraft

**Full Changelog**: https://github.com/jgieseler/solarmach/compare/v0.4.0...v0.4.1

0.4.0

<!-- Release notes generated using configuration in .github/release.yml at v0.4.0 -->

What's Changed
* **Remove supported Python versions 3.8 & 3.9** (in alignment with latest `sunpy` versions)
* Extend supported Python versions to 3.10, 3.11, 3.12
* Use [sunkit-magex](https://pypi.org/project/sunkit-magex/) instead of [pfsspy](https://pypi.org/project/pfsspy/) for PFSS analysis (because the latter is discontinued)
* Unpin matplotlib version in requirements 57
* Remove astroquery from requirements 48

**Full Changelog**: https://github.com/jgieseler/solarmach/compare/v0.3.4...v0.4.0

0.3.4

<!-- Release notes generated using configuration in .github/release.yml at v0.3.4 -->

What's Changed
* Improve importing of `speasy` by disabling unused data providers before, which will speed up the initial automatic determination of solar wind speeds (using `get_sw_speed`)
* Improve handling of input date & time (using now `sunpy.time.parse_time` everywhere)
* Catch failing `get_horizons_coord`
* Adjust to upcoming Pandas changes
* Include real image tests
* Upgrade GitHub actions

**Full Changelog**: https://github.com/jgieseler/solarmach/compare/v0.3.3...v0.3.4

0.3.3

<!-- Release notes generated using configuration in .github/release.yml at v0.3.3 -->

What's Changed
* Bugfix: `get_sw_speed` has been fixed to work again for Solar Orbiter (due to some changed ID)
* Some internal changes in the pfsspy part

**Full Changelog**: https://github.com/jgieseler/solarmach/compare/v0.3.2...v0.3.3

0.3.2

<!-- Release notes generated using configuration in .github/release.yml at v0.3.2 -->

What's Changed
* Bugfix: PFSS extension now gives correct results when Stonyhurst coordinates are used (`coord_sys='Stonyhurst'`). Now, when calculating the PFSS solution, it is necessary to define the coordinate system that should be used. For example, `calculate_pfss_solution(gong_map=gong_map, rss=rss, coord_sys='Stonyhurst')`

**Full Changelog**: https://github.com/jgieseler/solarmach/compare/v0.3.1...v0.3.2

0.3.1

<!-- Release notes generated using configuration in .github/release.yml at v0.3.1 -->

What's Changed
* Add new option `markers` to the plot to use a single letter for the body/spacecraft marker instead of numbers (e.g., "P" for Parker Solar Probe). Note that duplicate letters can occour. This option replaces the previous plot option `numbered_markers`. For now on, use either `markers='letters'` or `markers='numbers'` (or `markers=False` for the default square symbol). See the following example:

python
from solarmach import SolarMACH
body_list = ['Venus', 'Earth', 'Mars', 'STEREO A', 'Solar Orbiter', 'PSP', 'BepiColombo']
date = '2021-6-1 12:00:00'
sm = SolarMACH(date, body_list)
sm.plot(markers='letters')

![image](https://github.com/jgieseler/solarmach/assets/39489154/25513223-0c1d-44c8-b5d9-2faa865ad8a8)

**Full Changelog**: https://github.com/jgieseler/solarmach/compare/v0.3.0...v0.3.1

Page 1 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.