SP3 clock interpolation is far from RINEX clock
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 23
- Forks
- 9
- Avg merge
- 5d 12h
- Merged PRs (30d)
- 4
Description
RINEX clock is close to what is computed by rtklib. But SP3-based clock is far from RINEX clock.
Possible reasons:
- not taking into account a particular hardware bias
- interpolation technique not adapted
- relativistic clock effect (not accounted by RINEX, accounted by SP3) <- taken into account
A extensive analysis should be done, with comparison with other tools (rtklib).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the discrepancy between the SP3-based clock and the RINEX clock, then compare both results with RTKLIB. Investigate the listed hardware bias, interpolation, and relativistic-effect possibilities. Done means identifying the cause of the mismatch and defining or implementing a correction, but no files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100