2018
DOI: 10.1007/978-3-319-99954-8_25
|View full text |Cite
|
Sign up to set email alerts
|

SciJava Interface for Parallel Execution in the ImageJ Ecosystem

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2021
2021
2023
2023

Publication Types

Select...
2

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(1 citation statement)
references
References 18 publications
0
1
0
Order By: Relevance
“…They can be invoked from other SciJava‐compatible applications including KNIME Analytics Platform, CellProfiler, OMERO, and others, as well as from user scripts, including for executing in headless mode from the command line, without any graphical user interface (Allan et al., 2012; Dietz et al., 2020; Kamentsky et al., 2011; Möller et al., 2016; Ouyang, Mueller, Hjelmare, Lundberg, & Zimmer, 2019). This is useful in several scenarios, including: for batch analysis across large quantities of data; when combining ImageJ functionality with other systems via standard interprocess interoperability approaches (files and/or pipes); for use within modules of container‐based workflow systems; and for distributed execution of analysis pipelines on server clusters (Krumnikl et al., 2018; Rubens et al., 2020; also see Apeer website in Internet Resources). See Support Protocol 2 for an example of invoking ImageJ headless from the command line.…”
Section: Commentarymentioning
confidence: 99%
“…They can be invoked from other SciJava‐compatible applications including KNIME Analytics Platform, CellProfiler, OMERO, and others, as well as from user scripts, including for executing in headless mode from the command line, without any graphical user interface (Allan et al., 2012; Dietz et al., 2020; Kamentsky et al., 2011; Möller et al., 2016; Ouyang, Mueller, Hjelmare, Lundberg, & Zimmer, 2019). This is useful in several scenarios, including: for batch analysis across large quantities of data; when combining ImageJ functionality with other systems via standard interprocess interoperability approaches (files and/or pipes); for use within modules of container‐based workflow systems; and for distributed execution of analysis pipelines on server clusters (Krumnikl et al., 2018; Rubens et al., 2020; also see Apeer website in Internet Resources). See Support Protocol 2 for an example of invoking ImageJ headless from the command line.…”
Section: Commentarymentioning
confidence: 99%