Closed abradley60 closed 9 months ago
Thank you, @abradley60 , for reporting this issue. Yes, the problem could be in the DEM coverage and/or the DEM no-data values. I noticed that you have disabled the flag check_ancillary_coverage
in your runconfig. We require that flag to be enabled in production, and we do not guarantee that the process will succeed if the flag is disabled. Also, the DEM we use in production does not have no-data values (including in ocean areas). Maybe you can try to substitute your DEM no-data values with 0 and see if the processing succeeds.
Thanks for the quick response @gshiroma. I will change the check_ancillary_coverage
to true and replace the no-data values to 0 to match your workflow. I'll report back if that solves the problem.
@gshiroma that looks to have solved the issue! I am now filling the missing glo_30 data with zero's (mainly off the Antarctic coast) and the products are processing as expected. Interesting that they would process with no-data filling provided apply_shadow_masking : false
. Thanks again for your help! Great to have tools like these available and open.
Checked for duplicates
Yes - I've already checked
Describe the bug
I am creating some backscatter products over the Antarctic region (coastal and inland). The workflow works as expected for a wide range of products I have tested. However, when I configure the workflow to apply and save the layover shadow mask, the process seems to hang indefinitely on certain bursts. This will only happen on some products.
E.g. Here are the logs for a test scene where I encountered the issue below. I let the process sit for approx. 10 hours. There was still high CPU usage so the process seemed to be ongoing.
it hung here.
What did you expect?
I ran the same workflow again with both
apply_shadow_masking : false
andsave_mask : false
set and it worked as expected:apply_shadow_masking : false
andsave_mask : false
-> SUCCESS (approx 50 mins)apply_shadow_masking : true
andsave_mask: true
-> HANGING (process still ongoing after 10 hours)If I had to guess I thought it could potentially be a DEM coverage issue? In some areas there can be a large amount of no-data in the DEM.
Here is the .yaml file I am using. Details on the scene can be found here.
Reproducible steps
Environment