[ecco-support] [EXTERNAL] grid_load.m

Ivana Cerovecki icerovecki at ucsd.edu
Sun May 3 19:02:16 EDT 2020


Hi Gael,

thank you so very much for your help; everything works fine with
 normal nctiles_grid/ folder  <https://doi.org/10.7910/DVN/H8W5VW>


Before I downloaded the grid from
https://ecco.jpl.nasa.gov/drive/files/Version4/Release4/nctiles_grid

and that was my problem. It would help users to have a clear instructions
which grid files to use;
thank you so very much for your prompt help - I spent quite a lot of time
trying to modify scripts to make them work and in the end I just gave
up.....
Cheers,
Ivana





On Sun, May 3, 2020 at 2:30 AM Gael Forget <gforget at mit.edu> wrote:

> Hi Ivana,
>
> 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. (full support? Now I
> am starting to wonder...)
>
> Doesn't everything work if you use the normal nctiles_grid/ folder
> <https://doi.org/10.7910/DVN/H8W5VW>with the up to date gcmfaces code
> (v0.1.5 ; with DOI 10.5281/zenodo.3606908) ?
>
> I just posted a reference to this public email thread from support to
> GitHub @ https://github.com/MITgcm/gcmfaces/issues/9
>
> Ou and myself had been discussing reformatting issues a bit over there.
> Please don’t hesitate to add comments to that thread on GitHub 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.
>
> Dear Ou,
>
> 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.
>
> Could you guys at JPL please clarify a few things for us:
>
> - why and when does one need to worry about using either the refomated
> version of nctiles_grid or the original?
> - why and when does one need to worry about using either new chunked
> version (ECCO-GRID_*.nc) vs or the new ECCO-GRID.nc?
> - Were any modifications made to the actual grid variables (hfacc etc)
> that users need to be aware of / should not overlook?
> - why and how did we change various naming conventions for variables &
> dimensions, and where is the documentation of these changes?
>
> 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, 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.
>
> 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 (con)current software
> version, right?
>
> 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 the recent reformatings. I have not
> looked at UT’s servers but assume they're synced with JPL's
>
> 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 returning or new users.
>
> 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.
>
> Should we aim to do something like that?
>
> Cheers,
> Gael
>
> 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!
>
>
> On May 2, 2020, at 8:25 PM, Ivana Cerovecki <icerovecki at ucsd.edu> wrote:
>
> Hi Gael,
>
> I am using the version that I downloaded from
> https://github.com/MITgcm/gcmfaces
>
> and grid data that I downloaded from
> https://ecco.jpl.nasa.gov/drive/files/Version4/Release4/nctiles_grid
>
> and here is my error message; maybe I am not using the most up to date
> version
> of the package???
>
> So looking at the error message, grid_load is looking for *GRID.0001.nc
> <http://grid.0001.nc/>* and grid files I download are called
> *ECCO-GRID_00.nc *etc.
>
> Thank you so much for your help, it would be great to have this sorted out,
> cheers,
> Ivana
>
> <Image 5-2-20 at 5.17 PM.jpg>
>
>
>
> On Sat, May 2, 2020 at 4:38 PM MIT <gforget at mit.edu> wrote:
>
>> Current version of gcmfaces should support both. Are you using the latest
>> version from GitHub?
>>
>> Sent from my iPhone
>>
>> On May 2, 2020, at 6:50 PM, Ivana Cerovecki <icerovecki at ucsd.edu> wrote:
>>
>> 
>> Hi Ian,
>>
>> thanks so much, that would be great!
>> Ivana
>>
>>
>>
>>
>> On Sat, May 2, 2020 at 3:16 PM Fenty, Ian G (US 329C) <
>> ian.fenty at jpl.nasa.gov> wrote:
>>
>>> Hi Ivana,
>>>
>>> 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.
>>>
>>> Ian
>>>
>>>
>>> On 5/2/20, 3:12 PM, "ecco-support-bounces at mit.edu on behalf of Ivana
>>> Cerovecki" <ecco-support-bounces at mit.edu on behalf of
>>> icerovecki at ucsd.edu> wrote:
>>>
>>>     Hi guys,
>>>
>>>     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
>>>      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.
>>>
>>>
>>>     Can somebody let me know where can I find a version of grid_load.m
>>> that reads the ECCO4v4 grid?
>>>
>>>
>>>     I would very much appreciate your help,
>>>     thank you kindly,
>>>     Ivana
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> ecco-support mailing list
>>> ecco-support at mit.edu
>>>
>>> https://urldefense.com/v3/__http://mailman.mit.edu/mailman/listinfo/ecco-support__;!!Mih3wA!XiV_R0LxnNUfWeofTWSkPWRazYOWR6hBZlmJQdZsCYXs_-eWvoTGjpqqx0lqGOvW0w$
>>>
>>>
>> _______________________________________________
>> ecco-support mailing list
>> ecco-support at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/ecco-support
>> <https://urldefense.com/v3/__http://mailman.mit.edu/mailman/listinfo/ecco-support__;!!Mih3wA!W44BO_9uMTQMGxkTrCXwr1__HqNdzmxCjHZTl6vZKQwSYa3mCsqbDr3JgTVMXPP9zA$>
>>
>> _______________________________________________
>> ecco-support mailing list
>> ecco-support at mit.edu
>>
>> https://urldefense.com/v3/__http://mailman.mit.edu/mailman/listinfo/ecco-support__;!!Mih3wA!W44BO_9uMTQMGxkTrCXwr1__HqNdzmxCjHZTl6vZKQwSYa3mCsqbDr3JgTVMXPP9zA$
>>
>>
> _______________________________________________
> ecco-support mailing list
> ecco-support at mit.edu
> http://mailman.mit.edu/mailman/listinfo/ecco-support
>
>
> _______________________________________________
> ecco-support mailing list
> ecco-support at mit.edu
> http://mailman.mit.edu/mailman/listinfo/ecco-support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/ecco-support/attachments/20200503/88108d6b/attachment-0001.html


More information about the ecco-support mailing list