MurphysLab

joined 2 years ago
[–] MurphysLab@lemmy.ca 2 points 2 years ago

I'm not aware of a debugger for javascript scripts for ImageJ. 95% of what I need can be accomplished in the macro language. Roughly how many lines is your script?

[–] MurphysLab@lemmy.ca 2 points 2 years ago

Definitely there is some hard truth, however in the problems as you note are that it is often a black box and not reproducible nor necessarily quantitative among many other problems. I see more of an increasing divide between those who create those AI tools and those who apply them. There's always been some of this with ImageJ, and macros or plugins have served as a bridge. I foresee similar bridges in the future.

Everything in the future is looking a bit shakey lately with how society and technology continues to co-evolve, so I wish you luck with the career side; I think we all need a bit of luck there.

[–] MurphysLab@lemmy.ca 2 points 2 years ago (2 children)

With ImageJ there was a major democratization in the accessibility of image analysis. It opened up the doors to greater involvement by non-compsci folks; people whose approach is guided and enriched by a deeper mechanistic understanding of what they are looking at. My view is that many of the job posts related to the field are being driven by HR people & committees whose "contribution" is peppering everything with novel buzzwords without understanding the relevance nor the meaning. Especially with academics, there's a habit of chasing after whatever was used in the latest "hot" paper without understanding what it is, how it works, or if it is applicable, at least when that hot new thing is outside of the prof's expertise. They don't need to learn it; they can just tell a grad student to do it.

[–] MurphysLab@lemmy.ca 2 points 2 years ago* (last edited 2 years ago) (1 children)

Generally I've preferred using the showProgress function in ImageJ, since it doesn't require a new window:

showProgress(progress)

Updates the ImageJ progress bar, where 0.0progress<=1.0. The progress bar is not displayed if the time between the first and second calls to this function is less than 30 milliseconds. It is erased when the macro terminates or progress is >=1.0. Use negative values to show subordinate progress bars as moving dots (example).

showProgress(currentIndex, finalIndex)

Updates the progress bar, where the length of the bar is set to currentIndex/finalIndex of the maximum bar length. The bar is erased if currentIndex>finalIndex or finalIndex==0.

 

The July 11th editorial in the journal, Nature Methods offers an overview of a suite of articles focused on the future of image analysis. The editorial and the technology feature are both available to read for free, while the other articles are paywalled. Here's an index of the articles for anyone who might be interested: