[MITgcm-support] using ECCOv4 exf inputs with a different model
ryan.abernathey at gmail.com
Thu May 25 11:25:06 EDT 2017
On Thu, May 25, 2017 at 11:15 AM, Menemenlis, Dimitris (329C) <
Dimitris.Menemenlis at jpl.nasa.gov> wrote:
> One would have to rotate/interpolate to a regular latitude/longitude grid
> (the most flexible approach) or to the specific grid that you want to drive.
It seems like a considerable waste of disk space to interpolate a coarse
resolution dataset to much higher resolution just so the model can read it.
Especially with 6-hourly forcing fields!
> I think this is of sufficiently general interest so that we could ask Ou
> or Hong to produce such forcing fields.
I am certainly very supportive of this suggestion! I'm sure that I am not
the only one who would be happy to have a high-quality "standard" exf
dataset on a lat-lon grid with which to force a global model.
> If your domain is between 70S and 56N, all one has to do is to get rid of
> the Northern polar cap and Southern tripolar grid.
Unfortunately not the case for me.
> Dimitris Menemenlis
> > On May 25, 2017, at 8:00 AM, Ryan Abernathey <ryan.abernathey at gmail.com>
> > Hello,
> > I would like to use the exf input forcing dataset produced by Gael for
> ECCOv4 (e.g. ECCO_v4_r2/forcing_baseline2/eccov4r2_rain_2010.data, etc.)
> with a different model with a different grid (llc1080).
> > My current understanding is that this is basically impossible because
> the ECCOv4 inputs are already interpolated to the llc90 grid, rather than a
> regular lat lon grid.
> > Am I right? Is there a workaround?
> > Thanks,
> > Ryan
> > p.s. If anyone can point me to a global, modern set of exf input data
> for MITgcm based on ECMWF, NCEP, or CORE, I would sincerely appreciate it.
> > _______________________________________________
> > MITgcm-support mailing list
> > MITgcm-support at mitgcm.org
> > http://mitgcm.org/mailman/listinfo/mitgcm-support
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MITgcm-support