It seems to run fine using the cold start option. The run crashed after a period of time, but I think it was due to memory limitation on the machine I'm using for testing.
When you say a file mismatch, do you mean the cpio archive of initial conditions are big-endian rather than little-endian? I just tried another run, this time with cpio doing byte swapping while reading in from the archive. The run ended quickly with a floating point exception that I haven't yet tracked down. The bgrid_prog_var.res file that was created still doesn't contain the "restart format" string. Thanks, Norm On 11 Jun., V. Balaji wrote: > Norm Wood writes: > > > Has anyone else run into a problem reading the restart > > version number from the restart file? > > > > This is occuring with the solo code compiled for the > > bgrid core using pgf90 under Linux. > > > > When executed, (an initial run, not a restart run) the run > > aborts with a message from the open_prog_var_file() subroutine > > in bgrid_prog_var.f90: > > > > FATAL from PE 1: bgrid_prog_var_mod: > > problem extracting restart version number > > > > This subroutine searches for the string "restart format" in > > the restart file but doesn't find it and issues a FATAL call > > to mpp_error(). The restart file exists (bgrid_prog_var.res), > > but strings shows no occurrence of "restart format" in the file. > > It's possible there's a file mismatch. Have you tried using the > cold-start option of bgrid_solo? It is capable of generating all > its own input data, and should not need bgrid_prog_var.res. _______________________________________________________________ Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Fms-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fms-users
