New URL for NEMO forge!   http://forge.nemo-ocean.eu

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.
#1655 (SETTE test fails if your installation path contains "SETTE" keyword) – NEMO

Opened 9 years ago

Closed 9 years ago

Last modified 3 years ago

#1655 closed Bug (fixed)

SETTE test fails if your installation path contains "SETTE" keyword

Reported by: mcastril Owned by: nemo
Priority: low Milestone:
Component: OCE Version: v3.6
Severity: Keywords: OPA v3.6
Cc:

Description

Maybe is not a common issue but if you have your test versions in a path containing "SETTE", the script chops the path string and SETTE doesn't run.

For example:

/filesystem/NEMO/TESTS/SETTE/nemo_v3.6/NEMOGCM

It will think that NEMO_DIR is /filesystem/NEMO/TESTS

Commit History (2)

ChangesetAuthorTimeChangeLog
6460lovato2016-04-08T18:00:29+02:00

Move runoff fields time swap in sbcmod (#1703) and change SETTE path definition of MAIN_DIR (#1655)

6459lovato2016-04-08T18:00:11+02:00

Move runoff fields time swap in sbcmod (#1703) and change SETTE path definition of MAIN_DIR (#1655)

Change History (3)

comment:1 Changed 9 years ago by timgraham

It is minor but still quite annoying at times.

I think it can be fixed quite easily by replacing

MAIN_DIR=${SETTE_DIR%/SETTE}

with

echo $(dirname $SETTE_DIR)

in the sette.sh script.

comment:2 Changed 9 years ago by lovato

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

The path to MAIN_DIR was modified as follow 

MAIN_DIR=$(dirname $SETTE_DIR)

and changes were committed in nemo_v3_6_STABLE at r6459
and in the trunk at r6460

comment:3 Changed 3 years ago by nemo

  • Keywords OPA v3.6 added
Note: See TracTickets for help on using tickets.