Dynlib: Difference between revisions

From gfi
No edit summary
No edit summary
Line 1: Line 1:
== [[Dynlib Documentation|Documentation]] ==
== [http://folk.uib.no/csp001/dynlib_doc/ Documentation] ==


The steps necessary to obtain dynlib are described below. A more thorough documentation is compiled in [[Dynlib Documentation|the main documentation page]].
The steps necessary to obtain dynlib are described below. A more thorough documentation is compiled in [http://folk.uib.no/csp001/dynlib_doc/ the main documentation website].


== Use the centrally installed dynlib ==
== Use the centrally installed dynlib ==
Line 15: Line 15:
To take into account your changes use <code>source ~/.bash_profile</code>. You can then create a project folder with the default settings file and some example scripts with the command  
To take into account your changes use <code>source ~/.bash_profile</code>. You can then create a project folder with the default settings file and some example scripts with the command  
<code>dynlib_init.py <project-name></code>.
<code>dynlib_init.py <project-name></code>.
For some types of login <code>.bash_profile</code> is not taken into account. In case you'll experience problems create a symbolic link <code>~/.bashrc</code> to point to the <code>.bash_profile</code> and re-login.


== Quick start to developing with dynlib ==
== Quick start to developing with dynlib ==
Line 72: Line 74:
== Dynlib functions ==
== Dynlib functions ==


The functions are classified into different categories.
The functions are classified into different categories. All functions and categories listed in the [http://folk.uib.no/csp001/dynlib_doc/apidoc.html API documentation].
* [[Dynlib derivatives functions|Dynlib derivatives libary]]
* [[Dynlib diag functions|Dynlib diagnostic functions]]
* [[Dynlib utils functions|Dynlib utility functions]]


[[Category:Dynlib]]
[[Category:Dynlib]]
[[Category:Libraries]]
[[Category:Libraries]]

Revision as of 07:56, 4 September 2015

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 in /Data/gfi/users/local/lib/python2.7/site-packages. You'll only have to adapt some paths in your ~/.bash_profile to start using it! Add the following to your ~/.bash_profile:

export SHARED='/Data/gfi/users/local'
export PATH="$PATH:$SHARED/bin"
export PYTHONPATH="$PYTHONPATH:$SHARED/lib/python2.7/site-packages"

To take into account your changes use source ~/.bash_profile. You can then create a project folder with the default settings file and some example scripts with the command dynlib_init.py <project-name>.

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

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 $SHARED/src/dynlib.git
    To clone the repository to your laptop or any machine outside the UiB network, use
    $ git clone <username>@login.uib.no:$SHARED/src/dynlib.git
  3. Change into the dynlib folder
    $ cd dynlib
  4. Compile the library
    $ ./compile
  5. Make sure everything works as expected
    $ ./test
  6. You can now go back to your main project folder and use dynib from there. Dynlib automatically installed a settings.py where you can override the default settings and some examples scripts in that project folder.
    $ cd ..
    $ ls
    example_ani.py example_diag.py example_netcdf_write.py example_stat.py settings.py

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.