Hans Vanrompay
Hans Vanrompay
I want to bump this issue, since I stumbled over a similar unclarity on how UDF currently tackle working with the input data (automatic conversion if needed)
as part of APEX we will be porting this UPD over in the next 2 weeks. So I will immediately take a look at where the error comes from.
currently being worked on in: https://github.com/ESA-APEx/apex_algorithms/issues/34
Already managed to get a clean UDF running on CDSE backend. Wuld need to be validated. @clausmichele what is the standard spatiotemporal extent you used for validation
working UDF and UDP can be found in the following PR: Changes might still be made https://github.com/ESA-APEx/apex_algorithms/pull/44
@soxofaan I have worked on the comments above and also included 2 additional unit tests to test the behavior
@soxofaan The issues seems to be resolved
We now have 3 types of job splitters which we are looking into @VictorVerhaert, @jdries would you propose here to have it 'non-optimized' and fixed splitting per 20km tiles? Or...
@jdries perhaps good if we indeed create a couple of sub-tasks for this one. It would be good to have a clear sight on how we want users to 'ínteract'...
We need to validate whether solution would also be applicable for WEED inference runs