<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="+1"><tt>See embedded opinions...<br>
<br>
</tt></font>
<div class="moz-cite-prefix">On 10/22/13 12:59 PM, Tim Hoar wrote:<br>
</div>
<blockquote cite="mid:77A451E3-3403-4A04-81C3-831F746F7F1F@ucar.edu"
type="cite">
<pre wrap="">
Functionally, I would like to propose that the shell_scripts directories for each model component have (something like) the following:
CESM1_1_1_setup_inital (pull model states from all over)
CESM1_1_1_setup_pmo (advance a single model state)
CESM1_1_1_setup_hybrid (stage an ensemble from a reference case and carry on)
perfect_model_obs.csh
assimilate.csh</pre>
</blockquote>
Is CESM1_1_1_config missing from this list? Or has it been absorbed
into something else?<br>
It's good to have the model version in the name. If it's useful,
unchanged, for future model versions,<br>
we can just have note in each file saying so.<br>
I like Nancy's proposal for perfect_model{_obs}.csh.<br>
Will st_archive.sh be in here too?<br>
Nitpick; 'initial' instead of 'inital'<br>
<br>
<blockquote cite="mid:77A451E3-3403-4A04-81C3-831F746F7F1F@ucar.edu"
type="cite">
<pre wrap="">
CAM may need additional scripts to provide backward compatibility.
CESM1_1_1_setup_startup (run in perpetual startup mode ...)
assimilate.csh (to manipulate the value of CONTINUE_RUN ...)
Does anyone have an improvement on that? I need to rename the scripts in the CESM directories to be more consistent. This will help the learning curve as well as the documentation.
Does anyone have an opinion about making the names a bit more specific?
perfect_model_obs.csh --> [cam,clm,pop]_perfect_model_obs.csh
assimilate.csh --> [cam,clm,pop]_assimilate.csh</pre>
</blockquote>
I'm in favor of either this, but I'd listen to arguments in favor of
keeping the generic names,<br>
but copying them to new, local names when they might be confused
with sibling scripts for <br>
other components, like when doing multi-component, or coupled
assimilation. <br>
Will people be doing assimilations outside of the CESM framework,
where the generic name<br>
would be slightly more convenient?<br>
<blockquote cite="mid:77A451E3-3403-4A04-81C3-831F746F7F1F@ucar.edu"
type="cite">
<pre wrap="">
Can we call the observations from a perfect model experiment obs_seq.xxxx.perfect instead of
obs_seq.out? Can we reserve the obs_seq.out for 'real' observations?</pre>
</blockquote>
That would be an improvement. <br>
We could also consider 'obs_seq.real' for real obs files that
haven't been assimilated yet.<br>
'Obs_seq.final' seems fine for the output from assimilations. <br>
<blockquote cite="mid:77A451E3-3403-4A04-81C3-831F746F7F1F@ucar.edu"
type="cite">
<pre wrap="">
Now is the time to provide your opinions.
Thanks -- Tim
Tim Hoar, Associate Scientist
National Center for Atmospheric Research
<a class="moz-txt-link-abbreviated" href="mailto:thoar@ucar.edu">thoar@ucar.edu</a>
303.497.1708
_______________________________________________
Dart-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dart-dev@mailman.ucar.edu">Dart-dev@mailman.ucar.edu</a>
<a class="moz-txt-link-freetext" href="http://mailman.ucar.edu/mailman/listinfo/dart-dev">http://mailman.ucar.edu/mailman/listinfo/dart-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>