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.
prepare_exe_dir.sh in branches/UKMO/dev_r5518_GO6_package/NEMOGCM/SETTE – NEMO

source: branches/UKMO/dev_r5518_GO6_package/NEMOGCM/SETTE/prepare_exe_dir.sh @ 7993

Last change on this file since 7993 was 6487, checked in by davestorkey, 8 years ago

Changes from nemo_v3_6_STABLE_copy branch.
Custom merge into /branches/UKMO/dev_r5518_GO6_package/NEMOGCM: r6237 cf. r5781 of /branches/UKMO/nemo_v3_6_STABLE_copy/NEMOGCM@6486

  • Property svn:executable set to *
File size: 1.7 KB
Line 
1#!/bin/bash
2##########################################################################
3# Author : Simona Flavoni for NEMO
4# Contact : sflod@locean-ipsl.upmc.fr
5#
6# ----------------------------------------------------------------------
7# NEMO/SETTE , NEMO Consortium (2010)
8# Software governed by the CeCILL licence     (NEMOGCM/NEMO_CeCILL.txt)
9# ----------------------------------------------------------------------
10#
11# Some scripts called by sette.sh
12# prepare_exe_dir.sh : script prepares execution directory for test
13##########################################################################
14#set -x
15set -o posix
16#set -u
17#set -e
18#+
19#
20# ==================
21# prepare_exe_dir.sh
22# ==================
23#
24# ----------------------------------------------
25# Set of functions used by sette.sh (NEMO tests)
26# ----------------------------------------------
27#
28# SYNOPSIS
29# ========
30#
31# ::
32#
33#  $ ./prepare_exe_dir.sh
34#
35# DESCRIPTION
36# ===========
37#
38# prepare_exe_dir.sh creates execution directory takes name of TEST_NAME defined in every test in sette.sh
39#
40# it is necessary to define in sette.sh TEST_NAME ( example : export TEST_NAME="LONG") to create execution directory in where run test.
41#
42# NOTE : each test has to run in its own directory ( of execution), if not existing files are re-written (for example namelist)
43#
44# EXAMPLES
45# ========
46#
47# ::
48#
49#  $ ./prepare_exe_dir.sh
50#
51#
52# TODO
53# ====
54#
55# option debug
56#
57#
58# EVOLUTIONS
59# ==========
60#
61# $Id: $
62#
63#   * creation
64#-
65
66
67cd ${CONFIG_DIR}
68mkdir -p ${NEW_CONF}/${TEST_NAME}
69
70export EXE_DIR=${CONFIG_DIR}/${NEW_CONF}/${TEST_NAME}
71
72cp -rL ${CONFIG_DIR}/${NEW_CONF}/EXP00/* ${EXE_DIR}/.
73if [ ! -f ${EXE_DIR}/file_def.xml ]; then cp -r ${SETTE_DIR}/iodef_sette.xml ${EXE_DIR}/iodef.xml; fi
74cd ${EXE_DIR}
Note: See TracBrowser for help on using the repository browser.