... | ... | @@ -46,7 +46,7 @@ Foresee a discussion meeting with Det group for lima3 plan |
|
|
|
|
|
COD tasks
|
|
|
---------
|
|
|
- dev of lima 2.0
|
|
|
- dev of lima 2
|
|
|
- BinRoiFlipRot
|
|
|
- De-couple Acq and processing ??
|
|
|
- Processlib for mutli-branches ??
|
... | ... | @@ -57,4 +57,22 @@ COD tasks |
|
|
|
|
|
Next
|
|
|
- write COD position paper
|
|
|
- meeting with Det group for defining COD deliverables for lima2 lima3 roadmap |
|
|
\ No newline at end of file |
|
|
- meeting with Det group for defining COD deliverables for lima2 lima3 roadmap
|
|
|
- Define the good architecture for Lima 3
|
|
|
|
|
|
|
|
|
Architecture for Lima 3
|
|
|
=======================
|
|
|
|
|
|
After last discussion Alejandro and Sebastien proposed two different approaches.
|
|
|
Seb: A Distributed Lima with 2 stages
|
|
|
- back-end stage (acquisition) should manage balancing of images or part of images on several computers to a storage area
|
|
|
- front-end stage (processing) should manage ready images for further processing
|
|
|
Pros:
|
|
|
Cons:
|
|
|
Alejandro: A Distributed Lima single stage
|
|
|
Both acquisition and processing should be manage as a single stage as it is today.
|
|
|
Pros:
|
|
|
Cons:
|
|
|
|
|
|
|