Testing problem vers. 3.0

[matteocappuccio]

Hi everyone,
We are installing Pride version 3.0 on a newly purchased linux PC. The installation seems to be successful but we get the attached error. During the test, however, the kinematic positioning was successful.
We also encounter problems when trying pdp3 with our RINEX and the error remains the same

Could you help us out?

Thank you in advance for your time!

Matteo

[Dengyingda]

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 problem is directory-related.

[matteocappuccio]

Hello Dengy and thank you for your reply.
Sorry for the delay in ours.

The problem has not been solved, we tried installing the latest version on github (3.1.1) but it does not continue without any change in the ‘DataCleaning’ of the first static test.

Thanks again if you help us!

Matteo

[Dengyingda]

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 path /media/bernese/Disco3/ could potentially cause permission or path resolution issues.
Could you please try reinstalling the software in your home directory (e.g., ~/app-name on Linux/macOS)?
This would help us verify if the problem stems from directory permissions or filesystem configuration.

[matteocappuccio]

Thank you again Dengy,

We are sure it is not a Pride problem but unfortunately we cannot find the solution. The test.sh stops at the ‘DataCleaning’ stage without continuing. I attach the installation report and the lock screen.
Thank you again for your help and kindness.

Matteo

UNIBO_installationreport.txt

[Dengyingda]

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 diagnose this, could you please:

1. Terminate the current test process
2. Navigate directly to the computation directory:

• cd [Year]/[DOY]/ # e.g. 2023/150/

3. Run the LSQ module individually:

• lsq config (config file in this directory) rinex_obs (rinex file)

4. Share the complete terminal output

This will help us to find where 'lsq' stuck.