[Mesa-users] ./re functionality for cluster

Rob Farmer r.j.farmer at uva.nl
Thu Apr 11 03:34:51 EDT 2019


So the ./re script just copies the photo you give it to a file called
restart_photo into the current working directory then it calls ./star,
while ./rn will remove any restart_photo before calling star. So what you
could do is always just call ./star directly (no ./rn or ./re). Then in
your extras_finish_step:

use star_lib
if(mod(s%model_number,s%photo_interval)==0) then
    call star_save_for_restart(s%id,'restart_photo',ierr)
end if

This will then write a photo out with the name restart_photo. The first
time you run a model with ./star there wont be a restart_photo so it'll act
like ./rn. while the second time the restart_photo will exist so calling
./star will act like ./re (without you needing to copy and photos yourself).


On Thu, 11 Apr 2019 at 03:14, amber lauer via Mesa-users <
mesa-users at lists.mesastar.org> wrote:

> Great, thanks. Though, for those attempting it in the future I found it
> easier to just write the restart portion into the batch submission script.
> At least with the aforementioned many jobs structure.
> On Wed, Apr 10, 2019, 5:16 PM Josiah Schwab <jwschwab at ucsc.edu> wrote:
>> 2)Alter re to copy the newest photo to restart_photo via
>>> *cp $(ls -t  | head -1) restart_photo*
>>> and comment out everything above it. However, I almost usually find when
>>> I want to do things like this that it already exists in some form. So I'm
>>> checking with the mailing list.
>> I usually do some variant of this.
>> Josiah
> _______________________________________________
> mesa-users at lists.mesastar.org
> https://lists.mesastar.org/mailman/listinfo/mesa-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20190411/8a0f4209/attachment.html>

More information about the Mesa-users mailing list