[mpas-developers] suggestion for flag to avoid initial output file

Michael Duda duda at ucar.edu
Thu Mar 15 11:16:21 MDT 2012


Hi, Mark.

I think the ability to avoid the initial output write would be 
generally useful; would the proposed changes be applied to all
cores, or just the ocean core?

Michael


On Wed, Mar 14, 2012 at 03:19:05PM -0600, Mark Petersen wrote:
> mpas developers,
> 
> Now that we are beginning large high-rez runs, I would like to suggest 
> adding the flag:
> 
> &io
> ...
>     config_write_initial_output = .true.
> /
> 
> where .true. is default, and if .false., the code would not write an 
> output file upon start-up.  There is no need to do this when restarting 
> from a continued run, and it is useful to avoid initial i/o when 
> debugging these large runs.  I would like to ask for feedback on this, 
> since it involves the driver.  See details below.
> 
> Mark
> 
> *******************************************
> 
> This flag would turn off the lines
> 
>        if(config_frames_per_outfile > 0) then
>           call mpas_output_state_init(output_obj, domain, "OUTPUT", 
> trim(timeStamp))
>        else
>           call mpas_output_state_init(output_obj, domain, "OUTPUT")
>        end if
> 
> in mpas_subdriver.F
> 
> and the first
>         call ocn_write_output_frame(output_obj, output_frame, domain)
> before timestepping begins in an individual core,
> 
> and
>                 call mpas_output_state_finalize(output_obj, domain % dminfo)
> the first time it is called in a timestep in each core.
> 
> 
> _______________________________________________
> mpas-developers mailing list
> mpas-developers at mailman.ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/mpas-developers


More information about the mpas-developers mailing list