Patches processed issue

[suatcoskun]

I have no enough RAM capacity so I tried to worked with patches option. Bu at the end of the process I faced this Issue. Do you have any advice?

Best...

config.json

025-02-17 00:56:59,202 - INFO - Parameter value default
2025-02-17 00:56:59,202 - INFO - _________ _____ _______
2025-02-17 00:56:59,202 - INFO - input_path inputs/ inputs/
2025-02-17 00:56:59,202 - INFO - output_path /media/suat/demir3/isce_deneme/miaplpy/outputs <--- outputs/
2025-02-17 00:56:59,202 - INFO - num_cores 20 <--- 50
2025-02-17 00:56:59,202 - INFO - num_patches 5 <--- 1
2025-02-17 00:56:59,202 - INFO - apply_temporal_unwrapping True True
2025-02-17 00:56:59,202 - INFO - spatial_unwrapping_method puma puma
2025-02-17 00:56:59,202 - INFO - logging_level INFO INFO
2025-02-17 00:56:59,202 - INFO - logfile_path logfiles/ logfiles/
2025-02-17 00:56:59,202 - INFO -
2025-02-17 00:56:59,202 - INFO - ---------------------------------------------------------------------------------
2025-02-17 00:56:59,202 - INFO - STEP 0: PREPARATION
2025-02-17 00:56:59,203 - INFO - ---------------------------------------------------------------------------------
2025-02-17 00:56:59,203 - INFO - Parameter value default
2025-02-17 00:56:59,203 - INFO - _________ _____ _______
2025-02-17 00:56:59,203 - INFO - start_date None None
2025-02-17 00:56:59,203 - INFO - end_date None None
2025-02-17 00:56:59,203 - INFO - ifg_network_type sb sb
2025-02-17 00:56:59,203 - INFO - num_ifgs 3 3
2025-02-17 00:56:59,203 - INFO - max_tbase 24 <--- 100
2025-02-17 00:56:59,203 - INFO - filter_window_size 9 9
2025-02-17 00:56:59,203 - INFO -
2025-02-17 00:56:59,203 - INFO - ########## PREPARE PROCESSING: LOAD INPUT ##########
open slc file: slcStack.h5
2025-02-17 00:56:59,212 - INFO - Orbit direction: DESCENDING
2025-02-17 00:56:59,212 - INFO - Start date: 2022-10-01
2025-02-17 00:56:59,212 - INFO - Stop date: 2024-12-25
2025-02-17 00:56:59,213 - INFO - Number of SLC: 64
2025-02-17 00:56:59,213 - INFO - ########## DESIGN IFG NETWORK ##########
2025-02-17 00:56:59,214 - INFO - Small baseline network
2025-02-17 00:56:59,214 - INFO - write IfgNetwork to /media/suat/demir3/isce_deneme/miaplpy/outputs/ifg_network.h5
2025-02-17 00:56:59,217 - INFO - temporal baselines: [12 24 36]
2025-02-17 00:56:59,942 - INFO - ########## GENERATE STACK OF 118 INTERFEROGRAMS & ESTIMATE TEMPORAL COHERENCE ##########
2025-02-17 00:56:59,942 - INFO - Process 6 patches (3 x 2).
2025-02-17 00:56:59,955 - INFO - Prepare dataset: ifgs of <class 'numpy.complex64'> in size of (2382, 8396, 118)
2025-02-17 00:56:59,961 - INFO - Prepare dataset: temp_coh of <class 'numpy.float32'> in size of (2382, 8396)
open slc file: slcStack.h5
2025-02-17 00:58:26,425 - INFO - Patches processed: 1/6
2025-02-17 00:59:36,396 - INFO - Patches processed: 2/6
2025-02-17 01:00:36,519 - INFO - Patches processed: 3/6
2025-02-17 01:01:36,166 - INFO - Patches processed: 4/6
2025-02-17 01:02:36,682 - INFO - Patches processed: 5/6
2025-02-17 01:03:36,040 - INFO - Patches processed: 6/6
2025-02-17 01:03:36,556 - INFO - Transform coordinates from latitude and longitude (WGS84) to North and East (UTM).
Traceback (most recent call last):
File "/home/suat/miniconda3/envs/sarvey/bin/sarvey", line 8, in
sys.exit(main())
File "/home/suat/miniconda3/envs/sarvey/lib/python3.10/site-packages/sarvey/sarvey_mti.py", line 311, in main
run(config=config, args=args, logger=logger)
File "/home/suat/miniconda3/envs/sarvey/lib/python3.10/site-packages/sarvey/sarvey_mti.py", line 106, in run
proc_obj.runPreparation()
File "/home/suat/miniconda3/envs/sarvey/lib/python3.10/site-packages/sarvey/processing.py", line 188, in runPreparation
coord_utm_obj.prepare(input_path=join(self.config.general.input_path, "geometryRadar.h5"))
File "/home/suat/miniconda3/envs/sarvey/lib/python3.10/site-packages/sarvey/objects.py", line 183, in prepare
utm_crs = CRS.from_epsg(utm_crs_list[0].code)
IndexError: list index out of range

[mahmud1]

Hi @suatcoskun. The issue is not related to the patches, but to the conversion of radar coordinates to UTM, as described here in this issue. We already have a fix for this issue and will merge it into the next_release branch soon.
Cheers,
Mahmud