[mpas-developers] config_write_initial_output option

[Michael Duda]

Mark,

I think this would be a useful option, though as currently implemented
in the branch, I'm not sure that it would work as expected when there
are multiple history frames written to the same file. I've also been
looking at implementing this, and I have some changes to the IO layer to
support appending time frames to an existing file that I think might be
useful for a completely general implementation of the
write_initial_output functionality. I can send these changes to you to
take a look at, or I can merge them into the branch; just let me know.

Michael


On Thu, May 10, 2012 at 01:06:15PM -0600, Mark Petersen wrote:
> MPAS Developers,
> 
> I added the flag config_write_initial_output to all cores in the branch 
> ocean_projects/first_output_optional.  It simply controls if an output 
> file is written upon start-up.  The ocean core needs this for our large 
> runs, to save i/o and for simply time-averaged variables.  Because the 
> first file initialized in driver/mpas_subdriver.F, it affects all 
> cores.  In addition, it seems like a useful flag for everyone.
> 
> I tested by compiling all four cores, and running with the ocean core.  
> Could someone run a little test with the atmospheric cores, switching 
> this flag on and off, and make sure it works as expected?  When I hear 
> back, I will merge the branch to the trunk.
> 
> Thanks,
> Mark
> _______________________________________________
> mpas-developers mailing list
> mpas-developers at mailman.ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/mpas-developers