Hv pv detection

[HansVRP]

added EURAC UDP.

There are some points which are still open for debate:

• Do we want to set the max cloud cover as a parameter as well and/or the kernel size of the postprocessing filter?

• Currently I get the model and dependencies within the UDF, I saw that for world cereal job options are given. Is there a preferred approach?

[soxofaan]

Currently I get the model and dependencies within the UDF, I saw that for world cereal job options are given. Is there a preferred approach?

at the moment there is no standard way to attach job options to UDPs, e.g see this discussion:

• UDP: define minimally required additional job options Open-EO/openeo-api#545

so for the moment, I think doing it in the UDF is the only way

[HansVRP]

In the word cereal benchmark they are passed as:

"job_options": {
"driver-memory": "4g",
"executor-memory": "1500m",
"python-memory": "5g",
"udf-dependency-archives": ["https://artifactory.vgt.vito.be/artifactory/auxdata-public/openeo/onnx_dependencies_1.16.3.zip#onnx_deps"]
}
}

hence my confusion.

Is this then different?

[soxofaan]

some notes

[soxofaan]

In the word cereal benchmark they are passed as: ...

ah ok I see what you mean now.

you can indeed define job options in the benchmark scenario

there are indeed two options at the moment

• handle model/deps "manually" from the UDF code. Adds more boilerplate to the UDF, but makes usage easier (less job_option worries)
• work with job options. less UDF boilerplate, but as a user you're forced to always set job options. And there is unfortunately no standard way jet to attach "recommended" job options to a UDP

I'm not sure what is best at the moment