Steffan Davies

Your suggestion solves the pathing issue. However, sbas.compute_ps() throws the following error, which is probably related to simultaneous access: # use the only selected dates for the pixels stability analysis...

The same for computing interferograms: OSError: [Errno 5] Can't synchronously read data (file read failed: time = Tue Apr 30 18:12:40 2024 , filename = '[/home/steffan/raw_sarez2017_desc/S1_20170511_ALL_F2.grd](http://localhost:8889/home/steffan/raw_sarez2017_desc/S1_20170511_ALL_F2.grd)', file descriptor = 18,...

> It seems that you have not configured your Dask cluster for parallel access to the network-shared data. Do you have any idea what options they might be? I have...

> There are many ways to begin; you could start here: https://docs.dask.org/en/stable/deploying.html Yes, I followed the dask docs for setting up the cli scheduler on A and workers on A...

> @SteffanDavies See the example of PS+SBAS processing: https://www.linkedin.com/feed/update/urn:li:activity:7089507310389121024/ I am currently testing this and in your example sbas.ps_parallel() is called before merging, however doing so will cause: `AssertionError: ERROR:...

> It should work for all the subswaths. Are you sure SBAS.ps_parallel() does not work for multiple subswaths? If I change to only 1 subswath it works fine, otherwise it...

More issues, topo_ra error and empty interferograms: Dem is fine:  topo_ra error seems dask related?  Empty intf and corr (only plot 1 but all the same): 

Dask is running, I've never had this error before.   

I reverted to PyGMTSAR pygmtsar-2023.5.3 and it is working. Something has broken in latest code.  

> The Dask issue can be related to disconnected client or maybe Dask version change (when Dask or distributed libraries upgraded and inconsistent to the running cluster). > > >...