Input GUI v2: general idea

[chalkie666]

make a new input GUI, that is all imageJ2, replacing IJ1 gerneric dialog stuff with however imageJ2 should do, it... swing. Some general inspiration from JACoP would be good.

The Inpu tGUI should deal with settnig all the input parameters, and not bother with eg. images display,

But could display image parameters that are under 1 sec to calculate, eg mean, max, min, and perform the input data sanity checks and show red flags for stuff that is missing or easy/fast to detect as bad.

[chalkie666]

Yes it's very nice.
But we can push it even further

And we can also implement the noise correction method rnbcc ... Should
make an issue for that. It might be patented. But that's not always a
problem for open source like us.
On 11 Aug 2015 20:27, "Ellen T Arena" [email protected] wrote:

Have you seen the input GUI from SVI?

https://svi.nl/ColocalizationAnalyzer?highlight=colocalization

it's worth a look-see...

—
Reply to this email directly or view it on GitHub
#29 (comment)
.

[etadobson]

@chalkie666 Ok... another question. i'm new to this whole world so bear with me. currently - the methods that are applied in Coloc2 are pixel-based... unlike with JACoP which also allows for object-based methods... would/could this also be in the pipeline for Coloc2v2??

[chalkie666]

This is the million dollar question.

Add object based methods or leave that to other tools like in Mosaic update
site.
Object based methods are doable once try have a good segmentation. But
there are no general segmentation methods that work for everything.

Small blobs vs small blobs
And
Larger extended features vs other stuff
Are very different problems.

There are many ways to define colocalisation in objects sense
This also a place for things to feature creep out of control.
On 11 Aug 2015 23:07, "Ellen T Arena" [email protected] wrote:

@chalkie666 https://github.com/chalkie666 Ok... another question. i'm
new to this whole world so bear with me. currently - the methods that are
applied in Coloc2 are pixel-based... unlike with JACoP which also allows
for object-based methods... would/could this also be in the pipeline for
Coloc2v2??

—
Reply to this email directly or view it on GitHub
#29 (comment)
.