Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

pyroSAR appearing to look for a tmp file before it's created

See original GitHub issue

which operating system are you using?
RHEL
which environment is pyroSAR running in?
user-level installation of Python 3.9.2
which version of pyroSAR are you using?
clone of the GitHub repository
which function of pyroSAR did you call with which parameters?
geocode
if applicable, which version of SNAP or GAMMA are you using in pyroSAR? SNAP 8.0, Sentinel-1 Toolbox 8.0.4
the full error message [Errno 2] No such file or directory: ‘[…]/T30VUJ/2021/03/29/pyrosar/S1B__IW___D_20210329T063721_NR_Orb_Cal_TF_TC_dB/tmp/S1B_IW_GRDH_1SDV_20210329T063721_20210329T063746_026226_03213E_AA5A_tmp3.dim’

geocode call: geocode(scene, outdir='%s' % (path2pyrosar), t_srs=crs_epsg, tr=resolution, scaling='dB', polarizations='all', geocoding_type='Range-Doppler', removeS1BorderNoise=True, removeS1BorderNoiseMethod='pyroSAR', removeS1ThermalNoise=True, terrainFlattening=terrainFlattening, externalDEMFile=dem_file, externalDEMNoDataValue=dem_ndv, externalDEMApplyEGM=True, speckleFilter=speckleFilter, refarea='gamma0', shapefile=granule_shp, alignToStandardGrid = True, standardGridOriginX = origin[0], standardGridOriginY = origin[1])

Issue Analytics

State:
Created 2 years ago
Comments:6 (5 by maintainers)

Top GitHub Comments

2reactions

maawoocommented, Aug 26, 2021

Now my process fails during Apply-Orbit-File even though POEORB files were downloaded manually at some point beforehand. Wasn’t the problem regarding the qc.sentinel1.eo.esa.int API resolved as stated in #131? Or am I missing something?

Resolved after updating SNAP 👍🏻

1reaction

jthetzelcommented, Oct 4, 2021

I also encountered this error and had trouble figuring out how to update SNAP in a Dockerfile. In case others are in a similar situation, adding the following as a RUN command after installing SNAP resolved the error.

snap --nosplash --nogui --modules --update-all 2>&1 | while read -r line; do     
    echo "$line";     
    [ "$line" = "updates=0" ] && sleep 2 && pkill -TERM -f "snap/jre/bin/java"; 
done; 
exit 0

The pkill workaround is needed because the SNAP update-all command hangs after updating ( https://senbox.atlassian.net/wiki/spaces/SNAP/pages/30539785/Update+SNAP+from+the+command+line ). The exit 0 is needed because the workaround was returning a non-zero status causing the Docker build to terminate.