-
Notifications
You must be signed in to change notification settings - Fork 110
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
Error on example rt_ppp_example.yaml #119
Comments
Can you create and provide us with a backtrace using gdb on the core file that was produced by that crash (core dump) please. |
Thanks for the comment. |
Hi Jürgen, I think the issue has been identified and addressed in the Best regards, |
Hej Sebastien! Thanks for the update, I switched to the develop-weekly branch. Unfortunately the sigma values are now higher than before. Now it is more than 500 meters, it was ~5 meters. Kind regards, Jürgen |
Hi Jürgen, Yes, I just realized this too. I am looking at it now. Sebastien |
Hej Sebastien! I switched back to branch release-v3.1.0. The sigma values are now in sub-meter range, but it takes several hours to get there...
Just wanted to notice you about that, it might help finding the issue.. in Postprocessing the PPP-works really well! Kind regards, Jürgen |
Hi Jürgen, we managed to find the issue in the The config file as provided needs to have the following changes:
receiver_options:
global:
[...]
clock_codes: [AUTO, AUTO]
zero_dcb_codes: [AUTO, AUTO] doing so, I have a sigma less than 1m after a few minutes and about 5cm after 15 to 20 minutes (first epoch is 11:29) Best regards |
Describe the bug
I tried to run the example rt_ppp_example.yaml but it fails. I changed the input sources (other CORS and BCEP).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should start processing stations.
Configuration files
pea_output.txt
Operating environment (please complete the following information):
These may be found in the 'Compilation details' section of the pea's output.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: