Closed Ovec8hkin closed 5 years ago
I can not tell where or when it went wrong, could you share more information @Ovec8hkin ? PySAR stops when there is an error, but it could went wrong earlier already.
There are a few data sets which have the slcDir specified (slcDir=$SCRATCHDIR/AgungSenDT32/SLC
). This may not be supported anymore. Just disable or delete those,
$SCRATCHDIR/AgungSenDT32/SLC
Falk Amelung Professor Department of Marine Geosciences Rosenstiel School of Marine and Atmospheric Sciences University of Miami 4600 Rickenbacker Causeway Miami, FL 33149 USA Tel: 305 421 4949 E-mail: famelung@rsmas.miami.edumailto:famelung@rsmas.miami.edu Web: http://insar.rsmas.miami.edu InSAR data: http://insarmaps.miami.edu
On Mar 27, 2019, at 2:14 PM, Joshua Zahner notifications@github.com<mailto:notifications@github.com> wrote:
The following error shows up in the log files produced by process_rsmas when called from run_operations. This does not occur for all datasets, but it does occur consistently for the datasets for which it occurs. I don't know if this is a PySAR issue, a process_rsmas issue, or a run_operations issue.
Project name: testLombokSenAT156 create directory: /projects/scratch/insarlab/jaz101/testLombokSenAT156/PYSAR Go to work directory: /projects/scratch/insarlab/jaz101/testLombokSenAT156/PYSAR copy default template file /nethome/jaz101/test/testfalk/rsmas_insar/sources/PySAR/pysar/defaults/pysarApp_template.txt to work directory create directory: /projects/scratch/insarlab/jaz101/testLombokSenAT156/PYSAR/INPUTS copy testLombokSenAT156.template to INPUTS directory for backup. read custom template file: /nethome/jaz101/insarlab/OPERATIONS/TEMPLATES/testLombokSenAT156.template update default template based on input custom template pysar.load.processor: auto --> isce pysar.reference.lalo: auto --> -8.6456,116.5234 pysar.networkInversion.weightFunc: auto --> fim pysar.troposphericDelay.method: auto --> no pysar.save.hdfEos5: auto --> yes pysar.save.hdfEos5.update: auto --> yes read default template file: /projects/scratch/insarlab/jaz101/testLombokSenAT156/PYSAR/pysarApp_template.txt
updateMode : True
compression: None
Traceback (most recent call last):
File "/nethome/jaz101/test/testfalk/rsmas_insar/sources/PySAR/pysar/pysarApp.py", line 1021, in
____ __ __ ____
/ ) / ) / | / )
------/__/-----------------/|---/ /------ / / / \ / | / | /____(/_(//____|/____| / (_ /
A Python package for InSAR time series analysis. PySAR v1.0.0-dev, 2019-03-16
Project name: testLombokSenAT156 Go to work directory: /projects/scratch/insarlab/jaz101/testLombokSenAT156/PYSAR ['/projects/scratch/insarlab/jaz101/testLombokSenAT156/PYSAR/INPUTS/testLombokSenAT156.template'] exists and is newer than ['/nethome/jaz101/insarlab/OPERATIONS/TEMPLATES/testLombokSenAT156.template'] --> skip. read custom template file: /nethome/jaz101/insarlab/OPERATIONS/TEMPLATES/testLombokSenAT156.template update default template based on input custom template No new option value found, skip updating /projects/scratch/insarlab/jaz101/testLombokSenAT156/PYSAR/pysarApp_template.txt read default template file: /projects/scratch/insarlab/jaz101/testLombokSenAT156/PYSAR/pysarApp_template.txt
updateMode : True
compression: None
Traceback (most recent call last):
File "/nethome/jaz101/test/testfalk/rsmas_insar/sources/rsmas_isce/process_rsmas.py", line 143, in
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgeodesymiami%2Frsmas_isce%2Fissues%2F107&data=02%7C01%7Cfamelung%40rsmas.miami.edu%7C594305ba7401494a4b9a08d6b2f0da5d%7C2a144b72f23942d48c0e6f0f17c48e33%7C0%7C0%7C636893144868794305&sdata=LviLuq7iYO6LOGfzrxfZq5ycR5kf7gnro%2BUNlXs9BKs%3D&reserved=0, or mute the threadhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKpT3JXadszz9vMJNCIodGdYNXKdvWbqks5va9EzgaJpZM4cOsMw&data=02%7C01%7Cfamelung%40rsmas.miami.edu%7C594305ba7401494a4b9a08d6b2f0da5d%7C2a144b72f23942d48c0e6f0f17c48e33%7C0%7C0%7C636893144868804309&sdata=4TooLZWjfvXVKpnLrTWjSsCphS2Cv9iHFRXnF1ZwNrE%3D&reserved=0.
@falkamelung that would be the case. Do we need to handle the case where the SLC directory is specified, or no? Should I just remove the specified SLC directory, or the whole dataset?
Falk Amelung Professor Department of Marine Geosciences Rosenstiel School of Marine and Atmospheric Sciences University of Miami 4600 Rickenbacker Causeway Miami, FL 33149 USA Tel: 305 421 4949 E-mail: famelung@rsmas.miami.edumailto:famelung@rsmas.miami.edu Web: http://insar.rsmas.miami.edu InSAR data: http://insarmaps.miami.edu
On Mar 27, 2019, at 3:35 PM, Joshua Zahner notifications@github.com<mailto:notifications@github.com> wrote:
@falkamelunghttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ffalkamelung&data=02%7C01%7Cfamelung%40rsmas.miami.edu%7Ce1346385fa884c656a2008d6b2fc2d81%7C2a144b72f23942d48c0e6f0f17c48e33%7C0%7C0%7C636893193498865462&sdata=1s6TIHqcctPrPYvbCrnQ1PGL5RtQl2%2BQXEurt8btc0o%3D&reserved=0 that would be the case. Do we need to handle the case where the SLC directory is specified, or no? Should I just remove the specified SLC directory, or the whole dataset?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgeodesymiami%2Frsmas_isce%2Fissues%2F107%23issuecomment-477356857&data=02%7C01%7Cfamelung%40rsmas.miami.edu%7Ce1346385fa884c656a2008d6b2fc2d81%7C2a144b72f23942d48c0e6f0f17c48e33%7C0%7C0%7C636893193498875471&sdata=%2FWOXo1tPqAK041QgtAyfDc5OUtPwAKcp1OKot1RmhYI%3D&reserved=0, or mute the threadhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKpT3C61nqnnRAQkTHbf0YrkIpmi18_Rks5va-QzgaJpZM4cOsMw&data=02%7C01%7Cfamelung%40rsmas.miami.edu%7Ce1346385fa884c656a2008d6b2fc2d81%7C2a144b72f23942d48c0e6f0f17c48e33%7C0%7C0%7C636893193498875471&sdata=Bh6cRQKelT6eNvLCJFBsPHCEdz9oyBNa8tYVlAy7Nw4%3D&reserved=0.
Alright. I disabled them. With that, I believe run_operations
works as advertised! I will submit it for code review and go over it with @2gotgrossman later this week or this weekend. I will let you know when its merged and ready for your to test out.
The following error shows up in the log files produced by
process_rsmas
when called fromrun_operations
. This does not occur for all datasets, but it does occur consistently for the datasets for which it occurs. I don't know if this is aPySAR
issue, aprocess_rsmas
issue, or arun_operations
issue.