This repository has been archived by the owner on Aug 29, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 15
Core Processing Requirements
Krzysztof (Chris) Bernat edited this page Feb 23, 2017
·
10 revisions
This page lists various Cate processing requirements and applications and how they are addressed by the various Cate interfaces. See also: Reasons for CLI
| Requirement/Application | API Script [1] | API REPL [2] | CLI | GUI |
|---|---|---|---|---|
| Get help for operation or workflow | Yes, but... | Yes | Yes | Yes |
| Call operation or workflow | Yes | No | Yes | Yes |
| Parameterise operation calls | Yes | No | Yes | Yes |
| Call Cate from OS shell scripts | Yes, but... | No | Yes | Yes |
| Batch processing | Yes | Yes, but... | Yes | Yes, but... |
| Service implementation | Yes | No | Yes | No |
| Progress observation | Yes, but... [3] | Yes, but... [3] | Yes | Yes |
| Progress cancellation | Yes, but... [3] | Yes, but... [3] | Yes | Yes |
| Logging | Yes, but... [3] | Yes, but... [3] | Yes | Yes |
| [1] | Users must first write the Python script and therefore know a little Python and the Cate API (e.g. read the API reference or copy sample code). Even the simplest script uses some boilerplate: import Cate, read parameter values from the command-line, read some data file, call Cate API, write some data files. |
| [2] | Users must start the REPL (IPython, Python) interpreter first. They must still know the Cate API. Importing Cate libs may be implicit. |
| [3] | (1, 2, 3, 4, 5, 6) Behavior must be programmed. API functions must support the feature. Users must know, how to use the API correctly. |