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

Fixed Typo - GPS INT,eger L1 Pseudorange Modulus Ambiguity #59

Closed
wants to merge 2 commits into from

Conversation

ArlinJae
Copy link

pyrtcm Pull Request Template

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context and, where applicable, any RTCM documentation sources you have used. List any dependencies that are required for this change.

Fix -
In the attributes, renamed GPS INT,eger L1 Pseudorange Modulus Ambiguity to GPS Integer L1 Pseudorange Modulus Ambiguity

Testing

Please test all changes, however trivial, against the supplied pytest suite tests/test_*.py. Please describe any test cases you have amended or added to this suite to maintain >= 99% code coverage.

  • No testing required, literally fixed typo

Checklist:

  • I agree to abide by the code of conduct (see CODE_OF_CONDUCT.md).
  • My code follows the style guidelines of this project (see CONTRIBUTING.md).
  • I have performed a self-review of my own code.
  • (if appropriate) I have cited my RTCM documentation source(s).
  • I have commented my code, particularly in hard-to-understand areas.
  • I have made corresponding changes to the documentation.
  • (if appropriate) I have added test cases to the tests/test_*.py unittest suite to maintain >= 99% code coverage.
  • I have tested my code against the full tests/test_*.py unittest suite.
  • My changes generate no new warnings.
  • Any dependent changes have been merged and published in downstream modules.
  • I have signed my commits.
  • I understand and acknowledge that the code will be published under a BSD 3-Clause license.

@ArlinJae
Copy link
Author

@semuadmin huge fan of the repo btw

@ArlinJae ArlinJae closed this by deleting the head repository Jun 21, 2024
@semuadmin
Copy link
Contributor

Hi @ArlinJae,happy to merge but other priorities mean I may not get to it for another week or so. Thanks

@ArlinJae
Copy link
Author

All good - accidentally deleted the repo, didn't know that would delete the MR - will reopen in a second

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.

None yet

2 participants