Since version 3.2, iomput is the NEMO output interface of choice. It has been designed to be simple to use, flexible and efficient. The two main purposes of iomput are: The complete and flexible control of the output files through external XML files adapted by …

2024年12月20日 · These pages are a practical guide explaining how to get started with NEMO and how to utilise some of the more advanced features. For more detailed descriptions of NEMO’s scientific and numerical options, and how these are built into the code, please refer to the Reference manuals here

2023年4月22日 · gdepw_0 refers to the depths of cell interfaces in s-coordinates as in z-coordinates. The only difference being that in z-coordinates, gdepw_0(z,y,x) = gdepw_1d(z) everywhere except at the ocean floor. If you really need the depth of interfaces (the top of layer), you need e3t arrays, the distance between two consecutive interfaces.

2020年11月10日 · This paper describes a new multi-grid approach developed for accelerating the computation of passive tracer transport in the Nucleus for European Modelling of the Ocean (NEMO) ocean circulation model.

iceberg changes ¶ On top of this Merino work has been included. A branch based on NEMO trunk has been developed for futur inclusion into the trunk. The corresponding NEMO tickets are #2494, #2375 and #1900. Tickets #2494 and #2375 are the first step before proper inclusion of …

This example showcases how xnemogcm can compute certain missing metrics (metrics are called scale factors in the NEMO community, and called metrics in the xgcm community). It is thus possible to e.g. compute e3u from e3t. We let the reader refer to the NEMO documentation for the explanation of the scale factors.

In NEMO OGCM, depth are defined with an analytical function and vertical scale factors are defined with its derived function. That’s why: e3t(k) =/ gdepw(k+1) - gdepw(k) AND e3w(k) =/ gdept(k+1) - gdept(k)

Description In z* vertical configuration, NEMO r12377 uses memory to store and update vertical scale factors e3 [P] where P = {t-, u-, v-, w-, f-, uw-, vw-} points at "before", "now" and "after" time steps. This means memory storage 6 x 4D + 1 x 3D tables, memory acces and CPU time for updating 3D scale factors.

For this example, the NEMO output files have already been saved as netCDF with the right coordinate names. The xorca package is designed to open NEMO datasets so they are understandable by xgcm. The xnemogcm does a similar work on idealized configurations. Below are some example of how to make calculations using xgcm.

Three main choices are offered (Fig. 4.5 a to c): -coordinate with full step bathymetry (ln_zco= true), -coordinate with partial step bathymetry (ln_zps= true), or generalized, -coordinate (ln_sco= true). Hybridation of the three main coordinates are available: or coordinate (Fig. 4.5 d and 4.5 e).