<div dir="ltr">Hey Michael,<div><br></div><div>It looks like this field is setup in src/operators/mpas_rbf_interpolation.F and that it is indeed meant to be nCells long. It's also used in src/operators/mpas_vector_reconstruction.F, and the only loop it's in is over nCellsSolve as well. So I think this change is fine.</div>
<div><br></div><div>Thanks,</div><div>Doug</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Feb 28, 2013 at 10:25 AM, Michael Duda <span dir="ltr"><<a href="mailto:duda@ucar.edu" target="_blank">duda@ucar.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi, Folks.<br>
<br>
While trying to track down a problem in our MPAS-A initialization, I<br>
noticed that in the registry files for all cores on the trunk, we have<br>
the cellTangentPlane field dimensioned as ( R3 TWO nEdges ). At least as<br>
far as I can tell -- and as indicated by the name of this field --<br>
cellTangentPlane should be a cell-based field rather than an edge-based<br>
field.<br>
<br>
I'm planning to test our core after switching the dimensions for<br>
cellTangentPlane to ( R3 TWO nCells ), but I thought I'd let everyone<br>
else know about this issue, and perhaps to see whether anyone else<br>
agrees or disagrees with this switch.<br>
<br>
Michael<br>
_______________________________________________<br>
mpas-developers mailing list<br>
<a href="mailto:mpas-developers@mailman.ucar.edu">mpas-developers@mailman.ucar.edu</a><br>
<a href="http://mailman.ucar.edu/mailman/listinfo/mpas-developers" target="_blank">http://mailman.ucar.edu/mailman/listinfo/mpas-developers</a><br>
</blockquote></div><br></div>