... | ... | @@ -8,5 +8,12 @@ In case of offering multiple hardware transformations, each manufacturer specifi |
|
|
|
|
|
The proposition in Lima2 is to let the HW provide a description of the sequence of image transformations and to expose that to the user. The same kind of description is expected to be provided by the processing pipeline, coupling both HW and SW chains will allow transform any coordinate between any stage, from the detector sensor to the final image provided to the user.
|
|
|
|
|
|
|
|
|
# High level user configuration
|
|
|
|
|
|
Lima2 will provide a single call to set **all** the parameters configuring the detector, the data acquisition and the processing. In the camera configuration parameters there will eventually be the image HW image transformations (binning, flip, RoI), with a well defined order provided by the hardware (which could be implemented through a read-only entry in the parameter tree). The same explicit configuration of the processing pipeline will be provided in the global configuration tree.
|
|
|
|
|
|
Helper classes in the client side can implement the Lima1 `HardAndSoft` concept, by querying first the camera for the possible HW image transformation and then inserting, if necessary, the SW tasks the processing chain in order to fulfill the user request.
|
|
|
|
|
|
|
|
|
# Layout vs HW reconstruction tasks |
|
|
\ No newline at end of file |