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
Is your feature request related to a problem? Please describe.
ariaTSsetup.py is used in the NISAR Solid Earth ATBD testing with Sentinel-1 data. When it is run for large areas or stacks that span large time periods, the process can take hours to complete. When the process runs for many hours inside a Jupyter cell, there is the possibility of an instance freezing, a kernel dying, or other interruptions, after which it has to be restarted from scratch to run again for many hours. In addition, if a NISAR on-demand user has to leave the process running for a long, unspecified amount of time, this can result in instances being open for longer than necessary, which can translate into unnecessary spending on the project side.
Describe the solution you'd like
It would be extremely helpful to break up the script into multiple smaller steps, each of which can be run in a separate Jupyter cell and each of which should have a verbose mode and a separate progress bar.
for example: (I really don't know everything the script does, so this is a guess)
step 1: download DEM
step 2: crop images
step 3: stitch images
step 4: ...
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
ariaTSsetup.py is used in the NISAR Solid Earth ATBD testing with Sentinel-1 data. When it is run for large areas or stacks that span large time periods, the process can take hours to complete. When the process runs for many hours inside a Jupyter cell, there is the possibility of an instance freezing, a kernel dying, or other interruptions, after which it has to be restarted from scratch to run again for many hours. In addition, if a NISAR on-demand user has to leave the process running for a long, unspecified amount of time, this can result in instances being open for longer than necessary, which can translate into unnecessary spending on the project side.
Describe the solution you'd like
It would be extremely helpful to break up the script into multiple smaller steps, each of which can be run in a separate Jupyter cell and each of which should have a verbose mode and a separate progress bar.
for example: (I really don't know everything the script does, so this is a guess)
step 1: download DEM
step 2: crop images
step 3: stitch images
step 4: ...
The text was updated successfully, but these errors were encountered: