Forums » GAMMA Processing » SAR Data Preprocessing »
ERROR: calloc_1d: number of elements <= 0: 0
Added by Tapas Dey about 3 years ago
Hi Gamma users,
I am getting an weird error (ERROR: calloc_1d: number of elements <= 0: 0) while I am trying to deramp single burst S1A SLCs using run_all.pl dates 'ScanSAR_deramp_2nd.py $1_rslc_tab $1 20180531_rslc_tab 10 2 1' command. I am getting the error while SLC_mosaic_S1_TOPS is executed. Is it due to single burst or any other reason behind this? Can you please help me to fix this error. Thank you.
cmd: /usr/local/GAMMA_SOFTWARE-20210701/ISP/bin/SLC_mosaic_S1_TOPS 20180119_rslc_tab.deramp 20180119.rslc.deramp 20180119.rslc.deramp.par 10 2 1 20180531_rslc_tab ERROR: calloc_1d: number of elements <= 0: 0 *** Calculate SLC mosaic of Sentinel-1 TOPS burst SLC data *** *** Copyright 2020, Gamma Remote Sensing v4.5 16-Oct-2020 clw/awi/cm *** OPENMP: number of physical processors: 30 OPENMP: default max. number of threads (program specific): 8 OPENMP: current max. number of available threads: 30 OPENMP: number of program threads: 8 SLC_tab: 20180119_rslc_tab.deramp output SLC mosaic: 20180119.rslc.deramp file number: 4 range looks used to determine burst data window: 10 azimuth looks used to determine burst data window: 2 output SLC mosaic image: 20180119.rslc.deramp output SLC mosaic parameter file: 20180119.rslc.deramp.par NOTE: calculating burst window parameters from burst parameters reference scene SLC_tab: 20180531_rslc_tab number of input SLC images: 1 number of reference scene SLC images: 1 S1 TOPS SLC file: 20180119.rslc.deramp SLC parameter file: 20180119.rslc.deramp.par S1 TOPS burst parameter file: 20180119.rslc.deramp.tops.par WARNING: subroutine rd_str, keyword not found: title WARNING: subroutine rd_str, keyword not found: sensor WARNING: subroutine rd_str, keyword not found: date WARNING: subroutine rd_dbl, keyword not found: start_time WARNING: subroutine rd_dbl, keyword not found: center_time WARNING: subroutine rd_dbl, keyword not found: end_time WARNING: subroutine rd_int, keyword not found: line_header_size WARNING: subroutine rd_int, keyword not found: range_samples WARNING: subroutine rd_int, keyword not found: azimuth_lines WARNING: subroutine rd_int, keyword not found: range_looks WARNING: subroutine rd_int, keyword not found: azimuth_looks WARNING: subroutine rd_str, keyword not found: image_format WARNING: image_format parameter of SLC parameter file set to default: SCOMPLEX WARNING: subroutine rd_dbl, keyword not found: range_scale_factor WARNING: missing range pixel spacing scale factor is set to 1.0 WARNING: subroutine rd_dbl, keyword not found: azimuth_scale_factor WARNING: missing azimuth pixel spacing scale factor is set to 1.0 WARNING: subroutine rd_dbl, keyword not found: center_latitude WARNING: subroutine rd_dbl, keyword not found: center_longitude WARNING: subroutine rd_dbl, keyword not found: heading WARNING: subroutine rd_dbl, keyword not found: range_pixel_spacing WARNING: subroutine rd_dbl, keyword not found: azimuth_pixel_spacing WARNING: subroutine rd_dbl, keyword not found: near_range_slc WARNING: subroutine rd_dbl, keyword not found: center_range_slc WARNING: subroutine rd_dbl, keyword not found: far_range_slc WARNING: subroutine rd_dbl, keyword not found: incidence_angle WARNING: subroutine rd_str, keyword not found: azimuth_deskew WARNING: subroutine rd_dbl, keyword not found: azimuth_angle WARNING: subroutine rd_dbl, keyword not found: radar_frequency WARNING: subroutine rd_dbl, keyword not found: adc_sampling_rate WARNING: subroutine rd_dbl, keyword not found: chirp_bandwidth WARNING: subroutine rd_dbl, keyword not found: prf WARNING: subroutine rd_dbl, keyword not found: azimuth_proc_bandwidth WARNING: subroutine rd_vec, keyword not found: doppler_polynomial WARNING: subroutine rd_vec, keyword not found: doppler_poly_dot WARNING: subroutine rd_vec, keyword not found: doppler_poly_ddot WARNING: subroutine rd_dbl, keyword not found: receiver_gain WARNING: subroutine rd_dbl, keyword not found: calibration_gain WARNING: subroutine rd_dbl, keyword not found: sar_to_earth_center WARNING: subroutine rd_dbl, keyword not found: earth_radius_below_sensor WARNING: subroutine rd_dbl, keyword not found: earth_semi_major_axis WARNING: subroutine rd_dbl, keyword not found: earth_semi_minor_axis WARNING: subroutine rd_int, keyword not found: number_of_state_vectors WARNING: subroutine rd_str, keyword not found: image_geometry WARNING: missing image_geometry parameter in parameter file set to: GROUND_RANGE WARNING: subroutine rd_dbl, keyword not found: azimuth_line_time WARNING: missing azimuth line time calculated from start time, end time, and number of lines: -0.000000e+00 WARNING: subroutine rd_vec, keyword not found: first_slant_range_polynomial WARNING: subroutine rd_vec, keyword not found: center_slant_range_polynomial WARNING: subroutine rd_vec, keyword not found: last_slant_range_polynomial r0 (m): 0.000 r2 (m): 0.000 nr: 0 rpix (m): 0.000000 t0 (s): 0.000000 t2 (s): 0.000000 nlines: 0 time_per_line (s): -0.000000e+00 SLC mosaic date year: 0 month: 00 day: 00 SLC mosaic when not resampled to reference SLC range samples: -2147483647 lines: -2147483647 reference S1 TOPS burst parameter file: 20180531.rslc.tops.par r0 (m): 845507.816 r2 (m): 903970.503 nr: 25097 rpix (m): 2.329562 t0 (s): 78408.009136 t2 (s): 78411.096582 nlines: 1503 time_per_line (s): 2.055556e-03 reference SLC mosaic range samples: 25097 lines: 1503 SLC input data format: FCOMPLEX bytes/sample: 8
Replies (4)
ERROR: calloc_1d: number of elements <= 0: 0 - Added by Charles Werner about 3 years ago
Hello,
What you think is an SLC parameter file is not that, the program is looking for
various keywords in the SLC parameter file that should be present.
Please run the script on just one file to test, rather than a stack with run_all.pl
Mosaicking a single burst should not be an issue.
From the command that was executed:
SLC_mosaic_S1_TOPS 20180119_rslc_tab.deramp 20180119.rslc.deramp 20180119.rslc.deramp.par 10 2 1 20180531_rslc_tab
I would look at the files in the tab file
20180119_rslc_tab.deramp
Does this file must have 3 columns: burst SLC, burst SLC parameter file, burst
SLC tab file?
Do each of these files contain the correct data?
There can be up to 3 lines in the tab one line for each of the swaths.
ERROR: calloc_1d: number of elements <= 0: 0 - Added by Charles Werner about 3 years ago
Hello,
What you think is an SLC parameter file is not that, the program is looking for
various keywords in the SLC parameter file that should be present.
Please run the script on just one file to test, rather than a stack with run_all.pl
Mosaicking a single burst should not be an issue.
From the command that was executed:
SLC_mosaic_S1_TOPS 20180119_rslc_tab.deramp 20180119.rslc.deramp 20180119.rslc.deramp.par 10 2 1 20180531_rslc_tab
I would look at the files in the tab file
20180119_rslc_tab.deramp
Does this file must have 3 columns: burst SLC, burst SLC parameter file, burst
SLC tab file?
Do each of these files contain the correct data?
There can be up to 3 lines in the tab one line for each of the swaths.
RE: ERROR: calloc_1d: number of elements <= 0: 0 - Added by Tapas Dey about 3 years ago
Dear Charles,
Thanks for your response.
As you suggested, I ran ScanSAR_deramp_2nd.py for one slave data (20180119) with cleaning flag 0 (not deleted) and checked that both 20180119.rslc.deramp and 20180119.rslc.deramp.par are of zero size. The error log is attached.
Most probably, 20180119.rslc.deramp and 20180119.rslc.deramp.par are overwritten in SLC_mosaic_S1_TOPS step as inputs file names in SLC_tab and output derampred SLC and deramped SLC_par filenames are same. The names should not be the same, I guess. The master and slave rslc_tab files are attached for your reference. Please help me to solve this issue.
Regards,
Tapas
| deramp_error_log (8.06 KB) deramp_error_log | |||
| 20180119_rslc_tab (55 Bytes) 20180119_rslc_tab | slave_rslc_tab | ||
| 20180531_rslc_tab (55 Bytes) 20180531_rslc_tab | master_rslc_tab |
RE: ERROR: calloc_1d: number of elements <= 0: 0 - Added by Charles Werner about 3 years ago
Hello,
Why not try using different names and see if it works for you...
Charles