-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failing benchmark "max_ndvi_composite" #52
Comments
from logs of r-24110514497740198b2a6f53bb71cd0a:
|
found the issue: benchmark scenario uses apex_algorithms/benchmark_scenarios/max_ndvi_composite.json Lines 11 to 17 in 43bf814
but the UDP expects a apex_algorithms/openeo_udp/examples/max_ndvi_composite/max_ndvi_composite.json Lines 383 to 385 in 43bf814
It was quite confusing to figure this out, beause the apex_algorithms/openeo_udp/examples/max_ndvi_composite/generate.py Lines 17 to 19 in 43bf814
I guess it would have failed with a much cleaner error if that parameter wasn't optional @jdries you seemed to make it optional intentionally with 3e14e13#diff-0465fb74b5eed7572e8e0e73471b227c6ed5a472441522fc64c1a026878d809dL17 is there a particular reason for that? |
Yes, intentional, I actually even want to use: See: |
@jdries I guess you commented on the bbox/spatial extent rename, which I fully understand. My question was about making the parameter optional with a default value |
it's optional because a user may want to leave it empty, and specify some sort of spatial filtering later on, when using the udp in a larger pipeline, this is the same reasoning as for load_collection. |
ok makes sense, but the problem is then that that |
last run at the time: https://github.com/ESA-APEx/apex_algorithms/actions/runs/11684670042/job/32536394554
benchmark failure due to job failure:
The text was updated successfully, but these errors were encountered: