SCIRun User Mailing List

Text archives Help

[SCIRUN-USERS] SCIRun in headless mode

Chronological Thread 
  • From: <>
  • To: " " <>
  • Subject: [SCIRUN-USERS] SCIRun in headless mode
  • Date: Wed, 17 Aug 2016 17:27:29 +0100
  • Importance: normal


Dear All,


I started using SCIRun 5.0 in the scripting mode and made some observation. The aim is to run SCIRun 5.0 headless on an HPC. My observations are most like due to my limited knowledge of SCIRun.


To use SCIRun on the cluster, I need to compile it there. However, the QT4 version installed on the cluster is rather old. Therefore, I compiled a recent version separately. The path to the new QT4 is then supplied the Cmake script of the Superbuild. However,  when generating the Cmake files, it turns out that new projects are generated in 'bin/SCIRun/cpm'. These projects do not take on the path to the manually specified QT4, and as a result fail. The good thing is that the problem can be avoided when compiling headless only.


The same projects in 'bin/SCIRun/cpm/' seam to have a different compiler path. If in the Superbuild project 'gcc' is specified as compiler, then some of the projects in given folder use 'cc' as  compiler. I am not sure, whether Cmake has two different variables for both compiler but I suspect it is just a different configuration. Currently, I fix this problem with a symbolic link to gcc.


After compiling SCIRun in headless mode, I found a few question regarding the execution of SCIRun.

1.       Is it possible to specify the number of CPU to use? A node on the HPC might have more CPUs then I applied for. So it would be good if SCIRun would use a set number of CPUs, only.

2.       Is it possible to save a network from the interactive console, when compiled in headless mode? The 'scirun_save_network' command seams not to be existing and causes errors.

3.       Is the 'scirun_execute_all' command supposed to return immediately? Meaning before the execution is completed. If so, is there a way of synchronization with the execution?

4.       After running SCIRun in verbose mode and then exiting, it seams as everything in the memory is printed to screen. A large amount of nonsense is printed to the screen.

5.       When running SCIRun with the combination '-s -I' , the quite command results in an endless output of the string "scirun>"

6.       Is it possible to use SCIRun directly form Python?


These are my observations, so far. I would be very thank full for help with any of the questions.






Archive powered by MHonArc 2.6.18.

Top of page