RLaB3 is an interactive, interpreted scientific programming environment for Linux operating system. It allows fast prototyping and script development. Its syntax is a combination of c (curly brackets for blocks of statement, some statements) and M**LAB and fortran (e.g., indexing of arrays starts from 1). The project RLaB3 provides a syntax update with some internal and organizational changes compared to RLaB2, as developed by Ian Searle. The projects support 32- and 64-bit linux systems, for AMD, Intel and arm/RaspberryPi.
The project RLABPLUS adds a number of solvers, input/output operations, and visualization features and connections to other specialized software, in form of shared object libraries. Basically, the solvers within the project are aimed at narrow technical field, and might not be of interest to wide audiences. For that reason, these solvers were not incorporated into RLaB3 but are, so to speak, free standing.
The project comprise the following solver libraries:
-
gpib - GPIB (Hewlett-Packard's General Purpose Interface Bus, for those who still use it and remember it) for hardware and instrumentation control: RLaB2/RLaB3 wrapper for linux-gpib.
-
glpk - provides solvers from GNU linear programming kit.
-
gphoto2 - provides camera control and image download for usb connected cameras using gphoto2.
-
gts - provides access to GNU triangulation library for meshes creations and computations.
-
kripto - provides cryptography functions from libkripto.
-
matio - MATLAB /mostly input/only basic output/ library: if you are wondering about the asymmetry, well, since 2010's RLaB2/RLaB3 support input/output using HDF5 for all its data structures (except cell that was added in 2018). As MATLAB mat files format is an abominable obfuscation of HDF5, advanced users should not have problems importing HDF5 files into it.
-
ngspice - access to modeling of electronic/thermal circuits using ngspice : create circuit scripts, executing them using a multiprocessor ngspice interpreter, with computation results returned as internal variables. The only caveat of the approach is that ngspice has to be built as a shared library: Fear not, however, the library supports linux systems with ngspice executable only, as well, but then its supports boils down to script creation, calling executable to execute the scripts and write the output in their raw format, which can be post-processed by RLaB2/RLaB3. My doppelgaenger posted code model for diode that was aimed at electro-thermal modeling of the component using RLaB2/RLaB3.
At random times it may happen that a library is gobbled up by RLaB3: If that is the case then it will dissappear from this list, and appear as a part of RLaB3, with the request that the shared library be available for linking.
At some other random times it may happen that the library and its shared library are both gobbled up by RLaB3: This happened to fann library after I modified it to suit my needs (I allowed NN nodes to have fixed - as in immutable - weights, this change was forked off official site and absorbed into RLaB3). In this particular case the home-brewed NN library I developed way back, was removed.