[OpenSPIM] WG: Re: WG: Antwort: Re: "Stack at this Z plus" problem persisting
edgar.escobar.nieto at ipt.fraunhofer.de
edgar.escobar.nieto at ipt.fraunhofer.de
Thu Nov 7 13:03:43 CST 2013
Hi Luke,
There was not message error and no response when launching the SPIMage acquisition plugin, that was the most surprising.
About the hs_err file all were the same even if I was using the Demo Camera configuration. Only using the Windows 7 64 bit PC I didn't
get any hs_err file.
Today I launch the plugin and it works again, I really don't know why it was not working on monday (even in two different PCs).
Surprisingly I got a message window when pressing "Stack at this Z plus" button. The message was: Couldn't create stack: For input string "3493,500",
for this case 3493,500 was the currently Z position when pressing the "Stack at this Z plus" button.
Today I didn't get any hs_err file by the way. :-)
I attach two corelog files, in one the debug log option is enabled. In both corelog files the first attempt is using the demo cam hardware configuration,
the secon attempt is using the TIS CAM hardware configuration.
What I could guess from the corelog file is that the problem could be the way the value of the Z position is handled. I am not sure but I think
that this issue started since the resolution in the stage position values are managed as 1,5 um instead of 1 um.
Hope this information is useful. Thanks again.
Kind regards,
Edgar
_________________________________________________________________________
Fraunhofer-Institut für Produktionstechnologie IPT
Edgar Escobar Nieto
Steinbachstraße 17
52074 Aachen
edgar.escobar.nieto at ipt.fraunhofer.de
http://www.ipt.fraunhofer.de
_________________________________________________________________________
-----Luke Stuyvenberg <stuyvenberg at wisc.edu> schrieb: -----
An: edgar.escobar.nieto at ipt.fraunhofer.de
Von: Luke Stuyvenberg <stuyvenberg at wisc.edu>
Datum: 06.11.2013 21:52
Kopie: openspim at openspim.org
Betreff: Re: WG: Re: WG: Antwort: Re: "Stack at this Z plus" problem persisting
Hi Edgar,
On 11/04/13, edgar.escobar.nieto at ipt.fraunhofer.de wrote:
> I attach the corelog and the error file although they don't say too much about what is the cause of the problem.
Curiouser and curiouser -- not a single error is produced by the plugin launch, and yet it isn't displayed? It certainly seems to be a much deeper issue than I initially suspected.
On 11/04/13, edgar.escobar.nieto at ipt.fraunhofer.de wrote:
> Now that I update Fiji again I am not able to start the plugin SPIMage Acquisition. It is so strange because
> even using different hardware configurations (D_cam instead of TIS_cam) it doesn't work. :-/
A different camera adapter had no better luck? Did it too produce an hs_err file that might be different from the others?
Since you aren't using the Cube, you might try enabling the further debug output, if it's not already turned on: From Micro-Manager, click Tools -> Options, and check Debug Log Enabled. This will produce significantly more output in the Core Log. (I say the absence of a Cube is an advantage in this situation; the laser is queried once per second, and in debug logging mode, the messages become difficult to sift through.) With luck, this might provide more detailed information.
Thank you again,
Luke
On 11/04/13, edgar.escobar.nieto at ipt.fraunhofer.de wrote:
> Hi Luke,
>
> Now that I update Fiji again I am not able to start the plugin SPIMage Acquisition. It is so strange because
> even using different hardware configurations (D_cam instead of TIS_cam) it doesn't work. :-/
>
> I tried also in the other computer (Win 7, 64 bit) and didn't work as well.
>
> I attach the corelog and the error file although they don't say too much about what is the cause of the problem.
>
> Kind regards,
> Edgar
>
>
> _________________________________________________________________________
>
> Fraunhofer-Institut für Produktionstechnologie IPT
> Edgar Escobar Nieto
>
>
>
>
> Steinbachstraße 17
> 52074 Aachen
>
> edgar.escobar.nieto at ipt.fraunhofer.de
> http://www.ipt.fraunhofer.de(http://www.ipt.fraunhofer.de/(http://www.ipt.fraunhofer.de/" target="1"> http://www.ipt.fraunhofer.de
> _________________________________________________________________________
>
>
>
>
>
>
> -----Weitergeleitet von Edgar Escobar Nieto/Fraunhofer IPT am 04.11.2013 14:39 ----- An: Luke Stuyvenberg <stuyvenberg at wisc.edu>
> Von: Edgar Escobar Nieto/Fraunhofer IPT
> Datum: 01.11.2013 17:34
> Kopie: openspim at openspim.org
> Betreff: Re: WG: Antwort: Re: "Stack at this Z plus" problem persisting
>
> Hi Luke,
>
> Yes, the issue happens, at least to me, regardless of the operating system and of the architecture.
> I don't know if someone else is facing this issue as well.
>
> I did check the plugin using the no shutter configuration, now any message that the setup
> is not complete appears when starting the plugin, but the problem persists.
>
> Yes, the 4 motors are fully functional and all they report the actual position correctly.
>
> I will update Fiji again on monday, and I will let you know what happen.
>
> Thanks to you,
> Edgar
>
>
> _________________________________________________________________________
>
> Fraunhofer-Institut für Produktionstechnologie IPT
> Edgar Escobar Nieto
>
>
>
>
> Steinbachstraße 17
> 52074 Aachen
>
> edgar.escobar.nieto at ipt.fraunhofer.de
> http://www.ipt.fraunhofer.de
> _________________________________________________________________________
>
>
>
>
>
>
> -----Luke Stuyvenberg <stuyvenberg at wisc.edu> schrieb: ----- An: edgar.escobar.nieto at ipt.fraunhofer.de
> Von: Luke Stuyvenberg <stuyvenberg at wisc.edu>
> Datum: 31.10.2013 20:48
> Kopie: openspim at openspim.org
> Betreff: Re: WG: Antwort: Re: "Stack at this Z plus" problem persisting
>
> Hi Edgar,
>
> So the issue appears regardless of operating system (Windows XP versus Windows 7) and architecture (32-bit versus 64-bit)? Did you try going back to the no-shutter configuration? (It shouldn't have a problem now that I've added some checks for an absent laser.)
>
>
> I take it all the motor controls are fully functional? That is, the sliders all report the current position correctly, and let you change the position without trouble, for all four stage axes?
>
> I've uploaded another version of the plugin which is a little more direct about its error reporting; please try updating once more -- although this may not fix the issue, it might produce useful error output.
>
>
> Thanks again,
> Luke
>
>
> On 10/31/13, edgar.escobar.nieto at ipt.fraunhofer.de wrote:
> > Hi Luke,
> >
> > About the error files, you are right, they appear as long as I close æManager/Fiji. The "Stack at this Z plus" button is the only problem, I can
> > still made everthing else as I menctioned before. I just updated Fiji and the problem persist. The button is unstucked as long as I move the mouse
> > cursor outside the area of the button and I am able to click it again. The problem is comparable as if I place the cursor over a normal button e.g.
> > Oh Snap!, then click the mouse and move the cursor outside Oh Snap! and finally release the mouse outside Oh Snap!
> > If you do that simply nothing happens. That is just the way the "Stack at this Z plus" button behaves.
> >
> > I also thought that the problem was related with the TIS cam but I already test Fiji in a different computer (Windows 7 64 bits). In that computer
> > is not installed any driver or software from the camera. I made a test using only the Picard Stage, a demo shutter and a demo camera
> > and the problem about "Stack at this Z plus" remains, the only difference I noticed is that when I close æManager/Fiji there is no error files.
> >
> > Hope this information is useful. Have a happy longweekend.
> >
> > Kind regards,
> > Edgar
> >
> >
> >
> >
> >
> >
> > _________________________________________________________________________
> >
> > Fraunhofer-Institut fr Produktionstechnologie IPT
> > Edgar Escobar Nieto
> >
> >
> >
> >
> > Steinbachstraáe 17
> > 52074 Aachen
> >
> > edgar.escobar.nieto at ipt.fraunhofer.de
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openspim.org/pipermail/openspim/attachments/20131107/5008ed94/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CoreLog20131107.txt
Type: application/octet-stream
Size: 57722 bytes
Desc: not available
URL: <http://openspim.org/pipermail/openspim/attachments/20131107/5008ed94/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CoreLog20131107 (debug log enabled).txt
Type: application/octet-stream
Size: 33941 bytes
Desc: not available
URL: <http://openspim.org/pipermail/openspim/attachments/20131107/5008ed94/attachment-0005.obj>
More information about the OpenSPIM
mailing list