Skip to content

Apply space motion jmr#465

Open
jmripic wants to merge 79 commits intodsavransky:masterfrom
jmripic:apply_space_motion_jmr
Open

Apply space motion jmr#465
jmripic wants to merge 79 commits intodsavransky:masterfrom
jmripic:apply_space_motion_jmr

Conversation

@jmripic
Copy link
Copy Markdown
Contributor

@jmripic jmripic commented Apr 10, 2026

Describe your changes

Changed starprop method to use astropy's apply_space_motion. Required packaging proper motion and radial velocity values into StarCatalog/TargetList coords and deprecating the proper motion and radial velocity attributes. Also fixed a probabilistic error that occurred during some e2e tests.

Type of change

  • Bug fix (non-breaking change which fixes an issue)

Reference any relevant issues (don't forget the #)

#313

Checklist before requesting a review

  • [.] I have verified that all unit tests pass in a clean virtual environment and added new unit tests, as needed
  • [.] I have run e2eTests and added new test scripts, as needed
  • [.] I have verified that all docstrings are properly formatted and added new documentation, as needed

MalichiMerski and others added 30 commits November 30, 2025 13:39
Remove self attributes: pmra, pmdec, and rv. Package internally to the SkyCoord object.
typo fix from numpy.zeroes to numpy.zero
Initial updates with maturation still needed for starprop function before final fix.
Initial attempt for starprop update based on SkyCoord changes.
Added a default epoch to ensure deterministic propagation and avoid hidden Astropy defaults.
Import time from astropy for proper SkyCoord function and update docstrings for relocated kinematic parameters.
apply_space_motion instead of manually computing vectors
appended [sInds] to coord_old within starprop.
sInds contains one index so it is scalar when it needs to be an array.
Attempt to force array semantics. Problem appears to originate from astropy and/or SkyCoord metadata being scalar for the case of 1.
importing astropy Skycoord
Call SkyCoord directly.
updates for transforming coordinate system to heliocentric true eclipltic
jmripic and others added 30 commits March 11, 2026 10:37
arange's final value would sometimes be less than endTime, and this
would sometimes cause interpolation to return nan.
Note that an if statement was not included (for adding dt to endTime)
to eliminate any possibility of a floating point error, given that the
values are all floats.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants