Now the selection of forecast system via fcsys works.

In CFU_PB quantile computation type set to 8. Before type was set to 7.

Now lat and lon objects should be correct.

wasted) + times failed.

Usage:
- Upload exp_job_info.sh to the platform where yo are running the
experiment.
- Run the script ./exp_info.sh <ARCH> <EXPID> <ESTIMATED RUNTIME>
e.g.: ./exp_info.sh mn m00v 1.3 > m00v.txt
- Download the output to your local machine
- Run python plotting script

CFU_NAO() computes the North Atlantic Oscillation (NAO) index based
on the projection onto the pattern of the leading observed EOF mode.
See the extensive description in the header of the function.

CFU_plotbox() produces a time series of the obs vs. box-and-whisker plots of
the re-forcast for a specific target period.
See the extensive description in the header of the function.

Now working fine when forecast lead dimension equals 1.

- deploy has already been shifted under separate project (https://dev.cfu.local/deploy_models.git), in case if someone interested to look into something feel free to grep the stuff from new project
- while transfer related scripts has got minor update...

- scripts/tools added for preparing and reformatting atmospheric initial conditions in the context of CFU infrastructure.

- chkexpout.sh: by using this tool/script/feature user may have a quick view regarding the downloaded files at cfunas after finishing some experiment at HPC.
e.g:
> ./chkexpout.sh ecearth m00y
m00y 19821101 fc0 MMA=14 MMO=14 SIZE=50G LOGS=0 TOTAL_SIZE=50G
51G     /cfunas/exp/ecearth/m00y
du: cannot access `/cfunas/exp/ecearth/gribfiles/m00y': No such file or directory

- chkexpjlt.sh: by using this tool/script/feature user may have a picture about job's life time (currently working for simulation jobs only) and this implies to running experiments at HPC or recently completed.
e.g:
> ./chkexpjlt.sh mn-pr1e4400 m00y 5.88
Job_Number Job_Life_Time(Hours) Job_Wasted_Time(Hours) Job_Failed Remarks
1 27.55 21.67 2 m00y_19821101_fc0_1_sim
2 5.88 0.00 0 m00y_19821101_fc0_2_sim
3 17.55 11.67 1 m00y_19821101_fc0_3_sim
4 19.35 13.47 1 m00y_19821101_fc0_4_sim
5 14.60 8.72 0 m00y_19821101_fc0_5_sim
6 11.75 5.87 0 m00y_19821101_fc0_6_sim
7 7.87 1.99 0 m00y_19821101_fc0_7_sim
8 18.47 12.59 0 m00y_19821101_fc0_8_sim
9 25.83 19.95 0 m00y_19821101_fc0_9_sim
10 8.78 2.90 0 m00y_19821101_fc0_10_sim
11 42.23 36.35 0 m00y_19821101_fc0_11_sim
12 12.55 6.67 0 m00y_19821101_fc0_12_sim
13 14.23 8.35 1 m00y_19821101_fc0_13_sim
14 7.38 1.50 0 m00y_19821101_fc0_14_sim
m00y (optimum computing time per job ~5.88H)
started: May 31 12:26 - till: Jun 10 08:18

Corrected weights for area mean in CFU_MODE(), CFU_EOF(), CFU_AMO().

- ecearth3 structural change: v3.0-r1012 has been renamed as v3.0 (that's the real tagged name of the version as downloaded from the ecearth3 repository)

New option to CFU_clim, NDV for an improved version of the Kharin method + new function CFU_selindices

==========================================

Here is below a fundamental link for detailed information about available
models and computing platforms:

http://ic3.cat/wikicfu/index.php/Models

Here are below fundamental paths for the sources of models and
released patches (w.r.t. different platforms):

/cfu/releases/models
/cfu/releases/patches

MODELS
------

Here is below the list of models could be deployed:

* nemo:    ecearth-v2.2, v3.2, v3.3, ece-v3.0.1
* ecearth: v2.0, v2.1, v2.2.0, v2.2.1, v2.2.3, v2.3.0, v3.0-r1012, v3.0.1

PLATFORMS
---------

Here is below the list of platforms could be used for deployment of a model:

* ithaca
* marenostrum
* marenostrum3
* ecmwf
* hector
* lindgren
* jaguar

e.g.
----

Here are below examples given for starting the deployment process in
distributed fashion:

> cd src
> nohup ./deploy.sh ithaca nemo ece-v3.0.1 >& deploy_ithaca_nemo_ece-v3.0.1.log &
> nohup ./deploy.sh ithaca ecearth v3.0.1 >& deploy_ithaca_ecearth_v3.0.1.log &

- new scripts have been added to update ic (atmos, ocean, ice), nudging and model's (setup & inidata)
in the context of various HPC, please feel free to use them and keep on these scripts.
- in the context of ic & nudging, its users responsiblity to keep the HPC's clean and tidiy and also
always leave one set of ic & nudging at "/cfu/releases".