View Issue Details

IDProjectCategoryView StatusLast Update
0002399Slicer4Core: CLI infrastructurepublic2014-05-13 10:01
ReporterlassoanAssigned Tomillerjv 
PrioritynormalSeverityfeatureReproducibilityalways
Status assignedResolutionopen 
Product Version 
Target VersionFixed in Version 
Summary0002399: Automatically generate meaningful names for new nodes
Description

Currently when creating an output node the node name is too generic, such as "Output Volume_1", so the user has to often rename the node to something meaningful.

For CLI modules we could generate meaningful names by combining the name of the input data and the operation that has been applied,
e.g.,
Input volume name: MRI-needle1
Operation: bias correction
Generated output volume name: MRI-needle1-bias-corrected

The automatic naming pattern could be very easily defined in the CLI definition XML file by the "reference" (already exists) and "defaultNames" attributes:

<?xml version="1.0" encoding="utf-8"?>
<executable>
<title>N4ITK MRI Bias correction</title>

<parameters>
<label>IO</label>
<description><![CDATA[Input/output parameters]]></description>
<image>
<longflag>inputimage</longflag>
<name>inputImageName</name>
<label>Input Image</label>
<channel>input</channel>
<description><![CDATA[Input image where you observe signal inhomegeneity]]></description>
</image>

<image reference=”inputImageName” defaultName=”[reference]-bias-corrected”>
<longflag>outputimage</longflag>
<name>outputImageName</name>
<label>Output Volume</label>
<channel>output</channel>
<description><![CDATA[Result of processing]]></description>
</image>

</parameters>
</executable>

TagsNo tags attached.

Activities

jcfr

jcfr

2013-09-17 12:25

administrator   ~0009983

@Jim: Could you have a look at there before the end of the week. The idea would be to cut the 4.3.1 on Monday next week (Sept 23). Thanks

millerjv

millerjv

2013-09-23 11:33

developer   ~0010055

Discussed at the last project week. Larger issue than can be solved for 4.3.1.

Try to address by Winter Project Week.

jcfr

jcfr

2013-09-23 11:41

administrator   ~0010059

Based on note 10055, re-targeting for 4.4.0

jcfr

jcfr

2014-05-13 10:01

administrator   ~0011774

@Jim: If you plan on addressing this before the 4.4 release. Make sure to re-target. Thanks

Issue History

Date Modified Username Field Change
2012-08-14 12:05 lassoan New Issue
2012-08-14 12:05 lassoan Status new => assigned
2012-08-14 12:05 lassoan Assigned To => millerjv
2012-08-22 05:56 jcfr Target Version => Slicer 4.3.0
2013-09-02 13:06 jcfr Target Version Slicer 4.3.0 => Slicer 4.3.1
2013-09-17 12:25 jcfr Note Added: 0009983
2013-09-23 11:33 millerjv Note Added: 0010055
2013-09-23 11:41 jcfr Target Version Slicer 4.3.1 => Slicer 4.4.0
2013-09-23 11:41 jcfr Note Added: 0010059
2014-05-13 10:00 jcfr Target Version Slicer 4.4.0 =>
2014-05-13 10:01 jcfr Note Added: 0011774