You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 15, 2025. It is now read-only.
**Problem**: When running the ``process`` step, many corrections are reported as ``Skipped: interferograms already corrected``, but I want to try different processing parameters!
13
-
14
-
::
15
-
16
-
>> pyrate correct -f input_parameters.conf
17
-
16:43:16 main 97 24732 INFO 0/0 Verbosity set to INFO.
18
-
16:43:16 shared 1294 24732 INFO 0/0 Running process serially
19
-
16:43:17 process 86 24732 INFO 0/0 Found 13 unique epochs in the 17 interferogram network
20
-
16:43:17 process 134 24732 INFO 0/0 Searching for best reference pixel location
21
-
16:43:18 process 155 24732 INFO 0/0 Selected reference pixel coordinate: (38, 58)
22
-
16:43:18 process 170 24732 INFO 0/0 Calculating orbital correction
23
-
16:43:18 shared 1255 24732 INFO 0/0 Skipped: interferograms already corrected
24
-
16:43:18 process 198 24732 INFO 0/0 Calculating reference phase
25
-
16:43:19 shared 1255 24732 INFO 0/0 Skipped: interferograms already corrected
26
-
16:43:19 process 105 24732 INFO 0/0 Calculating minimum spanning tree matrix
27
-
16:43:19 process 342 24732 INFO 0/0 Calculating the temporal variance-covariance matrix
28
-
16:43:20 process 391 24732 INFO 0/0 Calculating time series using SVD method
29
-
16:43:20 timeseries 152 24732 INFO 0/0 Calculating timeseries in serial
30
-
16:43:21 process 323 24732 INFO 0/0 Calculating rate map from stacking
31
-
16:43:21 process 326 24732 INFO 0/0 Stacking of tile 0
32
-
16:43:21 stack 64 24732 INFO 0/0 Calculating stack rate in serial
33
-
16:43:21 process 314 24732 INFO 0/0 PyRate workflow completed
34
-
35
-
**Reason**: `PyRate` updates the phase values in the input interferogram geotiff files as corrections are applied during the ``process`` step. Metadata is then added to the geotiff header to indicate the correction has been applied. This metadata is then checked upon subsequent runs to see if the correction should be applied.
36
-
37
-
**Solution**: Start again from ``prepifg`` step, creating new cropped/multi-looked interferograms that have not been corrected.
38
-
39
-
.. note::
40
-
41
-
We plan to change this workflow behaviour in a future `PyRate` release, recognising that
42
-
it would be convenient to be able to quickly test the impact of parameter changes.
43
-
44
-
45
10
ValueError: too many values to unpack (expected 2)
**Problem**: During ``prepifg`` step, the following error is encountered:
@@ -104,12 +69,12 @@ Stack Rate map appears to be blank/empty
104
69
105
70
**Reason**: The ``maxsig`` parameter is too low, resulting in stack rate values being replaced by NaNs. ``maxsig`` is a threshold for masking stack rate pixels according to the corresponding stack error estimate saved in ``out/tmpdir/stack_error_*.npy``.
106
71
107
-
**Solution**: Increase ``maxsig``, then re-run ``process`` and ``merge`` steps. Maximum permittable value for ``maxsig`` is 1000 mm.
72
+
**Solution**: Increase ``maxsig``, then re-run the ``merge`` step. Maximum permittable value for ``maxsig`` is 1000 mm.
108
73
109
74
110
75
Failure of APS spatial low pass filter
111
76
---------------------------------------
112
-
**Problem**: Atmospheric corrections during “process“ fails due to the interpolated grid used for correction being empty:
77
+
**Problem**: Atmospheric corrections during ``correct`` step fails due to the interpolated grid used for correction being empty:
In general, users are advised to input a network of small-baseline interferograms
156
121
that has at least 2 interferometric connections per SAR image epoch. Furthermore,
157
122
make sure that ``ts_pthr``, ``pthr`` and ``tlpfpthr`` are smaller than the number
158
-
of image epochs. To check that ``process`` worked correctly, users can check that
159
-
the ``tsincr_*.npy`` and ``tscuml*.npy`` arrays in the ``/<outdir>/tmpdir`` contain numeric values and not NaNs.
123
+
of image epochs. To check that the spatio-temporal filters worked correctly, users can check that
124
+
the numpy arrays saved at ``/<outdir>/aps_error/*aps_error.npy`` contain numeric values and not NaNs.
160
125
161
126
162
127
Out of memory errors
@@ -167,12 +132,12 @@ Out of memory errors
167
132
168
133
joblib.externals.loky.process_executor.TerminatedWorkerError: A worker process managed by the executor was unexpectedly terminated. This could be caused by a segmentation fault while calling the function or by an excessive memory usage causing the Operating System to kill the worker. The exit codes of the workers are {EXIT(1), EXIT(1), EXIT(1)}
169
134
170
-
**Solution**: Increase the amount of memory available. On HPC systems this can be done by increasing the value provided to the ``mem`` argument when submitting a PBS job, e.g.:
171
-
172
-
::
135
+
**Solution**: Increase the amount of memory available. On HPC systems this can be done by increasing the value provided to the ``mem`` argument when submitting a PBS job, e.g.::
173
136
174
137
mem=32Gb
175
138
139
+
If no more memory can be called upon, users can try running the job in serial, or reducing the size of the interferograms by increasing the multi-looking factors applied during ``prepifg`` (parameters ``ifglksx`` and ``ifglksy``).
140
+
176
141
Incorrect modules loaded on Gadi
177
142
----------------------------------
178
143
**Problem**: `PyRate` requires certain versions of Python, GDAL and Open MPI to be loaded on Gadi and other HPC systems. While sourcing the `PyRate/scripts/nci_load_modules.sh` script will load the correct modules, you may need to unload previously unloaded modules.
0 commit comments