Closed fmigneault closed 2 years ago
For the workflow let's start with something basic : subsetting -> climate index For subsetting we will start using WPS1 flyingpigeon subset_bbox and when available, try to use the CWT one.
App package should be created from the following endpoints:
(output for reference: https://colibri.crim.ca:443/wpsoutputs/flyingpigeon/81bb1fa6-4fef-11e9-9535-0242ac12000c/result_2019-03-26T17:49:45Z__4zz8XW.json)
Climate index request sample : https://finch.crim.ca/wps?service=WPS&request=execute&version=1.0.0&identifier=ice_days&storeExecuteResponse=true&DataInputs=tasmax=files@xlink:href=https://github.com/Ouranosinc/xclim/raw/master/tests/testdata/NRCANdaily/nrcan_canada_daily_tasmax_1990.nc;freq=MS
@davidcaron once your CWT implementation ready, you should be able to contribute to this functional tests issue and add, as discussed, a subsetter using the ESGF backend.
@dbyrns
using the above referenced fix + commit 077d9a8 + following wps_providers.yml
config, WPS-2 processes are deployed successfully with their CWL WPS1Requirement
on startup.
providers:
- url: https://colibri.crim.ca/twitcher/ows/proxy/flyingpigeon/wps?service=WPS&request=describeprocess&version=1.0.0&identifier=subset_bbox
name: colibri-flyingpieon
- url: https://finch.crim.ca/wps?service=WPS&request=describeprocess&version=1.0.0&identifier=ice_days
name: finch
Just be careful with the naming scheme... what we deploy in Weaver are processes not providers. I would prefer to see a wps_processes.yml config file looking like this to avoid confusion :
processes:
- url: https://colibri.crim.ca/twitcher/ows/proxy/flyingpigeon/wps?service=WPS&request=describeprocess&version=1.0.0&identifier=subset_bbox
name: colibri-flyingpieon-subset_bbox
- url: https://finch.crim.ca/wps?service=WPS&request=describeprocess&version=1.0.0&identifier=ice_days
name: finch-ice_days
relates to #3
DockerRequirement
href
instead ofProcessDescription
(seeDockerRequirement
note)owsContext
withinProcessDescription -> Process
executionUnit
(combined withdeploymentProfileName
) (seeDockerRequirement
note)WPS1Requirement
(added in #372) (must provideprocess
in requirement)href
instead ofProcessDescription
owsContext
withinProcessDescription -> Process
executionUnit
(combined withdeploymentProfileName
)DescribeProcess
endpointhref
instead ofProcessDescription
owsContext
withinProcessDescription -> Process
executionUnit
(combined withdeploymentProfileName
)GetCapabilities
endpoint (must includeidentifier=...
to deriveDescribeProcess
)href
instead ofProcessDescription
owsContext
withinProcessDescription -> Process
executionUnit
(combined withdeploymentProfileName
)GET Process
endpointhref
instead ofProcessDescription
owsContext
withinProcessDescription -> Process
executionUnit
(combined withdeploymentProfileName
)Workflow
using deployed sub-processesDockerRequirement
noteImplementation missing from below tests but feature is tested across many other tests since it is the most common use case. Should implement just to make sure it is always evaluated for consistency. https://github.com/crim-ca/weaver/blob/107fec5e19f20b77061b9405a764da911d2db8a2/tests/wps_restapi/test_processes.py#L627-L641