New URL for NEMO forge!

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
#2743 (Bug: OBS does not seem to take into account the eos used in NEMO) – NEMO

Opened 2 years ago

Last modified 2 years ago

#2743 assigned Bug

Bug: OBS does not seem to take into account the eos used in NEMO

Reported by: mathiot Owned by: systeam
Priority: low Milestone:
Component: TOP Version: trunk
Severity: minor Keywords:



OBS interpolates NEMO T and S onto the obs location. It works from the EN4 data converted into feedback files. These observations are in potential temperature and practical salinity. After looking at the model data interpolated and the code I think the data are not converted to the observations eos and the netcdf attributes of the _Hx variables are missleading.


I see different possible answer to improve this:

  • convert model T and S to observation expected T and S based on model eos and observation eos (function for conversion available in eosbn2 I think)
  • do not convert the model T and S but adapt the netcdf attributes of _Hx variables (not convinced it is in the spirit of the OBS operator)


For solution 1, a call to eos_pt_from_ct can do the job for temperature. For salinity, a function eos_ps_from_sa need to be implemented.

Commit History (0)

(No commits)

Change History (1)

comment:1 Changed 2 years ago by nemo

  • Owner set to systeam
  • Status changed from new to assigned
Note: See TracTickets for help on using tickets.