<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Damien,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">“Geometry-weighted” means a variable is weighted by the fraction of a grid cell in vertical which is wet, namely hFacC, hFacW, or hFacS in the model. They are unitless, ranging from 0 to 1 for a fully dry and wet point and in between for
partial cells. “Geometry-weighted” replaces “Mass-weighted” that was used in older versions, as the weighting is not in mass unit and therefore we decided to use “Geometry Mass-weighted” instead.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">EVEL, NVEL, and WVELMASS are the E-W, N-S, and bottom-up 3D velocity fields. WVELMASS is just an alias of WVEL. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Cheers,<o:p></o:p></p>
<p class="MsoNormal">Ou<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black"><ecco-support-bounces@mit.edu> on behalf of ddesbruy <Damien.Desbruyeres@ifremer.fr><br>
<b>Reply-To: </b>"ECCO support list, wider membership" <ecco-support@mit.edu><br>
<b>Date: </b>Thursday, October 1, 2020 at 6:44 AM<br>
<b>To: </b>"ecco-support@mit.edu" <ecco-support@mit.edu><br>
<b>Subject: </b>[EXTERNAL] [ecco-support] Question on ECCO velocity variables<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p>Dear ECCO team,<o:p></o:p></p>
<p>I have a quick question regarding the ECCO interpolated velocity fields (Version 4 Release 4, interp_monthly).<o:p></o:p></p>
<p>What does "geometry-weighted" exactly mean ? I have also found some other mentions of "mass-weighted" velocities in older versions. I am not entirely sure to what they correspond (in particular when considering the regular interpolated fields).<o:p></o:p></p>
<p>My aim is to use the north-south, east-west, bottom-up 3D velocity fields. I have considered using EVEL, NVEL, and WVELMASS (there is no corresponding WVEL) and I just want to make sure that these are the variables to use.<o:p></o:p></p>
<p>Many thanks in advance for your reply,<o:p></o:p></p>
<p>Damien<o:p></o:p></p>
</div>
</body>
</html>