BUG: lprint in move
It seems the idea to add a lprint
in a move has some drawbacks:
CYRIL [2]: ascan(mm1, 1,2,3, 0.11, sim_ct_2, diot)
Moving mm1 from 2 to 0.99 ] 0/ 4 eta [None]
Moving mm1 from 1 to 1.333[>
Moving mm1 from 1.33 to 1.667===================> ] 2/ 4 eta [00:01
Moving mm1 from 1.67 to 2 ==========> 3 0
Out [2]: Scan(number=33, name=ascan, path=/tmp/fdsf/lysozyme/dfsfs.h5)
see also ID01 remark : cf @homsrego