[OpenSPIM] OpenSPIM Digest, Vol 25, Issue 11

[m.pawlowska at nencki.gov.pl]

> From: Johannes Schindelin <johannes.schindelin at gmx.de>
(...)
> Alternatively, it could be that the code is just waiting for the motors
> to arrive at the desired position, which would also not be recorded by
> the profiler.

But we are talking about acquiring a time series, will all the motors 
unchecked in the plugin, so all the movements are 0 steps by definition. 
So it's just the communication with the motors that takes 150 ms, not 
any physical movement:

---
2015-05-07T18:28:18.352459 tid3700 [dbg,Core] Will start absolute move 
of Picard XY Stage to position (0.000, 0.000) um
2015-05-07T18:28:18.384461 tid3700 [dbg,Core] Will start absolute move 
of Picard XY Stage to position (0.000, 0.000) um
2015-05-07T18:28:18.416463 tid3700 [dbg,Core] Will start absolute move 
of Picard Z Stage to position 0.00000 um
2015-05-07T18:28:18.448465 tid3700 [dbg,Core] Will start absolute move 
of Picard R to position -98.88889 um
2015-05-07T18:28:18.480466 tid3700 [dbg,Core] Waiting for device Picard 
R...
2015-05-07T18:28:18.512468 tid3700 [dbg,Core] Finished waiting for 
device Picard R
2015-05-07T18:28:18.512468 tid3700 [dbg,Core] Waiting for device Picard 
Z Stage...
2015-05-07T18:28:18.512468 tid3700 [dbg,Core] Finished waiting for 
device Picard Z Stage
2015-05-07T18:28:18.512468 tid3700 [dbg,Core] Waiting for device Picard 
XY Stage...
2015-05-07T18:28:18.512468 tid3700 [dbg,Core] Finished waiting for 
device Picard XY Stage
---

I suppose there are two questions, both to somebody with a better 
understanding of Micromanager than I:
1. Why is the communication so slow? (Same goes for Robert's laser)
2. Why does the communication with the motors take place if the distance 
to move is 0? Is this a bug, or is the plugin designed like that? How 
hard would it be to change?

(I'm looking at the code trying to figure out the answer to 2, but I 
don't see it yet)

Regards,
Monika