Skip to content, Skip to search

Changes

Op Finder

96 bytes added, 11:01, 6 May 2016
Code Snippets
</source>
5. Now At this stage, we need to get inputs can not actually run our code yet. The pasted snippet serves as a guideline for our Op, what types of parameters are needed and ensure produced. The next step is to ask the output is displayed. These tasks can all be handled with additional framework for instances of these parameters by adding [[Script_parameters|@Parameters]] added to the our script:
<source lang="python">
</source>
: '''Note:''' the types we copied and pasted just (<code>Img</code> and <code>RandomAccessibleInterval</code>) represent a ''minimum class requirement''. Open images will almost can always be requested as <code>Datasets</code>, which themselves have an <code>a type hierarchy including {{Bc|ImgPlus|Img|RandomAccessibleInterval}}. </code>, which has an <code>ImgDataset</code> which is thus a <code>RandomAccessibleInterval</code>good starting point as it can satisfy any of these parameters. If you want to have multiple input images image parameters, you should '''must''' use <code>@Dataset</code>. A safe alternative for single inputs is <code>ImgPlus</code>. Both of these classes contain additional metadata which can be useful in your script.
6. Our script is done! If we open a base image and kernel in ImageJ we can run our script. The <code>OpService</code> is populated automatically by the ImageJ framework, and an input window is automatically created to select the images:
Bureaucrat, emailconfirmed, incoming, administrator, uploaders
735
edits