Content deleted Content added
Added information about SilA 2, removed "Scope of Standardization" chapter, split "External Links" into "Sources" and "External Links" |
m spelling - it's->its, typo(s) fixed: time consuming → time-consuming |
||
Line 7:
Understanding the mechanisms of life requires extensive, often repetitive, experimentation. Laboratory automation, therefore, has become instrumental to the progress of the life sciences.
Industry provides commercial laboratory devices to perform increasingly sophisticated tasks. However, combining equipment from different providers to work in concert often proves impossible. Exporting captured data from proprietary software for further analysis can be frustrating or impossible.
This situation leads to a waste of resources: Available equipment needs to be replaced for compatibility reasons, software drivers have to be purchased or developed, and data conversion is time
Such technical obstacles impede the development of higher level autonomous experimentation systems.
SiLA enables researchers to focus on their scientific questions by reducing equipment connectivity effort to a minimum. This is achieved by using proven, tested and maintained documentation and code.
Line 66:
===Technical Background===
SiLA 2 considers every entity in the modern laboratory as a service. Focus on behaviour and service oriented design structures leads to the Feature Definition Language (FDL). SiLA 2 is based on a microservice architecture. Relying on [[HTTP/2]], SiLA uses [[Protocol Buffers]] to serialize payload data. Furthermore, SiLA 2 uses the wire format provided by [[gRPC]].
===Structures===
SiLA 2 can split up into a Core and Feature level. The SiLA Core is written and maintained by the SiLA 2 Working group. SiLA Features are specific extensions that may change and evolve in any way.
SiLA's basic structure consists of a client – server communication model. The SiLA Server (≙[[web server]]) exposes all
===Features===
| |||