All scripting languages have access to a universal
@parameter notation for declaring inputs and outputs. This approach is preferred to using ImageJ 1.x
GenericDialog because it is totally agnostic of the user interface, allowing such scripts to run in a variety of contexts. As with ImageJ2 plugins, script parameterization is based on the SciJava @Parameter annotation—so experience with plugin writing directly translates to scripting, and vice versa.
The rules for
@parameter use are as follows:
- All parameter declarations must appear in comments. Each comment line contains a single parameter declaration and nothing else.
- Any parameters after the first non-parameter line will not be recognized.
@type variableNamewill declare an input of the indicated type, assigned to the specified name.
@OUTPUT type outputNamewill declare the variable of the specified name as an output parameter with the given type.
# @String name # @OUTPUT String greeting # A Jython script with parameters. # It is the duty of the scripting framework to harvest # the 'name' parameter from the user, and then display # the 'greeting' output parameter, based on its type. greeting = "Hello, " + name + "!"
We see that an input parameter
name of type
String is declared.
@arameters are handled automatically by the framework; if we run this script when the User Interface is available (e.g. from the script editor), the
name parameter will automatically be harvested via a pop-up dialog:
We could also run this script headlessly, thanks to the general nature of
When the script is completed, any
@OUTPUT variables are handled by the framework, based on their type. In this case we expect the
greeting variable to be printed, since it is a
A list of possible data types and the corresponding widgets is provided:
|Data type||Widget type|
||(>=2 images) triggers a dropdown list|
By implementing InputWidget it is possible to extend this list.
If you look at the @Parameter annotation, you will notice it has many properties—for example,
Script parameters can set these properties, following these guidelines:
- All properties are defined in a single parenthetical expression immediately following the
- Properties are set by a comma-separated list of key=value pairs
Properties are your way to customize how an
@parameter should be handled by the framework.
Widgets are the User Interface elements shown to users to collect input information. For example, instead of just displaying "Name" to the user, we can add a custom label to the field of our
Greeting.py script as follows:
# @String(label="Please enter your name") name # @OUTPUT String greeting greeting = "Hello, " + name + "!"
We can add a
description property to provide mouse-over text for our field:
# @String(label="Please enter your name", description="Your name") name # @OUTPUT String greeting greeting = "Hello, " + name + "!"
Default values are also supported as parameter properties:
# @Integer(label="An integer!",value=15) someInt
Files and Folders
By default, a `@File` parameter will create a chooser for a single file:
# @File(label="Select a file") myFile print(myFile)
If you want to select a directory instead, use a
# @File(label="Select a directory", style="directory") myDir print(myDir)