Difference between revisions of "Dynlib"

m (Adapting developer instructions to changes in the central dynlib. Added disclaimer.)
m (Fixed typo.)
Line 23: Line 23:
 
#:<code>$ git clone /Data/gfi/users/local/src/dynlib.git</code>
 
#:<code>$ git clone /Data/gfi/users/local/src/dynlib.git</code>
 
#:To clone the repository to your laptop or any machine outside the UiB network, use
 
#:To clone the repository to your laptop or any machine outside the UiB network, use
#:<code>$ git clone <username>@login.uib.no: /Data/gfi/users/local/src/dynlib.git</code>
+
#:<code>$ git clone <username>@login.uib.no:/Data/gfi/users/local/src/dynlib.git</code>
 
# Change into the dynlib folder
 
# Change into the dynlib folder
 
#:<code>$ cd dynlib</code>
 
#:<code>$ cd dynlib</code>

Revision as of 10:48, 12 September 2017

Documentation

The steps necessary to obtain dynlib are described below. A more thorough documentation is compiled in the main documentation website.

Use the centrally installed dynlib

Dynlib is installed centrally for python 2.7 and python 3.4 in the python environments at /Data/gfi/users/local/share/virtualenv/dynpie2 and /Data/gfi/users/local/share/virtualenv/dynpie3. You'll only have to activate one of these python enviroments to start using dynlib:

source /Data/gfi/users/local/share/virtualenv/dynpieX/bin/activate

In this command X=2 for python 2.7 and X=3 for python 3.4. For convenience add this command to your ~/.bash_profile to activate the respective python environment automatically at each login.

Note: For some types of login .bash_profile is not taken into account. In case you'll experience problems create a symbolic link ~/.bashrc to point to the ~/.bash_profile and re-login.

Quick start to developing with dynlib

The following procedure is only necessary if you want to start developing dynlib further, for example if you want to add your own functions to dynlib. If you only want to use dynlib, the procedure in the above section is all you need.

Obtaining dynlib

  1. Create a new folder for the project that'll use dynlib, and go into that directory.
    $ mkdir <project-name>
    $ cd <project-name>
  2. Copying the source code repository
    $ git clone /Data/gfi/users/local/src/dynlib.git
    To clone the repository to your laptop or any machine outside the UiB network, use
    $ git clone <username>@login.uib.no:/Data/gfi/users/local/src/dynlib.git
  3. Change into the dynlib folder
    $ cd dynlib
  4. Compile the library
    $ ./compile
  5. (known broken right now) Make sure everything works as expected
    $ ./test

Happy developing!

Editing the Fortran code

The fortran code lives in src directory. At the moment there are 12 source code files

$ ls src/*.f95
src/config.f95 src/derivatives.f95 src/detect_fronts.f95 src/diag.f95 src/humidity.f95 src/stat.f95
src/const.f95 src/detect.f95 src/detect_rwb_contour.f95 src/ellipse.f95 src/kind.f95 src/utils.f95
The most important are diag.f95 which contains subroutines that calculate various diagnostics, and stat.f95 which contains statistical functions. Changed Fortran sources need to be recompiled, again using
$ ./compile

Version control

The changes you made to the source code files can be listed by

$ git status

or viewed in detailed diff-comparisons by

$ git diff

or for one file only

$ git diff <filename>

In case you want to undo your changes, you can revert any file to the last committed version by

git checkout <filename>

Commit your changes from time to time and give a sensible and brief description of your changes in the editor that is opened (automatically)

$ git commit -a

The commit is then stored in your copy of the source code repository, but not yet available for others, which allows you to also commit work-in-progress.

A more thorough introduction to the version control system is given here or on the official documentation.

Using the Fortran functions

An example python script which calculates deformation using the Fortran function is provided with example_diag.py.

Dynlib functions

The functions are classified into different categories. All functions and categories listed in the API documentation.