I am developing an an analyze tool to look at some images and am using particle analysis and I noticed difference if I use the dialog based tool as compared to using copy commands and then running it on an image. More specifically when I run from a the dialog window and select "Save Image Analysis", there is a wave W_particleNumber. Alternatively if I select "Copy Commands" and run it with the image wave there is no W_particleNumber generated. I can certainly write a script to generate one, but is there a flag to do it automatically?
The Copy Commands button refers to the commands needed to generate the image displayed in the dialog and run the generic particle analysis code.
The wave W_particleNumber contains a running index. It is useful if you start sorting the various waves generated by ImageAnalyzeParticles. W_particleNumber is a component in the dialog interface and it is not generated by the commands which only represent the code necessary to threshold and analyze the image. Note that the code similarly does not include instructions to compute any of the stats that are displayed when you choose "All Particles".
It's pretty easy to insert the necessary commands once you've generated the code. For example:
Function WMAnalyzeParticles(inWave) Wave inWave
ImageThreshold/M=4 inWave Wave M_ImageThresh ImageAnalyzeParticles/D=inWave /W/E/A=4 stats M_ImageThresh Duplicate/O $"w_spotx" w_particleNumber //add this code
w_particleNumber=p//add this code End
I would up doing something very similar.
Overall I think there was a step backwards with the Image processing interface based tools in going from IP6 to IP7. You got a much better preview in the IP6 version. IMHO (your mileage may vary). Of course once you get to programmed functions all is fine, but the initial preview is a bit less useful.
Overall I think there was a step backwards with the Image processing interface based tools in going from IP6 to IP7. You got a much better preview in the IP6 version. IMHO (your mileage may vary). Of course once you get to programmed functions all is fine, but the initial preview is a bit less useful.
I hope you are aware that the IP6 Image processing interface is still available for you using the old #includes.
As always, I'd welcome substantive comments about the new Image Processing.
The wave W_particleNumber contains a running index. It is useful if you start sorting the various waves generated by ImageAnalyzeParticles. W_particleNumber is a component in the dialog interface and it is not generated by the commands which only represent the code necessary to threshold and analyze the image. Note that the code similarly does not include instructions to compute any of the stats that are displayed when you choose "All Particles".
October 27, 2016 at 10:50 am - Permalink
Wave inWave
ImageThreshold /M=4 inWave
Wave M_ImageThresh
ImageAnalyzeParticles/D=inWave /W/E/A=4 stats M_ImageThresh
Duplicate/O $"w_spotx" w_particleNumber //add this code
w_particleNumber=p //add this code
End
October 27, 2016 at 11:43 am - Permalink
I would up doing something very similar.
Overall I think there was a step backwards with the Image processing interface based tools in going from IP6 to IP7. You got a much better preview in the IP6 version. IMHO (your mileage may vary). Of course once you get to programmed functions all is fine, but the initial preview is a bit less useful.
Andy
October 27, 2016 at 11:55 am - Permalink
I hope you are aware that the IP6 Image processing interface is still available for you using the old #includes.
As always, I'd welcome substantive comments about the new Image Processing.
A.G.
WaveMetrics, Inc.
October 27, 2016 at 06:07 pm - Permalink