Issue with missing Seconds of Week in IGS R03 sp3 orbits#1
Open
demiangomez wants to merge 2 commits intolahayef:masterfrom
Open
Issue with missing Seconds of Week in IGS R03 sp3 orbits#1demiangomez wants to merge 2 commits intolahayef:masterfrom
demiangomez wants to merge 2 commits intolahayef:masterfrom
Conversation
The seconds of the week field in the second line of the IGSR03 combined repro3 SP3 orbits Columns 9-23 Seconds of Week e.g. 518400.00000000 are all declared as 0.00000000 (at least in all the files we have checked so far). This makes software such as GPSPACE not work, since variable SECOW is read from the header and used in subsequent computations. Here is one example from a random day: #dP2010 1 2 0 0 0.00000000 288 ORBIT IGSR3 HLM IGS ## 1564 0.00000000 300.00000000 55198 0.0000000000000 while the repro2 orbits show #cP2010 1 2 0 0 0.00000000 96 ORBIT IGb08 HLM IGS ## 1564 518400.00000000 900.00000000 55198 0.0000000000000 I have modified GPSPACE to check if SECOW == 0 and, if true, recompute it using the date of the ephemeris file. Note that some assumptions were made, such as that the first epoch in the sp3 file is 0h 0m 0s. This should provide a temporary solution until the SP3 IGS R03 files are fixed.
|
thanks for this update @demiangomez ! |
Commit changes from GPSPACE master
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The seconds of the week field in the second line of the IGSR03 combined repro3 SP3 orbits
Columns 9-23 Seconds of Week e.g. 518400.00000000
are all declared as 0.00000000 (at least in all the files we have checked so far). This makes GPSPACE to fail to process, since variable SECOW is read from the header and used in subsequent computations.
I have modified GPSPACE to check if SECOW == 0 and, if true, recompute it using the date of the ephemeris file. Note that some assumptions were made, such as that the first epoch in the sp3 file is 0h 0m 0s. This should provide a temporary solution until the SP3 IGS R03 files are fixed.