Difference between revisions of "SCIRun Scripts on SPL Machines"
| 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. | |
| + | |||
| + | 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. | ||
Revision as of 09:58, 2 August 2007
Home < SCIRun Scripts on SPL MachinesHigh-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.
