<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Ivana,<div class=""><br class=""></div><div class="">Thanks for the clarification and reporting this issue. You have the correct gcmfaces location — presumably you’re using the current version v1.5.0 which has support for the new format. <font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class="">(full support? Now I am starting to wonder...)</span></font><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""> </span></div><div class=""><br class=""></div><div class=""><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">Doesn't everything work if you use the <a href="https://doi.org/10.7910/DVN/H8W5VW" class="">normal nctiles_grid/ folder </a>with the up to date gcmfaces code (v0.1.5 ; with DOI 10.5281/zenodo.3606908) ? </div></div><div class=""><br class=""></div><div class="">I just posted a reference to this public email thread from support to GitHub @ <a href="https://github.com/MITgcm/gcmfaces/issues/9" class="">https://github.com/MITgcm/gcmfaces/issues/9</a> </div><div class=""><br class=""></div><div class="">Ou and myself had been discussing reformatting issues a bit over there. Please don’t hesitate to add comments to that thread on <span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">GitHub</span> or a new one if you’d like. It helps make everyone aware of issues that potentially remain to be fixed. Thanks for having reported this issue to ecco-support btw.</div><div class=""><br class=""></div><div class="">Dear Ou,</div><div class=""><div class=""><br class=""></div><div class=""><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">I don’t immediately understand / recall why there was a need for a new grid folder. My guess is that it may have had to do with overly specific python libraries not being able to handle the standard nctiles_grid or something like that but I am nit sure.</div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><br class=""></div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">Could you guys at JPL please clarify a few things for us:</div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><br class=""></div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">- why and when does one need to worry about using either the refomated version of nctiles_grid or the original?</div></div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">- why and when does one need to worry about using either new chunked version (ECCO-GRID_*.nc) vs or the new ECCO-GRID.nc?</div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">- Were any modifications made to the actual grid variables (hfacc etc) that users need to be aware of / should not overlook?</div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">- why and how did we change various naming conventions for variables & dimensions, and where is the documentation of these changes?</div><div class=""><br class=""></div><div class="">Sorry if I overlooked some of the details up to this point but I feel that users should not be left wondering about such things, and that’s why the embedded READMEs are so important in my mind. As I look more closely at the READMEs currently in the release4 folder, <font color="#000000" class="">I am starting to be more and more concerned that issues like Ivana’s might emerge for either new or returning users more in the future.</font></div><div class=""><div class=""><br class=""></div></div><div class="">One obvious issue is that READMEs across the Release4 folder (at least some of them) seem to incorrectly point users to old versions of gcmfaces found in the MIT `opendap/ecco_for_las/` server. The READMEs should instead point to the official gcmfaces repository & the <span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">(con)current software version, right?</span></div><div class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><br class=""></span></div><div class="">But more generally, the READMEs currently in the JPL release4/ folder might be creating sources of potential confusion or even frustration for returning or new ECCOv4 users due to<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""> the recent reformatings. I </span><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class="">have not looked at UT’s servers but assume they're synced with JPL's</span></font><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""> </span></div><div class=""><br class=""></div><div class="">My sense is that all of the READMEs (probably from release1 to release4 and beyond) might now need to point users to a webpage with details about the reformatting and its implications <font color="#000000" class="">returning or new users. </font></div><div class=""><font color="#000000" class=""><br class=""></font></div><div class=""><font color="#000000" class="">I might be able to update the ones on MIT's ftp site but will need to know which webpage to point to for details about the reformatting (a version controlled GitHub page might be best so we don’t have to go back to the READMEs later e.g. if you decided to reformat again at some point) and someone else will need to take care of the JPL and UT server sides.</font></div><div class=""><br class=""></div><div class="">Should we aim to do something like that?</div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Gael</div><div class=""><br class=""></div><div class="">Ps. Sorry for so much text to read … I am rather confused by this reformatting stuff myself I am afraid but hopefully this is helpul!</div><div class=""><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class="">On May 2, 2020, at 8:25 PM, Ivana Cerovecki <<a href="mailto:icerovecki@ucsd.edu" class="">icerovecki@ucsd.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">Hi Gael,<div class=""><br class=""></div><div class="">I am using the version that I downloaded from</div><div class=""><a href="https://github.com/MITgcm/gcmfaces" target="_blank" class="">https://github.com/MITgcm/gcmfaces</a><br class=""></div><div class=""><br class=""></div><div class="">and grid data that I downloaded from</div><div class=""><a href="https://ecco.jpl.nasa.gov/drive/files/Version4/Release4/nctiles_grid" target="_blank" class="">https://ecco.jpl.nasa.gov/drive/files/Version4/Release4/nctiles_grid</a><br class=""></div><div class=""><br class=""></div><div class="">and here is my error message; maybe I am not using the most up to date version</div><div class="">of the package???</div><div class=""><br class=""></div><div class="">So looking at the error message, grid_load is looking for<span class="Apple-converted-space"> </span><b class=""><a href="http://grid.0001.nc/" class="">GRID.0001.nc</a></b><span class="Apple-converted-space"> </span>and grid files I download are called</div><div class=""><b class="">ECCO-GRID_00.nc<span class="Apple-converted-space"> </span></b>etc. </div><div class=""><br class=""></div><div class="">Thank you so much for your help, it would be great to have this sorted out,</div><div class="">cheers,</div><div class="">Ivana</div><div class=""><br class=""></div><div class=""><div class=""><span id="cid:ii_k9qb7gy00"><Image 5-2-20 at 5.17 PM.jpg></span><br class=""></div></div><div class=""><br class=""></div><div class=""><br class=""></div></div><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div class="gmail_quote" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div dir="ltr" class="gmail_attr">On Sat, May 2, 2020 at 4:38 PM MIT <<a href="mailto:gforget@mit.edu" target="_blank" class="">gforget@mit.edu</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div dir="auto" class="">Current version of gcmfaces should support both. Are you using the latest version from GitHub?<br class=""><br class=""><div dir="ltr" class="">Sent from my iPhone</div><div dir="ltr" class=""><br class=""><blockquote type="cite" class="">On May 2, 2020, at 6:50 PM, Ivana Cerovecki <<a href="mailto:icerovecki@ucsd.edu" target="_blank" class="">icerovecki@ucsd.edu</a>> wrote:<br class=""><br class=""></blockquote></div><blockquote type="cite" class=""><div dir="ltr" class=""><div dir="ltr" class="">Hi Ian,<div class=""><br class=""></div><div class="">thanks so much, that would be great! </div><div class="">Ivana</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, May 2, 2020 at 3:16 PM Fenty, Ian G (US 329C) <<a href="mailto:ian.fenty@jpl.nasa.gov" target="_blank" class="">ian.fenty@jpl.nasa.gov</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;">Hi Ivana,<br class=""><br class="">We updated the formatting of the netcdf files for V4 output. Ou Wang (cc'd) wrote a wrapper for gcmfaces to handle the updated format. He can point you to where it is and hopefully some directions on how to use it.<br class=""><br class="">Ian<br class=""><br class=""><br class="">On 5/2/20, 3:12 PM, "<a href="mailto:ecco-support-bounces@mit.edu" target="_blank" class="">ecco-support-bounces@mit.edu</a><span class="Apple-converted-space"> </span>on behalf of Ivana Cerovecki" <<a href="mailto:ecco-support-bounces@mit.edu" target="_blank" class="">ecco-support-bounces@mit.edu</a><span class="Apple-converted-space"> </span>on behalf of<span class="Apple-converted-space"> </span><a href="mailto:icerovecki@ucsd.edu" target="_blank" class="">icerovecki@ucsd.edu</a>> wrote:<br class=""><br class=""> <span class="Apple-converted-space"> </span>Hi guys,<br class=""><br class=""> <span class="Apple-converted-space"> </span>I will very much appreciate if somebody can help me: I am interested in the T and S budgets in the Southern Ocean. Using gcmfaces, I was able to read the grid and close the budgets using ECCO4v3 data as input without<br class=""> any problems. Now I would like to do the same analysis using gcmfaces and ECCO4v4 output, but I get stuck right away when I try to read the ECCO4v4 grid using grid_load.m.<br class=""><br class=""><br class=""> <span class="Apple-converted-space"> </span>Can somebody let me know where can I find a version of grid_load.m that reads the ECCO4v4 grid?<span class="Apple-converted-space"> </span><br class=""><br class=""><br class=""> <span class="Apple-converted-space"> </span>I would very much appreciate your help,<br class=""> <span class="Apple-converted-space"> </span>thank you kindly,<br class=""> <span class="Apple-converted-space"> </span>Ivana<br class=""><br class=""><br class=""><br class=""><br class="">_______________________________________________<br class="">ecco-support mailing list<br class=""><a href="mailto:ecco-support@mit.edu" target="_blank" class="">ecco-support@mit.edu</a><br class=""><a href="https://urldefense.com/v3/__http://mailman.mit.edu/mailman/listinfo/ecco-support__;!!Mih3wA!XiV_R0LxnNUfWeofTWSkPWRazYOWR6hBZlmJQdZsCYXs_-eWvoTGjpqqx0lqGOvW0w$" rel="noreferrer" target="_blank" class="">https://urldefense.com/v3/__http://mailman.mit.edu/mailman/listinfo/ecco-support__;!!Mih3wA!XiV_R0LxnNUfWeofTWSkPWRazYOWR6hBZlmJQdZsCYXs_-eWvoTGjpqqx0lqGOvW0w$</a><span class="Apple-converted-space"> </span><br class=""></blockquote></div><span class="">_______________________________________________</span><br class=""><span class="">ecco-support mailing list</span><br class=""><span class=""><a href="mailto:ecco-support@mit.edu" target="_blank" class="">ecco-support@mit.edu</a></span><br class=""><span class=""><a href="https://urldefense.com/v3/__http://mailman.mit.edu/mailman/listinfo/ecco-support__;!!Mih3wA!W44BO_9uMTQMGxkTrCXwr1__HqNdzmxCjHZTl6vZKQwSYa3mCsqbDr3JgTVMXPP9zA$" target="_blank" class="">http://mailman.mit.edu/mailman/listinfo/ecco-support</a></span><br class=""></div></blockquote></div>_______________________________________________<br class="">ecco-support mailing list<br class=""><a href="mailto:ecco-support@mit.edu" target="_blank" class="">ecco-support@mit.edu</a><br class=""><a href="https://urldefense.com/v3/__http://mailman.mit.edu/mailman/listinfo/ecco-support__;!!Mih3wA!W44BO_9uMTQMGxkTrCXwr1__HqNdzmxCjHZTl6vZKQwSYa3mCsqbDr3JgTVMXPP9zA$" rel="noreferrer" target="_blank" class="">https://urldefense.com/v3/__http://mailman.mit.edu/mailman/listinfo/ecco-support__;!!Mih3wA!W44BO_9uMTQMGxkTrCXwr1__HqNdzmxCjHZTl6vZKQwSYa3mCsqbDr3JgTVMXPP9zA$</a><span class="Apple-converted-space"> </span><br class=""></blockquote></div><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">_______________________________________________</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">ecco-support mailing list</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><a href="mailto:ecco-support@mit.edu" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">ecco-support@mit.edu</a><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><a href="http://mailman.mit.edu/mailman/listinfo/ecco-support" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">http://mailman.mit.edu/mailman/listinfo/ecco-support</a></div></blockquote></div><br class=""></div></body></html>