/Users/wkoeve/GeomarCloud/2018_TransientMetric/DataRepository
Fri 31 May 2019 12:17:19 CEST
wkoeve@geomar.de, v. 1.2, June 2020/ Oct 2020 / April 2021


Instructions to reproduce runs related to the paper:
Koeve, W., Kaehler, P., Oschlies, A., 2020, Does Export Production Measure Transient Changes of the Biological Carbon Pump's Feedback to the Atmosphere Under Global Warming? Geophysical Research Letters, 47, e2020GL089928. https://doi.org/10.1029/2020GL089928. 

- download UVic 2.9 from the official UVic web site
- configure UVic 2.9 to run on your local mashine in the default mode
   (see UVic web site for details)
- make sure you can compile and run UVic in the default mode; follow the instructions
  provided by the official UVic web site (you may need to make run/mk.ver complient with your system)

For each of the runs to be reproduced

- mkdir a respective run folder (e.g. 'COUPLED') 
- mkdir a subfolder called 'updates' within the run folder
- copy all files code/*.f, code/*.h from the repro repository folder to that updates folder
- cd to the updates folder
- rename all .f files to .F files, e.g. by means of the perl script rename (rename .f .F *.f )
- cd back to your run folder
- compile the code given your system's needs and the mk script provided 
  by the official UVic web site; you may use the instruction in 
  Misk/mk.generic.in after renaming it to mk.in and updating the Version_Directory entry. 
  In that case make sure that you also copy netcdf.inc from the UVic original source/netcdf to the updates folder 
- check that the first line in each .f and .h file which you find after 
  compilation in the code folder, points to the subfolder updates as the source of the code
- mkdir a subfolder 'data' inside the run folder
- copy forcing files and restart files (both can be found in the 
  data folder of the repro repository) to that data folder
- copy control* files from the repository to your run folder
- copy .nqs file from repository to your run folder
- adopt command sequence from .nqs file to your run environment; 
  in particular make sure to use correct restart.nc and control.in files, 
  as indicated in that .nqs runs script
- carry out the respective run

You should have an overall structure like this:

YourVersionDir
  |- source   (with the original UVic 2.9 files)
  |- updates
  |- run      
  |- data.100.100.19
  |- 2019_run1_repro (or whatever you name it; one folder per run!)
         |- updates (with code from the repository, .f converted to .F)
         |- code     (where your precompiled code will be found after you compile)
         |- data     (forcing data,from repository)
         mk.in
         control*.in
         *.nqs
         ... your output files (tsi, tavg, restart and log files) after the run has completed

Note: The folder 'run' which comes with the original UVic 2.9 code contains the file mk.ver. You may need to configure
this file given your local paths; eventually ask your admin for help, if needed.  
For compiling the code from this paper, make sure to link netcdf libs etc suitable for your system and compiled with your compiler. Folder data.100.100.19 which comes with orig UVic contains forcing data. By default, we you will overwrite
this generic forcing dataset by specific forcing files provided here and stored in your local data subfolder.