Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AMPERE boundary update #148

Merged
merged 5 commits into from
Mar 18, 2025
Merged

AMPERE boundary update #148

merged 5 commits into from
Mar 18, 2025

Conversation

aburrell
Copy link
Owner

@aburrell aburrell commented Mar 17, 2025

Description

Added AMPERE boundaries from 2022-2024 inclusive. Also updated the citation to these boundaries.

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. Please also list any relevant details for
your test configuration

import ocbpy
# Load the ampere data
ocb = ocbpy.OCBoundary(instrument='AMPERE', hemisphere=-1)
print(ocb)

Yields:

OCBoundary file: ~/Git/ocbpy/ocbpy/boundaries/amp_south_radii.ocb
Source instrument: AMPERE
Boundary reference latitude: -74.0 degrees

3646800 records from 2010-01-01 00:00:00 to 2024-10-31 23:58:00

YYYY-MM-DD HH:MM:SS Phi_Centre R_Centre R
-----------------------------------------------------------------------------
2010-01-01 00:00:00 296.57 2.24 10.00
2010-01-01 00:02:00 296.57 2.24 10.00
2024-10-31 23:56:00 90.00 0.00 0.00
2024-10-31 23:58:00 90.00 0.00 0.00

Uses scaling function(s):
ocbpy.ocb_correction.elliptical(**{})

Test Configuration

  • Operating system: OS X Ventura
  • Version number: Python 3.10
  • Any details about your local setup that are relevant: develop branch of pysat

Checklist:

  • Make sure you are merging into the develop (not main) branch
  • My commits are formatted appropriately (following the SciPy/NumPy style)
  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • Add a note to Changelog.rst, summarising the changes
  • Add yourself to AUTHORS.rst and .zenodo.json

Update the AMPERE boundaries to include data through 2024.
Fix the name of the pyproject-parser package.
Update the citations for Steve's boundaries.
Updated the sample package citation.
Added a summary of changes to the changelog in a new release section.
@aburrell aburrell added this to the v0.6.0 milestone Mar 17, 2025
@coveralls
Copy link

Coverage Status

coverage: 99.752%. remained the same
when pulling 5f8e31d on ampere_v3_update
into 695d81a on develop.

@aburrell aburrell merged commit f487fd9 into develop Mar 18, 2025
115 of 116 checks passed
@aburrell aburrell deleted the ampere_v3_update branch March 18, 2025 13:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants