Multiple threads

[Douglas Benn-2]

Dear Colleagues,

I am running a macro and within that macro I am running Orthogonal Views using doCommand("Orthogonal Views") so I have a separate thread. Orthogonal Views works fine for about 2 cursor point selections on the axial view and then it ceases to function. I think there is probably some sort of side effect from my main macro code that is interfering with Orthogonal Views.

I think a possible work around might be to execute the doCommand("Orthogonal Views"), perform one cursor point click and then kill the Orthogonal View thread. When my main macro returns to the top of its loop I can restart Orthogonal Views with the doCommand("Orthogonal Views") again.  I would like some advice please on how to identify which of my 2 threads is Orthogonal Views so I can kill the correct thread and also how to kill a thread.

Thanks.

Douglas

Dr Douglas K Benn, BDS,DDS, M.Phil., Ph.D., Dipl. Dental Radiology (Royal College of Radiologists, England).
Professor and Director of Oral & Maxillofacial Radiology
Dept of General Dentistry
Creighton University Dental School
2802 Webster St, Boyne 210
Omaha
Nebraska 68178

Tel: [phone]
Fax: [phone]

[Michael Schmid]

Hi Douglas,

did you try the ThreadKiller plugin?
   http://rsb.info.nih.gov/ij/plugins/thread-killer.html

It uses a GenericDialog for selecting the thread, so it should be  
even macro-recordable.

Michael
________________________________________________________________

On 6 May 2010, at 02:59, Benn, Douglas K. wrote:

> Dear Colleagues,
>
> I am running a macro and within that macro I am running Orthogonal  
> Views using doCommand("Orthogonal Views") so I have a separate  
> thread. Orthogonal Views works fine for about 2 cursor point  
> selections on the axial view and then it ceases to function. I  
> think there is probably some sort of side effect from my main macro  
> code that is interfering with Orthogonal Views.
>
> I think a possible work around might be to execute the doCommand
> ("Orthogonal Views"), perform one cursor point click and then kill  
> the Orthogonal View thread. When my main macro returns to the top  
> of its loop I can restart Orthogonal Views with the doCommand
> ("Orthogonal Views") again.  I would like some advice please on how  
> to identify which of my 2 threads is Orthogonal Views so I can kill  
> the correct thread and also how to kill a thread.
>
> Thanks.
>
> Douglas
>
> Dr Douglas K Benn, BDS,DDS, M.Phil., Ph.D., Dipl. Dental Radiology  
> (Royal College of Radiologists, England).
> Professor and Director of Oral & Maxillofacial Radiology
> Dept of General Dentistry
> Creighton University Dental School
> 2802 Webster St, Boyne 210
> Omaha
> Nebraska 68178
>
> Tel: [phone]
> Fax: [phone]

[dscho]

Hi,

On Thu, 6 May 2010, Michael Schmid wrote:

> did you try the ThreadKiller plugin?
>  http://rsb.info.nih.gov/ij/plugins/thread-killer.html
>
> It uses a GenericDialog for selecting the thread, so it should be even
> macro-recordable.

The names of threads are not well preserved, so I would recommend against
that.

Ciao,
Johannes

[Douglas Benn-2]

Dear Johannes & Michael,

Using doCommand("Orthogonal Views") within my macro loop seems to cure
the problem so I assume that executing doCommand("Orthogonal Views") a
second time kills the first thread. The Orthogonal Views response time
to selecting a new slice in a stack and updating it is slower than using
Orthogonal Views outside of a loop. I will experiment with turning on
batch mode and perhaps this will improve.

I did try thread-killer and got a run time error on the 1st line saying
it did not recognize the module it was supposed to load. However, since
Johannes says the thread names are not well preserved I will not spend
more time on this.

Thanks for your help.

Douglas

-----Original Message-----
From: ImageJ Interest Group [mailto:[hidden email]] On Behalf Of
Johannes Schindelin
Sent: Thursday, May 06, 2010 6:40 AM
To: [hidden email]
Subject: Re: Multiple threads

Hi,

On Thu, 6 May 2010, Michael Schmid wrote:

> did you try the ThreadKiller plugin?
>  http://rsb.info.nih.gov/ij/plugins/thread-killer.html
>
> It uses a GenericDialog for selecting the thread, so it should be even
> macro-recordable.

The names of threads are not well preserved, so I would recommend
against
that.

Ciao,
Johannes