Return to ENVRI Community Home![]()
...
Data processing requests generally originate from CV Presentation Objects#experiment_experiment laboratory which validate requests by invoking an AAAI service . The CV Presentation Objects#experiment_experiment laboratory will send a process request to a coordination service , which interprets the request and starts a processing workflow by invoking the required CV Component Objects#process_process controller. Data will be retrieved from the data store and passed to the execution platform, the coordination service will request that a data transfer service to prepare a data transfer.
Data will be retrieved from the data store and passed to the execution platform, the coordination service will request that a data transfer service to prepare a data transfer. The data transfer service will then configure and deploy a CV Component Objects#data_data exporter which will handle the transfer of data between the storage and execution platforms, i.e. performing data staging. A data-flow is established between all required CV Component Objects#data_data store _ controllers and CV Component Objects#process_process controller via the CV Component Objects#data_data exporter. After the data-flow is established, processing starts. Processing can include a host of activities such as summarising, mining, charting, mapping, amongst many others. The details are left open to allow the modelling of any processing procedure. The expected output of the processing activities is a derived data product, which in turn will need to be persisted into the RIs data stores.
...
The data transfer service will then configure and deploy a data importer which will handle the transfer of data between the execution and storage platforms. A data-flow is established between process controller and data store controller via the data importer. After the data-flow is established, the data transfer starts. The persistence if data will trigger various curation activities including data storage, backup, updating of catalogues, requiring identifiers and updating records. These activities can occurs automatically or just as signals sent out to warn human users that an action is expected.
| 패널 | |||
|---|---|---|---|
| borderColor | black | ||
| borderWidth | 1 | ||
| |||
Notation of Computational Viewpoint Models#notation_cv_objects |