Dynlib: Difference between revisions
m Fixed typo |
Typesetting |
||
| (17 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== [ | == [http://folk.uib.no/csp001/dynlib_doc/ Documentation] == | ||
The steps necessary to obtain dynlib are described below. A more thorough documentation is compiled in [ | 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]. | ||
== Obtaining dynlib == | == Quick start to developing with dynlib == | ||
*Before you compile you need to set up an environment where you will install the necessary libraries with the required version (e.g., numpy not newer than 1.26.2) | |||
*:<code>$ python3 -m venv dyn</code> | |||
*:<code>$ pip install numpy==1.26.2</code> | |||
*:<code>$ pip install scipy python-dateutil</code> | |||
*:<code>$ pip install xarray pandas netcdf4 h5netcdf</code> | |||
*:<code>$ pip install python-dateutil</code> | |||
*:<code>$ pip install basemap==1.3.8 basemap-data-hires</code> | |||
*Then activate the environment | |||
*:<code>$ '''source''' dyn/bin/activate</code> | |||
=== Obtaining dynlib === | |||
#Copying the source code repository | |||
#:<code>$ git clone /Data/gfi/users/local/src/dynlib.git</code> | |||
# Copying the source code repository | |||
#:<code>$ git clone /Data/gfi/users/ | |||
#: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/ | #:<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> | ||
# Compile the library | #Compile the library | ||
#:<code>$ ./compile</code> | #:<code>$ ./compile</code> Make sure that the current hostname is recognised, if needed add the following lines to compile | ||
#:<code>if [ "${host: -9}" == 'novalocal' ]; then</code><code> LIBS="-L$(pwd)/ext/spherepack3.2/lib -lopenblas -lscalapack -lspherepack"</code> <code> RPATH="" #-Wl,-rpath,/Data/gfi/users/local/lib"</code> and change <code>host=`hostname -f`</code> to <code>host=`hostname`</code> | |||
#:<code>$ ./ | # Finally, you need to link external libraries | ||
#:<code>export LD_LIBRARY_PATH="/cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/generic/software/ScaLAPACK/2.2.0-gompi-2023b-fb/lib:/cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/generic/software/OpenBLAS/0.3.24-GCC-13.2.0/lib"</code> | |||
# To use your personal development version of dynlib, create a symlink in your scripts folder that points to the development version | |||
#:<code><in script folder>$ ln -s <path-to-dynlib>/lib dynlib</code> | |||
#:<code> | |||
=== Editing the Fortran code === | === Editing the Fortran code === | ||
The fortran code lives in <code> | The fortran code lives in <code>lib/fortran</code> directory. At the moment there are 16 source code files<br /> | ||
<nowiki>$ ls *.f90 | |||
config.f90 detect_lines.f90 ellipse.f90 stat.f90 | |||
const.f90 detect_rwb_contour.f90 interpol.f90 tend.f90 | |||
derivatives.f90 diag.f90 kind.f90 thermodyn.f90 | |||
detect.f90 diag_tend.f90 sphere.f90 utils.f90</nowiki> | |||
The most important are <code>diag.f90</code> which contains subroutines that calculate various diagnostics, and <code>detect.f90</code> which contains feature detection algorithms. Changed Fortran sources need to be recompiled, again using | |||
:<code>$ ./compile</code> | :<code>$ ./compile</code> | ||
| Line 55: | Line 61: | ||
=== Using the Fortran functions === | === Using the Fortran functions === | ||
An example python script which calculates deformation using the Fortran function is provided | An example python script which calculates deformation using the Fortran function is provided in the [http://folk.uib.no/csp001/dynlib_doc/examples.html documentation]. | ||
== 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]. | ||
[[Category:Dynlib]] | [[Category:Dynlib]] | ||
[[Category:Libraries]] | [[Category:Libraries]] | ||
Latest revision as of 09:42, 17 April 2026
The steps necessary to obtain dynlib are described below. A more thorough documentation is compiled in the main documentation website.
Quick start to developing with dynlib
- Before you compile you need to set up an environment where you will install the necessary libraries with the required version (e.g., numpy not newer than 1.26.2)
$ python3 -m venv dyn$ pip install numpy==1.26.2$ pip install scipy python-dateutil$ pip install xarray pandas netcdf4 h5netcdf$ pip install python-dateutil$ pip install basemap==1.3.8 basemap-data-hires
- Then activate the environment
$ source dyn/bin/activate
Obtaining dynlib
- 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
- Change into the dynlib folder
$ cd dynlib
- Compile the library
$ ./compileMake sure that the current hostname is recognised, if needed add the following lines to compileif [ "${host: -9}" == 'novalocal' ]; thenLIBS="-L$(pwd)/ext/spherepack3.2/lib -lopenblas -lscalapack -lspherepack"RPATH="" #-Wl,-rpath,/Data/gfi/users/local/lib"and changehost=`hostname -f`tohost=`hostname`
- Finally, you need to link external libraries
export LD_LIBRARY_PATH="/cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/generic/software/ScaLAPACK/2.2.0-gompi-2023b-fb/lib:/cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/generic/software/OpenBLAS/0.3.24-GCC-13.2.0/lib"
- To use your personal development version of dynlib, create a symlink in your scripts folder that points to the development version
<in script folder>$ ln -s <path-to-dynlib>/lib dynlib
Editing the Fortran code
The fortran code lives in lib/fortran directory. At the moment there are 16 source code files
$ ls *.f90 config.f90 detect_lines.f90 ellipse.f90 stat.f90 const.f90 detect_rwb_contour.f90 interpol.f90 tend.f90 derivatives.f90 diag.f90 kind.f90 thermodyn.f90 detect.f90 diag_tend.f90 sphere.f90 utils.f90
The most important are diag.f90 which contains subroutines that calculate various diagnostics, and detect.f90 which contains feature detection algorithms. Changed Fortran sources need to be recompiled, again using
$ ./compile
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 in the documentation.
Dynlib functions
The functions are classified into different categories. All functions and categories listed in the API documentation.
