Open collinss-jpl opened 3 months ago
Hi @collinss-jpl This issues were resolved in the most recent patch release (DSWx-S1 v0.4.2 ).
Hi @collinss-jpl This issues were resolved in the most recent patch release (DSWx-S1 v0.4.2 ).
Hi @oberonia78, I was just able to verify the fix during acceptance testing of the 4.2 delivery, thanks for the quick turnaround!
Hi @oberonia78, I've been seeing this issue crop up again in the interface delivery for DSWx-NI. Seems like the fix for the issue was only merged to the dswx-s1-calval
branch, and not the main
branch, so it was not included with the DSWx-NI delivery.
Thanks @collinss-jpl for reporting the issue. We are planning to merge the recent changes for dswx-s1-calval
to the main branch (https://github.com/opera-adt/DSWX-SAR/pull/89). This issue will be fixed in the next delivery.
While testing the DSWx-S1 and DSWx-NI deliveries, I discovered that changing the docker working directory to
/home/dswx_user
(from the default of/home/dswx_user/scratch
) resulted in the following permission error:This is because there are two locations in the code where temporary products are written to the current working directory (
'.'
) instead of the scratch directory defined by the RunConfig:Redefining the container working directory is useful for PGE/SDS integration, so it would be nice if these temp products could get written to defined scratch directory like other temporary products.