Yingda Deng

The program is currently designed to handle a maximum of 108 days of data at once. This is not a bug in the software, but rather a design choice. If...

Yes, you should write a loop to process the GNSS data day by day. For example: ``` for doy in {001..365}; do pdp3 -s 2024/${doy} 00:00:00 -e 2024/${doy} 23:59:59 -m...

Yes, our software includes a small utility called `pbopos `that can help solve your problem. It's recommended that you take some time to learn how to use it.

> Dear PRIDE team, > > I have been processing my GNSS observations using PRIDE in static mode, and I now have POS solutions stored in individual daily folders. I’ve...

Sorry, in my last comment, I say that "pbopos tool can merge all .pos files into a single .pbo file.", this sentence should be "pbopos tool can merge all pos_...

Hello Jorge Jara, The pbopos tool uses the **average coordinates** from the input all _pos__ file as the reference coordinates if you do not explicitly define the [x_ref y_ref z_ref]...

The application might encounter issues when run outside of your home directory. Could you please try testing it again from your user home directory? This will help determine if the...

Thank you for sharing the details. While the test script (test.sh) runs successfully on my local machine, I notice the error might be related to your installation path. The current...

Hi Matteo, Thank you for testing in the home directory. While the workflow progresses through the DataCleaning stage unsuccessfully, it appears to halt before initiating the LSQ module. To help...

Hello, Yes, this issue exists. You can solve it by adding the -l option when running the program, e.g.: `pdp3 -l ...` The problem is caused by poor observation quality,...