nrniv window

[JimH]

For the life of me I can't figure out how to prevent the nrniv.exe window from showing. Is it possible to run the executable as a hidden process? I'm running simulations using multiple calls to the executable and the constant popping up of the windows takes over my computer. Thanks!

Jim

[ted]

It would be more efficient to use bulletin-board style parallelization instead. That would not only open just one NEURON terminal, but would allow you to use all of your PC's cores. Since you're using MSWin, you already have MPI (is packaged with NEURON's installer for MSWin), so getting this going should be dirt simple. You can read about running "embarrassingly parallel" simulations with NEURON in the Programmer's Reference
http://www.neuron.yale.edu/neuron/static/docs/help/neuron/neuron/classes/parcon.html
and here's an exercise from the NEURON summer course that might help you get started:
http://www.neuron.yale.edu/ftp/ted/neuron/bulletin_board_parallelization.zip

[hines]

nrniv.exe does not, itself, pop up a terminal window. That must be a consequence of the way you are launching it. I presume you are using the cygwin version
where there is generally an rxvt window. From a command window, try executing nrniv and I believe you will see nothing because there is no cygwin compatible
stdin or stdout. So it exits immediately because stdin is at end of file. But if you launch
nrniv -c 'continue_dialog("hello")'
then it will wait for your button press before exiting. However, notice it did not start a terminal window.
A fragment of code that one could use to exhibit the problem would be helpful.

[JimH]

It is actually through a system call in Matlab. I've nearly finished a process to support stdin/stdout back and forth communication but I need some results ASAP and all I was getting was flashing screens as a new window would pop up and close.

I added:

start /B /WAIT and now it seems to be working exactly as desired.

Thanks for the note on the parallel computation approach, although I don't have that many simulations to run yet and I need a bit of back and forth communication for everything to work.

This is an extension of this topic from a while back, although I've changed a few things since then:
https://www.neuron.yale.edu/phpBB2/viewtopic.php?t=996