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.
#1838 (Modifications to remove XIOS1 from dev_merge_2016) – NEMO

Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#1838 closed Enhancement (fixed)

Modifications to remove XIOS1 from dev_merge_2016

Reported by: timgraham Owned by: timgraham
Priority: low Milestone:
Component: OCE Version: trunk
Severity: Keywords:



It has been agreed that XIOS1.0 should be removed from the dev_merge_2016 before it is put back onto the trunk. This ticket documents the necessary changes


1) key_xios2 removed from code (iom.F90) only keeping the xios2 version of the code
2) the xml files from CONFIG/SHARED/ForXIOS2 have been moved to CONFIG/SHARED
3) SETTE/ has been modified to include field_def_nemo-*.xml files from CONFIG/SHARED directory and other minor changes for XIOS2
4) All configs (except SAS_BIPER) have been modified to use the new field_def files split by component and a context_nemo.xml file

Commit History (1)


#1838 - Changes to remove XIOS1.0

Change History (5)

comment:1 Changed 7 years ago by timgraham

Also have to modify TOOLS/COMPILE/ so that the correct xml files are copied into the EXE_DIR.

comment:2 Changed 7 years ago by timgraham

As an extra change I've commented out a section of TOOLS/COMPILE/ that deletes the oasis linking flags if you are not using key_oasis (e.g. -lmct). This allows us to have one installation of XIOS on each machine compiled with OASIS for use in forced or coupled models. If oasis isn't inst installed on a machine then they shouldn't be in the ARCH file.

comment:3 Changed 7 years ago by timgraham

Committed at r7635.

NB: ARCH files need to be updated to point to your XIOS2.0 installation

comment:4 Changed 7 years ago by timgraham

  • Resolution set to fixed
  • Status changed from new to closed

comment:5 Changed 7 years ago by nemo

  • Keywords dev_merge_2016 removed
Note: See TracTickets for help on using tickets.