OGC Algorithm Execution Case Studies

[marjo-luc]

Epic to keep track of the OGC algorithms we have successfully been able to register and execute on the MAAP DPS.

• NASA sardem-sarsen
• ESA sardem-sarsen
• OPERA watermask
• GEDI Subset

[marjo-luc]

Issues/questions uncovered through this effort:

• If updating an existing process to change an input parameter name, that update will not be respected. Even when the update request completes successfully, the job execution will ask for the older input parameter name instead of the new one. Do we have to create a new version of the process to support a change like this?
• Does the version specified in the CWL as s:version need to refer to a branch or tag? Can you have different algorithms registered from the same branch?

[sujen1412]

If updating an existing process to change an input parameter name, that update will not be respected. Even when the update request completes successfully, the job execution will ask for the older input parameter name instead of the new one. Do we have to create a new version of the process to support a change like this?

It looks like there are two places where an older input can come from. One is from the process database in maap api and other is hysds-io. HySDS IO gets overwritten on every registration. So it looks like the process database should also just completely overwrite the process in the database so as to not have any stale metadata/parameters. What do you think @grallewellyn

[sujen1412]

Does the version specified in the CWL as s:version need to refer to a branch or tag? Can you have different algorithms registered from the same branch?

I believe you can have multiple algorithms registered for the same version as long as they have different labels or different users registering them. The same user cannot register the exact same CWL as two different algorithms.

Is that what you were asking ?

[marjo-luc]

Thanks, @sujen1412 . Yes -- the same user case. I'll confirm same version, but different label works as expected.

[grallewellyn]

The API is not storing the inputs: https://github.com/MAAP-Project/maap-api-nasa/blob/release/5.0.0/api/models/process.py
We use HySDS to validate the inputs: https://github.com/MAAP-Project/maap-api-nasa/blob/release/5.0.0/api/utils/hysds_util.py#L565

[sujen1412]

Ohh yes, I forgot we use hysds for that now.
I'll have to run a test to see where it's picking up the stale inputs from.