Re: running long octave simulations

[Steve Thompson]

It seems to me that, yes, octave will keep running the original script.

On a side note, I've been having to do similar stuff (long, remote
runs) and I've found the screen command to be much more flexible than
nohup.

Step 1: log in to remote octave-crunching computer

Step 2: type "screen" at the command line, hit enter

Step 3: do your business (eg, get octave running)

Step 4: close terminal

Step 5: beer, beach, etc

Step 6: after a few hours check in on simulation

  6a: log in to said computer

  6b: type "screen -r"

      You will see a list of active screens, something like:

        There are several suitable screens on:
                17712.pts-3.prospect
                17459.pts-3.prospect
                17857.pts-3.prospect

      meaning there are 3 such screens doing stuff.

  6c: type "screen -r 17712.pts-3.prospect" to reconnect to the
      first one on the list, etc

This can be done as many times as you like.  Sooooo cool.

Steve


On Thu, Jun 19, 2008 at 2:08 PM, Kamaraju S Kusumanchi
<address@hidden> wrote:
> I have a small script which takes couple of hours to run in octave. I run
> the code by invoking
>
> nohup octave -q script1.m &
>
> Say the code takes about 10 hours to complete. Now if script1.m is modified
> during 5th hour and saved to the same file. Will octave be running original
> script1.m or the modified script1.m after the 5th hour? Is it assured that
> octave runs the original script1.m even though it was modified somewhere
> during the run time?
>
> Any ideas?
>
> thanks
> raju
> --
> Kamaraju S Kusumanchi
> http://www.people.cornell.edu/pages/kk288/
> http://malayamaarutham.blogspot.com/
>
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://www.cae.wisc.edu/mailman/listinfo/help-octave
>