[mesa-users] MesaScript/Ruby - problem with an automated execution of MESA
Jakub Ostrowski
ostrowski at astro.uni.wroc.pl
Fri Nov 7 11:55:50 EST 2014
Thank you for the suggestions. While trying them I realised that MESA stopped not the Ruby but I haven’t spotted it (many times!) due to a lot of errors printed by Ruby’s interpreter. When it was fixed the script worked perfectly.
So I’m sorry guys for bothering you with basically non-existing problem. Shame on me.
Cheers,
Jakub
> On 07 Nov 2014, at 17:45, Willie Strickland <cwskas at gmail.com> wrote:
>
> Hello Jakub,
>
> Seems like there is probably a better way, but you could have a loop that pauses some time, then checks for the presence of a file, say .finished, and continues when it finds that file.
>
> You then set rn to touch that file as the last step. You would also want to have your ruby script delete the file when it continued.
>
> Willie
>
>
> On Nov 7, 2014, at 10:23 AM, Jakub Ostrowski <ostrowski at astro.uni.wroc.pl> wrote:
>
>> The problem is that after the ./rn command the script shortly progresses to the next command and everything dies. Does someone know how to force the script to wait until MESA ultimately finishes its current run?
>
More information about the Mesa-users
mailing list