Skip to content
Falk Amelung edited this page Sep 26, 2019 · 5 revisions

This page lists common problems that users accounted and how they were solved:

  • DEM download problem

I met a problem:
File "/home/xiechou/rsmas_insar/minsar/dem_rsmas.py", line 98, in main raise Exception('ERROR starting dem.py subprocess') # FA 8/19: I don't think this happens, errors are is output Exception: ERROR starting dem.py subprocess

Solution: Was caused by bad Internet connections. Solved by keeping a local copy of the DEM.

  • h5py problem about rsmas_insar

Hi Falk:

I met a problem about h5py with I run process_rsmas.py. I listed the error as following:

File "/home/user/utility/anaconda3/lib/python3.7/site-packages/h5py/init.py", line 26, in from . import _errors ImportError: libhdf5.so.101: cannot open shared object file: No such file or directory

I uninstalled h5py and reinstalled h5py using conda, but the error was still there. Could you please tell me how to fix the problem?

Solution: Hi Chou, I never saw this. You may have something else in your Conda environment which causes conflicts. I see that you are installing in an area different than suggested in our setup. Falk

Hi Falk:

You are right. All my data doesn’t cover my bounding box because I took adjacent data wrongly. After modified bounding box, I met the following problem:

20190926:082246 * execute_runfiles.py /data3/WORKDIR/GuizhouSenDT164/GuizhouSenDT164.template 20190926:082246 * job_submission.py /data3/WORKDIR/GuizhouSenDT164/run_files/run_1_unpack_slc_topo_master --memory 4000 --walltime 8:00 --queuename batch --outdir /data3/WORKDIR/GuizhouSenDT164/run_files Traceback (most recent call last): File "/home/xiechou/rsmas_insar/minsar/process_rsmas.py", line 269, in main() File "/home/xiechou/rsmas_insar/minsar/process_rsmas.py", line 95, in main objInsar.run(steps=inps.runSteps) File "/home/xiechou/rsmas_insar/minsar/process_rsmas.py", line 247, in run self.run_interferogram() File "/home/xiechou/rsmas_insar/minsar/process_rsmas.py", line 209, in run_interferogram minsar.execute_runfiles.main([self.custom_template_file]) File "/home/xiechou/rsmas_insar/minsar/execute_runfiles.py", line 114, in main queue=queuename) File "/home/xiechou/rsmas_insar/minsar/job_submission.py", line 290, in submit_batch_jobs job_files = write_batch_job_files(batch_file, out_dir, memory=memory, walltime=walltime, queue=queue) File "/home/xiechou/rsmas_insar/minsar/job_submission.py", line 216, in write_batch_job_files scheduler, memory, walltime, queue) File "/home/xiechou/rsmas_insar/minsar/job_submission.py", line 185, in write_single_job_file queue) File "/home/xiechou/rsmas_insar/minsar/job_submission.py", line 149, in get_job_file_lines prefix + process_option.format(number_of_nodes, number_of_tasks), NameError: name 'number_of_nodes' is not defined

Could you please tell me how to solve it?

Best regards

Chou

  • Error: No acquisition forfills the temporal range and bbox requirement.

Hi Falk:

I started to run process_rsmas.py GuizhouSenDT164.template --step ifgrams, and met the following problem.


The overlap region among all dates (based on the preview kml files): South North East West 25.211691 27.249094 103.418205 106.218559


All dates (49) ['20180104', '20180116', '20180128', '20180209', '20180221', '20180305', '20180317', '20180329', '20180410', '20180422', '20180504', '20180516', '20180528', '20180609', '20180621', '20180703', '20180715', '20180727', '20180808', '20180820', '20180901', '20180913', '20180925', '20181007', '20181019', '20181031', '20181112', '20181124', '20181206', '20181218', '20181230', '20190111', '20190123', '20190204', '20190216', '20190228', '20190312', '20190324', '20190405', '20190429', '20190511', '20190523', '20190604', '20190616', '20190628', '20190710', '20190722', '20190803', '20190815']

dates covering the bbox (0) []


Error: No acquisition forfills the temporal range and bbox requirement. Skip creating run files ...

Actually, in GuizhouSenDT164.template,

topsStack.boundingBox = '27.12 27.87 103.7 106.0'

The bbox was covering by all the data.

**Solution: ** bounddingBox ie probably not correct