-
Notifications
You must be signed in to change notification settings - Fork 88
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
How to do multi-day sessions? #4
Comments
The new version is coming soon. It will support such function. |
Hello, the new version V1.14 is now supporting multi-station and multi-day processing. For the detailed usage, please refer to the manual. |
Thank you. Rover files >24h are correctly recognised (t_start, t_end). However the processing uses only data of the first day instead of all days - the DOY setting in 'Processing' obviously overrides start and end dates. I did not find a way to select multiple DOY for processing. Can you please advise? |
The software can automatically read the file of the next day. To enable that, you need to name your observation file in the format of IGS short file name format. For example, abmf1230.21o, abmf1240.21o. The sp3 and clock file name should also in the format of IGS short file name. For example, igs21730.sp3, igs21731.sp3. |
Thanks for the quick response. Do I understand this correctly: I have to split my single multi-day observation file into several distinct files of one day each, and appropriately name them? How can I do this automatically? EDIT: with your most recent upload of about 4h ago - exe + 2x dll - the version is now 1.14 as expected. |
If you have a single multi-day obs file, then you can just use that file and don't need to split it. |
My PPP observation files typically span multiple days. I have downloaded the clk and sp3 files for all of the days in question. Processing however seems only to use the clk and sp3 files belonging to the day selected in Positioning-Setting-Year/DOY. How can multi-day observations be processed using all data?
The text was updated successfully, but these errors were encountered: