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

refactor!: rename nadir_pointing profile to local_orbital_frame #484

Conversation

vishwa2710
Copy link
Contributor

@vishwa2710 vishwa2710 commented Jan 5, 2025

Summary by CodeRabbit

Release Notes

  • Refactor

    • Renamed NadirPointing method to LocalOrbitalFramePointing across multiple components of the OpenSpaceToolkit Astrodynamics library.
    • Updated method signatures and documentation to reflect the new method name while maintaining existing functionality.
  • Tests

    • Updated test suites to utilize the new LocalOrbitalFramePointing method.
    • Ensured consistent test coverage with the renamed method and adjusted expected outcomes accordingly.

@vishwa2710 vishwa2710 requested a review from apaletta3 January 5, 2025 03:06
@vishwa2710 vishwa2710 self-assigned this Jan 5, 2025
Copy link
Contributor

coderabbitai bot commented Jan 5, 2025

Warning

Rate limit exceeded

@vishwa2710 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 30 minutes and 10 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between d4e3e62 and 16b6021.

⛔ Files ignored due to path filters (3)
  • test/OpenSpaceToolkit/Astrodynamics/Flight/Profile/LocalOrbitalFramePointing/VVLH/Satellite_1 t_UTC x_GCRF v_GCRF q_B_GCRF w_B_GCRF_in_GCRF.csv is excluded by !**/*.csv
  • test/OpenSpaceToolkit/Astrodynamics/Flight/Profile/LocalOrbitalFramePointing/VVLH/Satellite_2 t_UTC x_GCRF v_GCRF q_B_GCRF w_B_GCRF_in_GCRF.csv is excluded by !**/*.csv
  • test/OpenSpaceToolkit/Astrodynamics/Flight/Profile/LocalOrbitalFramePointing/VVLH/Satellite_3 t_UTC x_GCRF v_GCRF q_B_GCRF w_B_GCRF_in_GCRF.csv is excluded by !**/*.csv
📒 Files selected for processing (10)
  • bindings/python/src/OpenSpaceToolkitAstrodynamicsPy/Flight/Profile.cpp (1 hunks)
  • bindings/python/src/OpenSpaceToolkitAstrodynamicsPy/Flight/Profile/Model/Transform.cpp (2 hunks)
  • bindings/python/test/flight/test_profile.py (1 hunks)
  • bindings/python/test/test_viewer.py (1 hunks)
  • include/OpenSpaceToolkit/Astrodynamics/Flight/Profile.hpp (1 hunks)
  • include/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Model/Transform.hpp (1 hunks)
  • src/OpenSpaceToolkit/Astrodynamics/Flight/Profile.cpp (1 hunks)
  • src/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Model/Transform.cpp (1 hunks)
  • test/OpenSpaceToolkit/Astrodynamics/Flight/Profile.test.cpp (9 hunks)
  • test/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Transform.test.cpp (3 hunks)

Walkthrough

The pull request introduces a comprehensive renaming of the NadirPointing method to LocalOrbitalFramePointing across multiple files in the OpenSpaceToolkit Astrodynamics library. This change affects both the C++ implementation and Python bindings, updating method signatures, test cases, and references in various source and test files. The modifications aim to provide a more accurate description of the method's functionality, focusing on local orbital frame transformations rather than a specific nadir pointing orientation.

Changes

File Path Change Summary
bindings/python/src/OpenSpaceToolkitAstrodynamicsPy/Flight/Profile.cpp Renamed nadir_pointing method to local_orbital_frame_pointing
bindings/python/src/OpenSpaceToolkitAstrodynamicsPy/Flight/Profile/Model/Transform.cpp Renamed nadir_pointing method to local_orbital_frame_pointing
bindings/python/test/flight/test_profile.py Renamed test method test_nadir_pointing to test_local_orbital_frame
bindings/python/test/test_viewer.py Updated profile fixture to use local_orbital_frame_pointing
include/OpenSpaceToolkit/Astrodynamics/Flight/Profile.hpp Renamed static method NadirPointing to LocalOrbitalFramePointing
include/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Model/Transform.hpp Renamed static method NadirPointing to LocalOrbitalFramePointing
src/OpenSpaceToolkit/Astrodynamics/Flight/Profile.cpp Replaced NadirPointing method with LocalOrbitalFramePointing
src/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Model/Transform.cpp Renamed NadirPointing method to LocalOrbitalFramePointing
test/OpenSpaceToolkit/Astrodynamics/Flight/Profile.test.cpp Updated method calls from NadirPointing to LocalOrbitalFramePointing
test/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Transform.test.cpp Renamed test case and method call to LocalOrbitalFramePointing

Possibly related issues

Poem

🚀 A Rabbit's Orbital Rename 🛰️
From Nadir's point to Local's frame,
Our code now sings a clearer name!
No more confusion, sharp and bright,
We've transformed our orbital might!
Hop, hop, hooray for clarity's reign! 🐰


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (7)
bindings/python/src/OpenSpaceToolkitAstrodynamicsPy/Flight/Profile/Model/Transform.cpp (1)

130-131: Update docstring references to reflect 'local orbital frame' instead of 'nadir pointing'.

The new method name is local_orbital_frame, but the docstring still describes "nadir pointing." Consider updating it to match the new concept:

 R"doc(
-    Create a transform for nadir pointing.
+    Create a transform for a local orbital frame.
 )doc"
src/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Model/Transform.cpp (1)

167-167: Consider clarifying the reasoning and usage of the local orbital frame.

The rename from NadirPointing to LocalOrbitalFrame makes the intent clearer, but it may be beneficial to provide in-code comments or docstrings explaining how the frames are derived and how this differs from a strict nadir orientation.

test/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Transform.test.cpp (2)

104-104: Avoid shadowing variable names.

Here, transform_ is declared in the parent scope and shadowed inside this function’s scope. Consider using a different local variable name to improve clarity, e.g. localTransform.

-    EXPECT_NO_THROW(Transform transform_(DynamicProvider(dynamicProviderGenerator), Frame::GCRF()));
+    EXPECT_NO_THROW(Transform localTransform(DynamicProvider(dynamicProviderGenerator), Frame::GCRF()));

212-215: Confirm correct initialization of LocalOrbitalFrame in tests.

The test successfully checks LocalOrbitalFrame creation. If additional orbital frame types are supported, consider adding a parameterized test case for each type to strengthen coverage.

bindings/python/src/OpenSpaceToolkitAstrodynamicsPy/Flight/Profile.cpp (1)

324-325: Update docstring to reflect LocalOrbitalFrame naming.

The docstring still mentions “nadir pointing.” Please rename it to reflect the local orbital frame context.

     "local_orbital_frame",
     &Profile::LocalOrbitalFrame,
-    R"doc(
-        Create a nadir pointing profile.
+    R"doc(
+        Create a local orbital frame profile.
         ...
     )doc",
src/OpenSpaceToolkit/Astrodynamics/Flight/Profile.cpp (1)

219-223: Consider validating the Orbit parameter before returning a Profile.
If anOrbit is undefined at runtime, TransformModel::LocalOrbitalFrame may raise an exception or produce an invalid Profile. A basic check here, similar to other constructors in this file, would enhance reliability.

test/OpenSpaceToolkit/Astrodynamics/Flight/Profile.test.cpp (1)

413-413: Confirm coverage of eccentricities & inclinations.
Although this test uses a circular (0.0 eccentricity), low-inclination orbit, consider adding more diverse scenarios to ensure LocalOrbitalFrame handles varied orbital parameters reliably.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d1c4ed4 and 7020642.

📒 Files selected for processing (10)
  • bindings/python/src/OpenSpaceToolkitAstrodynamicsPy/Flight/Profile.cpp (1 hunks)
  • bindings/python/src/OpenSpaceToolkitAstrodynamicsPy/Flight/Profile/Model/Transform.cpp (1 hunks)
  • bindings/python/test/flight/test_profile.py (1 hunks)
  • bindings/python/test/test_viewer.py (1 hunks)
  • include/OpenSpaceToolkit/Astrodynamics/Flight/Profile.hpp (1 hunks)
  • include/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Model/Transform.hpp (1 hunks)
  • src/OpenSpaceToolkit/Astrodynamics/Flight/Profile.cpp (1 hunks)
  • src/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Model/Transform.cpp (1 hunks)
  • test/OpenSpaceToolkit/Astrodynamics/Flight/Profile.test.cpp (8 hunks)
  • test/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Transform.test.cpp (3 hunks)
🔇 Additional comments (12)
include/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Model/Transform.hpp (1)

79-79: Name change aligns with the PR's objective.

The rename from NadirPointing to LocalOrbitalFrame improves semantic clarity. Ensure that the documentation (comments and user guides) is updated to reflect the new naming convention everywhere in the codebase.

bindings/python/test/test_viewer.py (1)

41-41: Local orbital frame usage is correctly updated.

The fixture now aligns with the new naming scheme. This looks good. For extra robustness, consider adding tests for additional Orbit.FrameType variants to ensure broader coverage of local orbital frame usage.

bindings/python/test/flight/test_profile.py (1)

195-199: Ensure method renaming is fully reflected in docstrings and references.

The test method now appropriately references local_orbital_frame instead of nadir_pointing. However, please ensure that any related docstrings and references throughout the file and project are fully updated to avoid confusion.

test/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Transform.test.cpp (1)

79-79: Confirm consistent usage of LocalOrbitalFrame.

Renaming the transform to LocalOrbitalFrame is consistent with the broader refactoring. Verify that references to NadirPointing are fully removed across the project to prevent confusion.

include/OpenSpaceToolkit/Astrodynamics/Flight/Profile.hpp (1)

295-295: Confirm the rename aligns with codebase references.

Renaming NadirPointing to LocalOrbitalFrame reflects the PR objective. Ensure all references, including documentation and call sites, are updated.

✅ Verification successful

Let me search for any implementation or usage of this method to ensure we catch all references.


Let me check the test file specifically for NadirPointing references.


Based on the search results, I can see that:

  1. The test file still contains references to "NadirPointing" in test names and scenario paths, but these appear to be test data files and not actual implementation code.

  2. The implementation has been updated to use "LocalOrbitalFrame" consistently in the actual code.

  3. The test file shows that the functionality previously tested under "NadirPointing" is now being tested under "LocalOrbitalFrame" with the same test cases and validation data.

Let me verify if there are any other implementation files that need to be checked.


Based on the comprehensive search results, I can now provide a final response:

The rename from NadirPointing to LocalOrbitalFrame has been properly implemented in the codebase

The only remaining references to "NadirPointing" are in:

  1. Test data files and paths under test/OpenSpaceToolkit/Astrodynamics/Flight/Profile/NadirPointing/
  2. A single test case name TEST_F(OpenSpaceToolkit_Astrodynamics_Flight_Profile, NadirPointing_VVLH)

These references are in test artifacts and don't affect the actual implementation. The core functionality has been properly renamed to LocalOrbitalFrame in:

  • Method declarations and definitions
  • Documentation
  • Python bindings
  • All implementation files

The test data can remain as-is since it's historical validation data, and the test name could be updated in a future cleanup but doesn't impact functionality.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Searches for stale references to 'NadirPointing' in the codebase.
rg "NadirPointing" -A 5

Length of output: 4671


Script:

#!/bin/bash
# Search for implementation and usage of LocalOrbitalFrame
rg "LocalOrbitalFrame" -A 5

# Search for test files that might need updates
fd "Profile.test" --exec cat {}

Length of output: 90434


Script:

#!/bin/bash
# Search for implementation and test files related to Profile
fd "Profile\.(hpp|cpp|test\.cpp)$" --exec cat {}

Length of output: 70653


Script:

#!/bin/bash
# Search for implementation files
fd "Profile\.(cpp|hpp)$" --type f --exec cat {}

Length of output: 43609

test/OpenSpaceToolkit/Astrodynamics/Flight/Profile.test.cpp (7)

106-106: Great update to use the renamed method.
Switching from NadirPointing to LocalOrbitalFrame looks correct. The orbit is defined at this point, so this usage should be valid.


423-423: Kudos for updating reference data path.
Ensuring that the path now matches the new method name LocalOrbitalFrame is consistent with the rename.


523-523: Reiterating coverage for inclination changes.
This test method already showcases an inclined orbit (45°). This helps confirm that LocalOrbitalFrame is tested with non-zero inclination.


533-533: Keeping reference data updated is crucial.
This line properly updates the expected CSV reference dataset. Good job in aligning test artifacts with the rename.


633-633: Confirm coverage for elliptical orbits.
This test uses non-zero eccentricity (0.05), verifying the new method with an elliptical orbit scenario, which is beneficial.


643-643: Updated reference data path for elliptical orbit.
The CSV file path now reflects the rename, ensuring consistency in test artifacts.


991-991: Nice consistency check with VNC frame compare.
Comparing LocalOrbitalFrame vs. a known VNC orientation ensures correctness. These lines are particularly insightful to validate alignment.

Copy link
Contributor

@lucas-bremond lucas-bremond left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the docstrings should be updated accordingly?

Also, we could make the PR non-breaking keeping "NadirPointing" with a warning being printed on use?

@vishwa2710
Copy link
Contributor Author

I think the docstrings should be updated accordingly?

Also, we could make the PR non-breaking keeping "NadirPointing" with a warning being printed on use?

Yeah we could provide a warning in this MR and then deprecate it in an upcoming patch. That's best. Will do!

Copy link
Contributor

@apaletta3 apaletta3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved pending requested changes

@vishwa2710
Copy link
Contributor Author

I think the docstrings should be updated accordingly?
Also, we could make the PR non-breaking keeping "NadirPointing" with a warning being printed on use?

Yeah we could provide a warning in this MR and then deprecate it in an upcoming patch. That's best. Will do!

Actually, upon further thought, since there are other breaking changes in this upcoming release, I would like to just club this together to simplify propagating the changes across downstream dependencies.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
bindings/python/src/OpenSpaceToolkitAstrodynamicsPy/Flight/Profile/Model/Transform.cpp (1)

130-140: LGTM! Consider enhancing the documentation.

The renaming from nadir_pointing to local_orbital_frame_pointing better reflects the functionality.

Consider enhancing the documentation by:

  1. Adding examples of available orbital frame types
  2. Explaining the differences between frame types
  3. Adding a code example showing typical usage
             R"doc(
                 Create a profile aligned with the provided local orbital frame type.

                 Args:
                     orbit (Orbit): The orbit of the satellite.
                     orbital_frame_type (OrbitalFrameType): The type of the orbital frame.
+                        Available types:
+                        - LVLH (Local Vertical Local Horizontal)
+                        - QSW (Quasi-Satellite Wing)
+                        - TNW (Tangential Normal Wing)
+                        For details on frame differences, see: <link_to_documentation>
+
+                    Example:
+                        >>> profile = Transform.local_orbital_frame_pointing(
+                        ...     orbit=satellite_orbit,
+                        ...     orbital_frame_type=OrbitalFrameType.LVLH
+                        ... )

                 Returns:
                     Transform: The transform for the local orbital frame pointing.
             )doc",
bindings/python/src/OpenSpaceToolkitAstrodynamicsPy/Flight/Profile.cpp (1)

324-334: LGTM! Consider enhancing the documentation.

The renaming is consistent with the changes in other files and maintains API coherence.

Consider enhancing the documentation by adding a usage example:

             R"doc(
                 Create a profile aligned with the provided local orbital frame type.

                 Args:
                     orbit (Orbit): The orbit.
                     orbital_frame_type (OrbitalFrameType): The type of the orbital frame.
+
+                Example:
+                    >>> # Create a profile using LVLH frame
+                    >>> profile = Profile.local_orbital_frame_pointing(
+                    ...     orbit=satellite_orbit,
+                    ...     orbital_frame_type=OrbitalFrameType.LVLH
+                    ... )
+                    >>> # Get the state at a specific instant
+                    >>> state = profile.get_state_at(instant)

                 Returns:
                     Profile: The profile aligned with the local orbital frame.
             )doc",
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7020642 and d4e3e62.

📒 Files selected for processing (9)
  • bindings/python/src/OpenSpaceToolkitAstrodynamicsPy/Flight/Profile.cpp (1 hunks)
  • bindings/python/src/OpenSpaceToolkitAstrodynamicsPy/Flight/Profile/Model/Transform.cpp (2 hunks)
  • bindings/python/test/test_viewer.py (1 hunks)
  • include/OpenSpaceToolkit/Astrodynamics/Flight/Profile.hpp (1 hunks)
  • include/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Model/Transform.hpp (1 hunks)
  • src/OpenSpaceToolkit/Astrodynamics/Flight/Profile.cpp (1 hunks)
  • src/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Model/Transform.cpp (1 hunks)
  • test/OpenSpaceToolkit/Astrodynamics/Flight/Profile.test.cpp (9 hunks)
  • test/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Transform.test.cpp (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (5)
  • bindings/python/test/test_viewer.py
  • include/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Model/Transform.hpp
  • include/OpenSpaceToolkit/Astrodynamics/Flight/Profile.hpp
  • src/OpenSpaceToolkit/Astrodynamics/Flight/Profile.cpp
  • test/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Transform.test.cpp
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Test / Run C++ Unit Tests
🔇 Additional comments (6)
src/OpenSpaceToolkit/Astrodynamics/Flight/Profile/Model/Transform.cpp (1)

Line range hint 167-193: LGTM! Implementation is robust and consistent.

The implementation correctly handles error cases and maintains proper functionality while being renamed to better reflect its purpose.

test/OpenSpaceToolkit/Astrodynamics/Flight/Profile.test.cpp (5)

106-106: LGTM! Setup correctly updated to use LocalOrbitalFramePointing.

The initialization of profile_ has been properly updated to use the new naming while maintaining the same functionality.


385-385: LGTM! Test case name updated to reflect new terminology.

The test case has been appropriately renamed to LocalOrbitalFramePointing_VVLH, which better describes the functionality being tested.


Line range hint 413-425: LGTM! Reference data paths updated consistently.

The reference data file paths have been updated to reflect the new naming scheme while maintaining the same directory structure and naming convention.

Also applies to: 524-536, 635-647


994-994: LGTM! Test comparison updated to use LocalOrbitalFramePointing.

The expected profile creation has been properly updated to use the new naming while maintaining the same functionality.


Line range hint 1-1200: Verify complete removal of old terminology.

Let's verify that all instances of the old terminology have been replaced.

✅ Verification successful

All instances of NadirPointing have been successfully replaced

The codebase has been thoroughly checked and no instances of the old terminology remain. The new term LocalOrbitalFramePointing is consistently used across source files, headers, tests, and bindings.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any remaining instances of "NadirPointing" in the codebase
# that might have been missed during the rename.

echo "Searching for any remaining instances of 'NadirPointing'..."
rg --type cpp "NadirPointing" || true

echo "Verifying all instances have been replaced with 'LocalOrbitalFramePointing'..."
rg --type cpp "LocalOrbitalFramePointing"

Length of output: 3209

@vishwa2710 vishwa2710 force-pushed the 480-refactor-rename-the-profilenadirpointing-to-profilelocalorbitalframe branch from d4e3e62 to 63ce283 Compare January 6, 2025 17:39
Copy link

codecov bot commented Jan 6, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.21%. Comparing base (da2b98f) to head (16b6021).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #484   +/-   ##
=======================================
  Coverage   91.21%   91.21%           
=======================================
  Files          86       86           
  Lines        8720     8720           
=======================================
  Hits         7954     7954           
  Misses        766      766           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@vishwa2710 vishwa2710 merged commit ef11d30 into main Jan 6, 2025
15 checks passed
@vishwa2710 vishwa2710 deleted the 480-refactor-rename-the-profilenadirpointing-to-profilelocalorbitalframe branch January 6, 2025 19:08
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.

[refactor] rename the Profile::NadirPointing to Profile::LocalOrbitalFrame
3 participants