Lima issueshttps://gitlab.esrf.fr/limagroup/lima/-/issues2020-03-10T08:29:35+01:00https://gitlab.esrf.fr/limagroup/lima/-/issues/103Int/ExtTriggerMulti: Distiguish between detector status Idle and WaitForTrigger2020-03-10T08:29:35+01:00Laurent ClaustreInt/ExtTriggerMulti: Distiguish between detector status Idle and WaitForTriggerThe detector status is a bit mask:
* DetIdle means the acquisition is finished (readout of last frame done): ready for a new prepareAcq
* DetWaitForTrigger means detector head is ready to receive a new software/hardware trigger
Todo: ...The detector status is a bit mask:
* DetIdle means the acquisition is finished (readout of last frame done): ready for a new prepareAcq
* DetWaitForTrigger means detector head is ready to receive a new software/hardware trigger
Todo:
* Remove HwInterface::Status::Basic
* Simulator, Frelon and Eiger, among others
* LimaCCDs attr ready_for_next_image
* This must been included in CtControl::startAcq()v1.10.0https://gitlab.esrf.fr/limagroup/lima/-/issues/116Data saving with HDF5 shows low performance2020-06-10T12:01:44+02:00Alejandro Homs PuronData saving with HDF5 shows low performanceWhen performing acquisitions with the Dectris/Eiger2 under X-ray generator photons at ID22, the effective data saving performance is very low:
> The current illumination scheme generate compressed images of ~450 kByte. Under this regim...When performing acquisitions with the Dectris/Eiger2 under X-ray generator photons at ID22, the effective data saving performance is very low:
> The current illumination scheme generate compressed images of ~450 kByte. Under this regime, at 2 kHz frame rate, we found a limiting saving speed on BeeGFS with HDF5-BSLZ4 of ~450 MByte/s (when 900 MByte/s is needed). The interesting news is that we found more or less the same limit saving on one NVME drive, contrary to what we expected
https://gitlab.esrf.fr/limagroup/lima/-/issues/108Usage of [[maybe_unused]] and other C++17 attributes2020-05-20T14:48:53+02:00Samuel DebionneUsage of [[maybe_unused]] and other C++17 attributesThe following discussion from !158 should be addressed:
- [ ] @debionne started a [discussion](https://gitlab.esrf.fr/limagroup/lima/-/merge_requests/158#note_70720): (+8 comments)
> `[[maybe_unused]]` is C++17 but should be harml...The following discussion from !158 should be addressed:
- [ ] @debionne started a [discussion](https://gitlab.esrf.fr/limagroup/lima/-/merge_requests/158#note_70720): (+8 comments)
> `[[maybe_unused]]` is C++17 but should be harmless (even for MSVC) but might generate a warning... which is what you are trying to avoid.https://gitlab.esrf.fr/limagroup/lima/-/issues/105Missing explicit way to know when prepareAcq can be called after an error2020-04-06T14:54:41+02:00Alejandro Homs PuronMissing explicit way to know when prepareAcq can be called after an errorAfter an error event the `AcqStatus` passes to `AcqFault`, and the clients cannot know then the processing has finish in order to call a new `prepareAcq`.
Possible solutions:
* Add AcqFaultStopping stateAfter an error event the `AcqStatus` passes to `AcqFault`, and the clients cannot know then the processing has finish in order to call a new `prepareAcq`.
Possible solutions:
* Add AcqFaultStopping statev1.10.0https://gitlab.esrf.fr/limagroup/lima/-/issues/104new CtAcquisition FramePerTrigger parameter2020-03-06T11:07:51+01:00Laurent Claustrenew CtAcquisition FramePerTrigger parameterThis will replace the TrigSequences trigger mode in Eiger experimental branch used on ID30a3.
This must work for both hw and soft triggers
Todo:
* Eiger
* Frelon
* Maxipix
* Simulator (useful to have test with mesh in bliss CI)This will replace the TrigSequences trigger mode in Eiger experimental branch used on ID30a3.
This must work for both hw and soft triggers
Todo:
* Eiger
* Frelon
* Maxipix
* Simulator (useful to have test with mesh in bliss CI)v1.10.0https://gitlab.esrf.fr/limagroup/lima/-/issues/84delation of external operation during acquisition not manage2019-03-13T15:07:18+01:00Laurent Claustredelation of external operation during acquisition not manageThat crashes something and the acquisition is endless till an abortAcq.
Solution, forbid the extOp.delete() during acquisitionThat crashes something and the acquisition is endless till an abortAcq.
Solution, forbid the extOp.delete() during acquisitionLaurent ClaustreLaurent Claustre