View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002361 | Slicer4 | Core: CLI infrastructure | public | 2012-07-27 08:05 | 2014-03-06 05:23 |
Reporter | muratmaga | Assigned To | millerjv | ||
Priority | low | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | Slicer 4.1.0 | ||||
Target Version | Slicer 4.3.0 | Fixed in Version | Slicer 4.3.0 | ||
Summary | 0002361: resamplescalarvectordwi.exe CLI module does not function in windows | ||||
Description | Slicer --launch lib/Slicer-4.1/cli-modules/ResampleScalarVolume.exe --spacing 2,2,2 c:/temp/807-r1_rec.nhdr cli.hdr Gives the downsampled output I want but Slicer --launch lib/Slicer-4.1/cli-modules/ResampleScalarVectorDWIVolume.exe --spacing 2,2,2 c:/temp/807-r1_rec.nhdr cli.hdr I also wasn't able to locate any command line options for this module via --help option | ||||
Tags | No tags attached. | ||||
Issue targeted for 4.2.0, re-target if it can't be addressed by sept 1st. |
|
Just tried: The format might be different for the call, it's a more complicated module than ResampleScalarVolume. |
|
If the module are executed within a installed tree, console IO are disabled in the launcher. See issue 0001683 |
|
Murat> Could you provide the data causing problem ? |
|
Considering that:
.. the issue as been retargeted to 4.3 |
|
When I issue the following command in Windows 7, nothing (not even the splash screen) happens. Version I use is 4.1.1 C:\Program Files (x86)\Slicer 4.1.1>Slicer --launch lib/Slicer-4.1/cli-modules/R Without the --help option the Splash screen come up for a second. Thus, I cannot locate the proper command line options for this tool to run it correctly. |
|
Try running it from the GUI and then looking in the Error Log window for the command line output to see what arguments are being passed in that case. |
|
Here is a workaround: 1) C:\Program Files (x86)\Slicer 4.1.1>Slicer --launch "C:/Windows/System32/cmd.exe" /c start cmd 2) It should then be possible to invoke any executable and see the associated output. You could also add the following to bin/SlicerLauncherSettings.ini. It would then be possible to start a "cmd.exe" with the Slicer env doing the following: ./Slicer --cmd [ExtraApplicationToLaunch] cmd/shortArgument= |
|
Since a workaround has been provided and the issue has not been updated in more than 6 months, resolving the issue. Note also that the "--cmd" argument has been added to Slicer launcher in r19596 [1] [1] http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=19596 |
|
Closing resolved issues that have not been updated in more than 3 months |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2012-07-27 08:05 | muratmaga | New Issue | |
2012-07-27 08:05 | muratmaga | Status | new => assigned |
2012-07-27 08:05 | muratmaga | Assigned To | => millerjv |
2012-08-22 05:53 | jcfr | Target Version | => Slicer 4.2.0 - Feature freeze Sept 1st 2012 |
2012-08-22 05:53 | jcfr | Note Added: 0005688 | |
2012-10-25 11:41 | jcfr | Priority | normal => low |
2012-10-25 11:47 | nicole | Note Added: 0006755 | |
2012-10-25 11:47 | nicole | Note Edited: 0006755 | |
2012-10-25 12:10 | jcfr | Note Added: 0006759 | |
2012-10-25 12:14 | jcfr | Note Added: 0006760 | |
2012-10-25 12:14 | jcfr | Target Version | Slicer 4.2.0 - coming release => Slicer 4.3.0 |
2012-10-25 12:15 | jcfr | Note Added: 0006761 | |
2012-10-25 12:15 | jcfr | Status | assigned => feedback |
2012-10-25 12:32 | muratmaga | Note Added: 0006763 | |
2012-10-25 12:42 | nicole | Note Added: 0006768 | |
2012-10-25 12:50 | jcfr | Note Added: 0006769 | |
2013-07-31 20:37 | jcfr | Note Added: 0009320 | |
2013-07-31 20:37 | jcfr | Status | feedback => resolved |
2013-07-31 20:37 | jcfr | Fixed in Version | => Slicer 4.3.0 |
2013-07-31 20:37 | jcfr | Resolution | open => fixed |
2014-03-06 05:21 | jcfr | Note Added: 0011148 | |
2014-03-06 05:23 | jcfr | Status | resolved => closed |