I'm sure not the best one to answer, but some things come to mind:
o Units of your graphs ?
o What kind of device does positioning ?
-different devices have (very?) different positioning time response
-many depend on how much they have to move
(in changing filters, that might be how much to rotate a cube)
-sometimes they need to check reference position ?
-sometimes just something happens and a correction takes place that
takes some time
-That's life with measurements ? :)
-Time from previous shot ? Some devices have some "prepare" time so you
can not take 2 shots back to back (or 100, or... i.e. max burst)
-Something else happening in your computer ?
I'm sure there are many others.
Bruno @ 09/05/2020 07:37 -0300 dixit:
> Hi all,
>
> Im commanding the scope with MicroManager through Matlab.
>
> I give the scope a series of instructions to perform an experiment, and I
> timed how much it takes to execute each instruction.
> For example I track how much it takes to change a filter, or change from one
> Group Config to another, or to project an image to the SLM.
>
> There is an average time it takes to execute an operation, but sometimes it
> takes much longer, like funny peaks in timing.
> Did anyone of you have this, and do you know why could it be?
>
> I have several devices and it seems to happen with most of them. So I
> wouldnt say its device specific.
>
> Thanks in advance!
> Best
> Bruno
>
> <
http://micro-manager.3463995.n2.nabble.com/file/t397139/for_mm_forums.png>
>
>
>
> --
> Sent from:
http://micro-manager.3463995.n2.nabble.com/
>
>
> _______________________________________________
> micro-manager-general mailing list
>
micro-mana...@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
> --
Carlos G Mendioroz <
tr...@acm.org>
_______________________________________________
micro-manager-general mailing list
micro-mana...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/micro-manager-general