Is there any kind of feedback for processing when there's a lot of data?

[PeterGrace]

So I'm running a ppp job attempting to process approximately 7 hours of 1-second resolution rinex data from a mosaic-x5 gnss receiver. It's been running now for hours at 100% cpu usage (on a single core in my ryzen 7800x3d system) which leads me to believe things are happening, but, there's no console output that indicates anything's going on (see output below.) Is this thing hung or does it just take a ridiculous amount of time to process 1-second-resolution data? It has been in this state for at least 17 hours at this point.

Also, the output says "max 16 threads" but I'm running in a docker container per the README. I'm not sure if I need to pass extra arguments to docker to tell it to use as much cpu as it desires.

Thanks in advance for any insights!

================
Logging at trace level2
Threading with max 16 eigen threads
Threading with max 16 omp threads




Loading ATX file ./products/igs20.atx
Loading SP3 file ./products/IGS2R03FIN_20191990000_01D_05M_ORB.SP3
Loading ERP file ./products/finals.data.iau2000.txt
Loading CLK file ./products/IGS2R03FIN_20191990000_01D_30S_CLK.CLK
Loading BSX file ./products/IGS2R03FIN_20191990000_01D_01D_OSB.BIA
Loading IGRF file ./products/tables/igrf13coeffs.txt
Loading SNX file ./products/igs_satellite_metadata.snx
Loading SNX file ./products/tables/sat_yaw_bias_rate.snx
Loading SNX file ./products/tables/qzss_yaw_modes.snx
Loading SNX file ./products/tables/bds_yaw_modes.snx
Loading SNX file ./products/IGS1R03SNX_20191950000_07D_07D_CRD.SNX
Loading GPT file ./products/tables/gpt_25.grd
Loading Ocean Pole Tide file ./products/tables/opoleloadcoefcmcor.txt
Loading planetary ephemeris file ./products/tables/DE436.1950.2050
Initialising station SEPT
Warning: No otl parameters found for SEPT in ./products/tables/OLOAD_GO.BLQ
Warning: No OCEAN BLQ for SEPT
Warning: No ATMOSPHERIC BLQ for SEPT


Starting to process epochs...

Starting epoch #1

[seballgeyer]

Hello,

It seems the PPP job is hanging after "Starting epoch 1" without any progress. Given that the log shows "max 16 threads" but only one core is active, and considering the product files are from 2019, there might be a mismatch between the observation data and the product files. This could lead to the process stalling or being unable to find the necessary data.

To troubleshoot:

• Verify Input Files: Ensure the RINEX observation file is correctly specified and accessible.
• Check Product Files: Confirm that the product files match the timeframe of the observation data.
• Provide Config File: Sharing the configuration file can help in identifying any misconfigurations or missing parameters.

By addressing these areas, we can better understand the cause of the delay and work towards a solution.