SCIRun Scripts on SPL Machines - Revision history

Mjolley: /* High-Throughput SCIRun Scripts on SPL Machines */

2007-08-02T10:19:49Z

High-Throughput SCIRun Scripts on SPL Machines

Mjolley: /* High-Throughput SCIRun Scripts on SPL Machines */

2007-08-02T10:16:30Z

High-Throughput SCIRun Scripts on SPL Machines

Mjolley: /* High-Throughput SCIRun Scripts on SPL Machines */

2007-08-02T09:58:56Z

High-Throughput SCIRun Scripts on SPL Machines

Mjolley at 22:18, 1 August 2007

2007-08-01T22:18:05Z

New page

== High-Throughput SCIRun Scripts on SPL Machines ==

← Older revision		Revision as of 10:19, 2 August 2007
Line 3:		Line 3:
	SCIRun scripts running SCIRun -E in bash were initially not working despite SCIRun building fine and all the manual nets working. The script nets and manual nets are in theory the same except for paths etc. Ultimately trashing the /SCIRun folder containing "on-the-fly-libs" and "tmp" in entirety and then deleting ".scrirunrc" and letting SCIRun regenerate both allowed the scripts to run. Note thse files are not in the SCIRun svn directory such as "/trunk/" etc, but created the first time you run SCIRun, usually in your ~/ directory unless you specify otherwise. This should not be an issue if you have never run SCIRun on a machine before, but might be if you have ever run SCIRun prior on a given machine.		SCIRun scripts running SCIRun -E in bash were initially not working despite SCIRun building fine and all the manual nets working. The script nets and manual nets are in theory the same except for paths etc. Ultimately trashing the /SCIRun folder containing "on-the-fly-libs" and "tmp" in entirety and then deleting ".scrirunrc" and letting SCIRun regenerate both allowed the scripts to run. Note thse files are not in the SCIRun svn directory such as "/trunk/" etc, but created the first time you run SCIRun, usually in your ~/ directory unless you specify otherwise. This should not be an issue if you have never run SCIRun on a machine before, but might be if you have ever run SCIRun prior on a given machine.

−	Simply deleting and regenerating "on-the-fly-libs" and ".scirunrc did" not work. The entire "SCIRun folder", then ".scirunrc" needed to both be deleted and then SCIRun run. I am not sure why the scripts are more sensitive to this. A hint to need to do this would be if it brings up screen ~~every time it~~ tries to update ".scirunrc" everytime a new SCIRun is opened in the script, or if your nets called by a script simply don't run, when the manual ones do.	+	Simply deleting and regenerating "on-the-fly-libs" and ".scirunrc did" not work. The entire "SCIRun folder", then ".scirunrc" needed to both be deleted and then SCIRun run. I am not sure why the scripts are more sensitive to this. A hint to need to do this would be if it brings up screen that tries to update ".scirunrc" everytime a new SCIRun is opened in the script despite having a current version of ".scirunrc", or if your nets called by a script simply don't run, when the manual ones do.

@@ Line 1: / Line 1: @@
 == High-Throughput SCIRun Scripts on SPL Machines ==
-SCIRun scripts running SCIRun -E in bash were initially not working despite SCIRun building fine and all the manual nets working.  The script nets and manual nets are in theory the same except for paths etc.  Ultimately trashing the /SCIRun folder containing "on-the-fly-libs" and "tmp" in entirety and then deleting ".scrirunrc" and letting SCIRun regenerate both allowed the scripts to run.  Note this is not in the SCIRun svn directory such as  "/trunk" etc, but created the first time you run SCIRun, usually created in your ~/ directory.  This should not be an issue if you have never run SCIRun on a machine before, but might be if you have prior versions.
+SCIRun scripts running SCIRun -E in bash were initially not working despite SCIRun building fine and all the manual nets working.  The script nets and manual nets are in theory the same except for paths etc.  Ultimately trashing the /SCIRun folder containing "on-the-fly-libs" and "tmp" in entirety and then deleting ".scrirunrc" and letting SCIRun regenerate both allowed the scripts to run.  Note thse files are not in the SCIRun svn directory such as  "/trunk/" etc, but created the first time you run SCIRun, usually in your ~/ directory unless you specify otherwise.  This should not be an issue if you have never run SCIRun on a machine before, but might be if you have ever run SCIRun prior on a given machine.
-Simply deleting and regenerating "on-the-fly-libs" and ".scirunrc did" not work.  The "SCIRun folder", then ".scirunrc" needed to both be deleted and then SCIRun run.  I am not sure why the scripts are more sensitive to this but with some builds you might need to trash these to run SCIRun -E with scripts, despite it working just fine in the standard manual situation for which SCIRun is most typically used.  I have also not seen it on other machines.  A hint would be if it tries to update ".scirunrc" everytime a new SCIRun is opened in the script.
+Simply deleting and regenerating "on-the-fly-libs" and ".scirunrc did" not work.  The entire "SCIRun folder", then ".scirunrc" needed to both be deleted and then SCIRun run.  I am not sure why the scripts are more sensitive to this.   A hint to need to do this would be if it brings up screen every time it tries to update ".scirunrc" everytime a new SCIRun is opened in the script, or if your nets called by a script simply don't run, when the manual ones do.

← Older revision		Revision as of 09:58, 2 August 2007
Line 1:		Line 1:
		+	== High-Throughput SCIRun Scripts on SPL Machines ==

−	~~== High~~-~~Throughput~~ SCIRun ~~Scripts~~ on ~~SPL Machines ==~~	+	SCIRun scripts running SCIRun -E in bash were initially not working despite SCIRun building fine and all the manual nets working. The script nets and manual nets are in theory the same except for paths etc. Ultimately trashing the /SCIRun folder containing "on-the-fly-libs" and "tmp" in entirety and then deleting ".scrirunrc" and letting SCIRun regenerate both allowed the scripts to run. Note this is not in the SCIRun svn directory such as "/trunk" etc, but created the first time you run SCIRun, usually created in your ~/ directory. This should not be an issue if you have never run SCIRun on a machine before, but might be if you have prior versions.
		+
		+	Simply deleting and regenerating "on-the-fly-libs" and ".scirunrc did" not work. The "SCIRun folder", then ".scirunrc" needed to both be deleted and then SCIRun run. I am not sure why the scripts are more sensitive to this but with some builds you might need to trash these to run SCIRun -E with scripts, despite it working just fine in the standard manual situation for which SCIRun is most typically used. I have also not seen it on other machines. A hint would be if it tries to update ".scirunrc" everytime a new SCIRun is opened in the script.