Libscientific is a C framework for multivariate and other statistical analysis written to be quasi-completely independent of common and well-established calculus libraries, except for the lapack library, which is used only to calculate left eigenvectors and eigenvalues.
The main goals of libscientific are:
- To provide a simple and tiny framework for multivariate analysis that can be used not only in regular computers but also in embedded systems
- Create a robust library of multivariate algorithms for any research and industrial application
Currently libscientific is able to compute:
-
Multivariate analysis
- Principal Component Analysis (PCA) NIPALS algorithm) [1]
- Partial Least Squares (PLS) NIPALS algorithm [1]
- Consensus PCA (CPCA) NIPALS algorithm [7]
- Multiple Linear Regression (MLR) Ordinary least squares algorithm
- Unfold PCA (UPCA) [2]
- Unfold PLS (UPLS) [2]
- Fisher LDA
-
Clustering
- K-means++ (David Arthur modification) [3]
- Hierarchical clustering
-
Object/Instance selection
- Most Descriptive Compounds (MDC) [4]
- Most Dissimilar Compounds (DIS) [5]
-
Statistical analyisis
- R2, MSE, MAE, RMSE, BIAS, Sensitivity, Positive Predicted Values
- Yates analysis
- Receiver operating characteristic (ROC)
- Precision-Recal
- Matrix-Matrix Euclidean, Manhattan, Cosine and Mahalanobis distances
-
Numerical analysis
- Estimate of an integral over a xy region (numerical integration using the trapezoid rule)
- Natural cubic spline interpolation and prediction
- Ordinary Least-Squares (OrdinaryLeastSquares)
- Linear Equation Solver (SolveLSE)
- Singular value decomposition
-
Optimization
- Nelder-Mead simplex algorithm
Moreover for some algorithms is possible to run validation methods with parallel computing to be faster:
- Bootstrap k-fold Cross Validation (RGCV)
- Leave-One-Out
- Y-Scrambling [6]
The library documentation is available at http://gmrandazzo.github.io/libscientific/
-
Implement Independent Component Analysis ICA
-
Implement PARAFAC
-
Exstensive test of some numerical analyisis methods: CholeskyReduction, QR Decomposition, LU Decomposition, HouseholderReduction and so on.
-
Fix UPLS algorithm
[1] P. Geladi, B.R. Kowalski Partial least-squares regression: a tutorial Analytica Chimica Acta Volume 185, 1986, Pages 1-17 link
[2] S. Wold, P. Geladi, K. Esbensen and J. Öhman MULTI-WAY PRINCIPAL COMPONENTSAND PLS-ANALYSIS Journal of Chemometrics Volume 1, Issue 1, pages 41–56, January 1987 link
[3] T. Kanungo, D.M. Mount, N.S. Netanyahu, C.D. Piatko, R. Silverman, A.Y. Wu An efficient k-means clustering algorithm: analysis and implementation Pattern Analysis and Machine Intelligence, IEEE Transactions on Issue Date: Jul 2002 On page(s): 881 - 892 link
[4] B.D. Hudson, R.M. Hyde, E. Rahr, J, Wood and J. Osman Parameter Based Methods for Compound Selection from Chemical Databases Quantitative Structure-Activity Relationships Volume 15, Issue 4, pages 285–289, 1996 link
[5] J. Holliday, P. Willett Definitions of "Dissimilarity" for Dissimilarity-Based Compound Selection Journal of Biomolecular Screening Volume 1, Number 3, 1996 Pages: 145-151 link
[6] R.D. Clark , P.C. Fox Statistical variation in progressive scrambling. J Comput Aided Mol Des. 2004 Jul-Sep;18(7-9):563-76. link
[7] J. A. Westerhuis, T. Kourti and J.F. Macgregor Analysis of multiblock and hierarchical PCA and PLS models Journal of Chemometrics 1998 12, 301-321 link
Libscientific is distributed under GPLv3 license. To know more in detail how the license work, please read the file "LICENSE" or go to "http://www.gnu.org/licenses/gpl-3.0.en.html"
The required dependencies to use libscientific are:
- lapack/blas library or a fortran compiler
- libsqlite3
- c compiler (gcc or clang for osx)
- cmake
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=/usr/ ..
make -j
make test # optional
sudo make install
cd ../src/python_bindings/
sudo pip install -e .
pytest # optional
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release -DPORTABLE_PYTHON_PACKAGE=True ..
make -j
cd ../src/python_bindings/
OSX: python3 setup.py bdist_wheel --plat-name macosx-14-0-arm64
Linux: python3 setup.py bdist_wheel --plat-name manylinux1_x86_64
N.B.: pip3 debug --verbose to get the compatible tags
mkdir build
cd build
cmake -G "MinGW Makefiles" -DCMAKE_BUILD_TYPE=Release -DPORTABLE_PYTHON_PACKAGE=True ..
mingw32-make -j
cd ../src/python_bindings/
python3 setup.py bdist_wheel --plat-name win_amd64
python3 setup.py bdist_wheel --plat-name mingw_x86_64
N.B.: pip3 debug --verbose to get the compatible tags
brew tap gmrandazzo/homebrew-gmr
brew install --HEAD libscientific
If you are interested in extending or developing a new algorithm, please read here to understand the logic behind the library.
The library is engineered to have a specific data structure for every model, which is then stored in the HEAP to support dynamic memory allocation. Every data object, such as matrix, vectors, tensors, or in general pca/pls/upca/...models, need to be manually allocated/deallocated using the predefined constructs “NewSOMETHING(&…);” and “DelSOMETHING(&…);”.
For example, pca.c contains:
- A data structure to store the model output (PCAMODEL). In this data structure, you have standard libscientific types such as matrix and vectors.
- A function that computes the PCA model (PCA(...)). This function takes an input matrix using the libscientific data type and uses this to produce and store the pca model inside the PCAMODEL data structure.
All the multivariate analysis algorithms are implemented with this logic: reusing libscientific datatype, writing a data structure for the algorithm, and writing the necessary functions to run the calculation.
N.B.: If you develop or modify an algorithm, a unit test and a stress test needs to be created to prove that the algorithm works and his numerically solid.
To contribute, you can fork the project, or if you have already forked the project update to the latest version of libscientific, make the changes and open a Pull Request.
Here are some important requests.
Before opening a Pull Request:
- Be sure that your code it's working.
- No leaks. Run valgrind.
- Comment your code with Parameters, attributes, returns, notes, and References.
- Test examples are necessary. Tests must prove that
- the algorithm works correctly
- the algorithm do not present any memory leak
Please first read the cmake documentation about testing with cmake and ctest
Then write a test for the proposed algorithm and save it in "src/tests" directory. Please write a test in src/python_bindings/tests for the python binding. The test should work using pytest.
Run and submit the resulting output in the pull request specifying:
- What the algorithm does
- What the unit tests represent and what they prove.