Lima issueshttps://gitlab.esrf.fr/limagroup/lima/-/issues2020-06-29T10:45:21+02:00https://gitlab.esrf.fr/limagroup/lima/-/issues/119Manual saving hdf5 frames are not contiguous2020-06-29T10:45:21+02:00Laurent ClaustreManual saving hdf5 frames are not contiguousWhen doing manual saving of a subset of the acquired frames, hdf5 container should save the frames in a contiguous dataset independently of the frame numberWhen doing manual saving of a subset of the acquired frames, hdf5 container should save the frames in a contiguous dataset independently of the frame numberv1.9.5https://gitlab.esrf.fr/limagroup/lima/-/issues/118h5 saving: frames_per_file not adjusted to the nb of frames2020-06-29T10:45:21+02:00Laurent Claustreh5 saving: frames_per_file not adjusted to the nb of framesWhen acquiring less frames than the frames_per_file parameter, CtSaving must passed to h5 container a total number of frames = to the acq number of frames if it it less than the parameters frames_per_files. And if more than one file is r...When acquiring less frames than the frames_per_file parameter, CtSaving must passed to h5 container a total number of frames = to the acq number of frames if it it less than the parameters frames_per_files. And if more than one file is required to save all the frames (frames_per_file < acq_nb_frames) the last file must be created for the exact number of remaining frames.
v1.9.5https://gitlab.esrf.fr/limagroup/lima/-/issues/117manual saving broken with frame number equal -12020-06-29T10:45:21+02:00Laurent Claustremanual saving broken with frame number equal -1When acquiring with manual saving mode, then asking for saving the last frame with -1 as frame number does not workWhen acquiring with manual saving mode, then asking for saving the last frame with -1 as frame number does not workv1.9.5Laurent ClaustreLaurent Claustrehttps://gitlab.esrf.fr/limagroup/lima/-/issues/115Memory corruption error after using CtControl::ImageStatusCallback2020-06-29T10:51:13+02:00Alejandro Homs PuronMemory corruption error after using CtControl::ImageStatusCallbackThe [test_int_trig_mult.py](/uploads/d36e153ac5956bac5b46bf922916b115/test_int_trig_mult.py) program systematically shows memory corruption errors with the Simulator, Eiger, and SlsDetector plugins:
```
Valid ranges:
min_exp_time=0.0...The [test_int_trig_mult.py](/uploads/d36e153ac5956bac5b46bf922916b115/test_int_trig_mult.py) program systematically shows memory corruption errors with the Simulator, Eiger, and SlsDetector plugins:
```
Valid ranges:
min_exp_time=0.0000000, max_exp_time=1000000.0000000
min_lat_time=0.0000000, max_lat_time=1000000.0000000
Starting acquisition ...
Sending start #0
Sending start #1
Sending start #2
Sending start #3
Sending start #4
Sending start #5
Sending start #6
Sending start #7
Sending start #8
Sending start #9
Average trigger_delay=0.078 (0.010 + 0.068)
Acquisition finished -0.000 sec after trigger sequence
[2020/06/08 17:31:48.478623] 7fe06f1de740 *Control*Control::Control::unregisterImageStatusCallback (/users/opid00/esrf/sls_detectors/Lima/control/src/CtControl.cpp:1260)-Always: Unregistering 0x557bb770bc40
double free or corruption (out)
```v1.9.5Alejandro Homs PuronAlejandro Homs Puron