<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Is there a reason that [core] needs to be generic? We could have more than one sea ice option, for instance, in which case it would make sense to use 'cice' for LANL's sea ice component.<div>e</div><div><br><div><div>On Sep 29, 2011, at 10:56 AM, Xylar Asay-Davis wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi Bill,<br><br>I definitely don't like the ice/glc convention used in CESM. As you know, I'm in favor of long-winded, so landice works for me.<br><br>-Xylar<br><br>On 9/29/11 10:52 AM, William Lipscomb wrote:<br><blockquote type="cite">Hi all,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I like this general naming scheme. I just wonder how we should<br></blockquote><blockquote type="cite">designate land ice as opposed to sea ice. The current CESM convention<br></blockquote><blockquote type="cite">is that sea ice is "ice" and land ice is "glc". Should we use that<br></blockquote><blockquote type="cite">convention, or should we switch to "landice" and "seaice" for greater<br></blockquote><blockquote type="cite">clarity? (Although "landice" is kind of long-winded, I don't think<br></blockquote><blockquote type="cite">"lice" is a good option.)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Cheers,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Bill<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Sep 29, 2011, at 10:44 AM, Doug Jacobsen wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">Hi All,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Just so you know, we have decided on a formal naming scheme for<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">modules.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">This naming scheme is chosen to try and keep all portions of mpas<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">named<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">uniformly. The generic format of this new naming scheme is as follows.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">[model]_[core]_[module_name].F<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Where [model] is going to be mpas for almost every source file. This<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">choice<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">is to help reduce potential namespace conflicts from the use of<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">module.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">[core] represents the core the code belongs to. For ocean, we are<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">using ocn<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">for [core], and atmosphere might use atmos for [core]. The choice<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">here would<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">be left up to the group developing the core to decide on.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">[module_name] is left ambiguous, and is meant to represent the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">content of<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">the individual source file.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">As an example, module_time_integration.F from the ocean core would be<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">transformed using this naming scheme to mpas_ocn_time_integration.F.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Also, all letter should be lower case in this naming scheme, to keep<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">file<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">name uniform looking.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I have also provided a simple bash script you can use to migrate<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">file names<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">to the new format, and update the Makefile for the core. I would read<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">through it and edit it if you need to before running it, but it<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">should give<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">a simple example of how to do this.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">If there are any questions or comments on this choice please let me<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">know,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">but I am going to be implementing this across our ocean core. Please<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">use<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">this naming scheme when creating new modules.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Thank you!<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Doug<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><transform.sh>_______________________________________________<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">mpas-developers mailing list<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="mailto:mpas-developers@mailman.ucar.edu">mpas-developers@mailman.ucar.edu</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://mailman.ucar.edu/mailman/listinfo/mpas-developers">http://mailman.ucar.edu/mailman/listinfo/mpas-developers</a><br></blockquote></blockquote><blockquote type="cite">*******************************************************************************<br></blockquote><blockquote type="cite">William H. Lipscomb<span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>E-mail: <a href="mailto:lipscomb@lanl.gov">lipscomb@lanl.gov</a><br></blockquote><blockquote type="cite">Los Alamos National Laboratory<span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>Phone: (505) 667-0395<br></blockquote><blockquote type="cite">Group T-3, Mail Stop B216<span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>Fax: (505) 665-5926<br></blockquote><blockquote type="cite">Los Alamos, NM 87545<br></blockquote><blockquote type="cite">*******************************************************************************<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">mpas-developers mailing list<br></blockquote><blockquote type="cite"><a href="mailto:mpas-developers@mailman.ucar.edu">mpas-developers@mailman.ucar.edu</a><br></blockquote><blockquote type="cite"><a href="http://mailman.ucar.edu/mailman/listinfo/mpas-developers">http://mailman.ucar.edu/mailman/listinfo/mpas-developers</a><br></blockquote><br><br>-- <br><br>***********************<br>Xylar S. Asay-Davis<br>E-mail: <a href="mailto:xylar@lanl.gov">xylar@lanl.gov</a><br>Phone: (505) 606-0025<br>Fax: (505) 665-2659<br>CNLS, MS B258<br>Los Alamos National Laboratory<br>Los Alamos, NM 87545<br>***********************<br><br><br></div></blockquote></div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>TSPA/DUSA EARTH<br>Correspondence<br><br> o <br> o Elizabeth Hunke <br> o T-3 Fluid Dynamics and Solid Mechanics Group <br> o MS-B216 <span></span> <span></span> <br> o Los Alamos National Laboratory <br> o Los Alamos, NM 87545 <span></span> <br> o office 505 665 9852 <br> o fax 505 665 5926 <br> o <a href="mailto:eclare@lanl.gov">eclare@lanl.gov</a> <br> o <a href="http://climate.lanl.gov/">http://climate.lanl.gov</a> <span></span> <span></span> <span></span> </div></div></span></div></span> </div><br></div></body></html>