Please note that FeenoX is a cloud-first back end aimed at advanced users. It does not include a graphical interface and it is not expected to run in Windows. See this 5-min explanation about why:
For an easy-to-use web-based front end with FeenoX running in the cloud directly from your browser see CAEplex at https://www.caeplex.com.
Any contribution to make dekstop GUIs such as PrePoMax or FreeCAD to work with FeenoX are welcome.
FeenoX is distributed under the terms of the GNU General Public License version 3 or (at your option) any later version.
Debian/Ubuntu packages (unofficial) | https://www.seamplex.com/feenox/dist/deb |
GNU/Linux static binaries | https://www.seamplex.com/feenox/dist/linux |
Windows binaries | https://www.seamplex.com/feenox/dist/windows |
Source tarballs | https://www.seamplex.com/feenox/dist/src |
Github repository | https://github.com/seamplex/feenox/ |
FeenoX is cloud-first. It was designed to run on servers.
Be aware that FeenoX does not have a GUI. Read the documentation, especially the description and the FAQs. Ask for help on the GitHub discussions page if you do now understand what this bullet means.
Debian/Ubuntu packages are unofficial, i.e. they are not
available in apt
repositories. They contain
dynamically-linked binaries and their dependencies are hard-coded for
each Debian/Ubuntu release. Make sure you get the right
.deb
for your release
(i.e. bookworm
/bullseye
for Debian,
kinetic
/focal
for Ubuntu).
Generic GNU/Linux binaries are provided as statically-linked executables for convenience. They do not support MUMPS nor MPI and have only basic optimization flags. Please compile from source for high-end applications. See detailed compilation instructions.
Try to avoid Windows as much as you can. The binaries are provided as transitional packages for people that for some reason still use such an outdated, anachronous, awful and invasive operating system. They are compiled with Cygwin and have no support whatsoever. Really, really, get rid of Windows ASAP.
“It is really worth any amount of time and effort to get away from Windows if you are doing computational science.”
https://lists.mcs.anl.gov/pipermail/petsc-users/2015-July/026388.html
Debian/Ubuntu packages are available at https://www.seamplex.com/feenox/dist/. Find the directory for your Debian or Ubuntu release, i.e.
bookworm
is Debian 12bullseye
is Debian 11buster
is Debian 10kinetic
is Ubuntu 22.10jammy
is Ubuntu 22.04focal
is Ubuntu 20.04If you know how to install .deb
packages, feel free to
use your method (i.e. gdebi
or with the “Software Center”
thing).
You can can always use dpkg
(as root):
$ sudo dpkg -i feenox-0.3_1_amd64.deb
Most likely, this step will fail due to failed dependencies. Just
call apt
to fix them for you:
$ sudo apt-get --fix-broken install
Now the command feenox
should be globally available:
$ feenox
FeenoX v0.3
a cloud-first free no-fee no-X uniX-like finite-element(ish) computational engineering tool
usage: ./feenox [options] inputfile [replacement arguments] [petsc options]
-h, --help display options and detailed explanations of commmand-line usage
-v, --version display brief version information and exit
-V, --versions display detailed version information
-c, --check validates if the input file is sane or not
--pdes list the types of PROBLEMs that FeenoX can solve, one per line
--elements_info output a document with information about the supported element types
--linear force FeenoX to solve the PDE problem as linear
--non-linear force FeenoX to solve the PDE problem as non-linear
Run with --help for further explanations.
$
If the execution fails, most likely the version of the
.deb
does not match your GNU/Linux release. Please try the
statically-linked binaries below or ask in the FeenoX
discussions page.
The FeenoX Unix man page should be available in section one:
$ man -k feenox
feenox (1) - a cloud-first free no-X uniX-like finite-element(ish) computational engineering tool
$ man feenox
$
Browse to https://www.seamplex.com/feenox/dist/ and check what the latest version for your architecture is. Then do
feenox_version=1.0.8
wget -c https://www.seamplex.com/feenox/dist/linux/feenox-v${feenox_version}-linux-amd64.tar.gz
tar xzf feenox-v${feenox_version}-linux-amd64.tar.gz
sudo cp feenox-v${feenox_version}-linux-amd64/bin/feenox /usr/local/bin
You’ll have the binary under bin
and examples,
documentation, manpage, etc under share
. Copy
bin/feenox
into somewhere in the PATH
and that
will be it. If you are root, do
sudo cp feenox-v${feenox_version}-linux-amd64/bin/feenox /usr/local/bin
If you are not root, the usual way is to create a directory
$HOME/bin
and add it to your local path. If you have not
done it already, do
mkdir -p $HOME/bin
echo 'expot PATH=$PATH:$HOME/bin' >> .bashrc
Then finally copy bin/feenox
to
$HOME/bin
cp feenox-v${feenox_version}-linux-amd64/bin/feenox $HOME/bin
Check if it works by calling feenox
from any directory
(you might need to open a new terminal so .bashrc
is
re-read):
$ feenox
FeenoX v1.0.8-g731ca5d
a cloud-first free no-fee no-X uniX-like finite-element(ish) computational engineering tool
usage: ./feenox [options] inputfile [replacement arguments] [petsc options]
-h, --help display options and detailed explanations of commmand-line usage
-v, --version display brief version information and exit
-V, --versions display detailed version information
-c, --check validates if the input file is sane or not
--pdes list the types of PROBLEMs that FeenoX can solve, one per line
--elements_info output a document with information about the supported element types
--linear force FeenoX to solve the PDE problem as linear
--non-linear force FeenoX to solve the PDE problem as non-linear
Run with --help for further explanations.
$
To compile the source tarball, proceed as follows. This procedure
does not need git
nor autoconf
but a new
tarball has to be downloaded each time there is a new FeenoX
version.
Install mandatory dependencies
sudo apt-get update
sudo apt-get install gcc make libgsl-dev
If you cannot install libgsl-dev
, you can have the
configure
script to download and compile it for you. See
point 4 below.
Install optional dependencies (of course these are optional but recommended)
sudo apt-get install libsundials-dev petsc-dev slepc-dev
Download and un-compress FeenoX source tarball. Browse to https://www.seamplex.com/feenox/dist/src/ and pick the latest version:
wget https://www.seamplex.com/feenox/dist/src/feenox-v0.1.66-g1c4b17b.tar.gz
tar xvzf feenox-v0.1.66-g1c4b17b.tar.gz
Configure, compile & make
cd feenox-v0.1.66-g1c4b17b
./configure
make -j4
If you cannot (or do not want) to use libgsl-dev
from a
package repository, call configure
with
--enable-download-gsl
:
./configure --enable-download-gsl
If you do not have Internet access, get the tarball manually, copy it
to the same directory as configure
and run again.
Run test suite (optional)
make check
Install the binary system wide (optional)
sudo make install
To compile the Git repository, proceed as follows. This procedure
does need git
and autoconf
but new versions
can be pulled and recompiled easily. If something goes wrong and you get
an error, do not hesitate to ask in FeenoX’s discussion
page.
Install mandatory dependencies
sudo apt-get update
sudo apt-get install git build-essential make automake autoconf libgsl-dev
If you cannot install libgsl-dev
but still have
git
and the build toolchain, you can have the
configure
script to download and compile it for you. See
point 4 below.
Install optional dependencies (of course these are optional but recommended)
sudo apt-get install libsundials-dev petsc-dev slepc-dev
Clone Github repository
git clone https://github.com/seamplex/feenox
Boostrap, configure, compile & make
cd feenox
./autogen.sh
./configure
make -j4
If you cannot (or do not want to) use libgsl-dev
from a
package repository, call configure
with
--enable-download-gsl
:
./configure --enable-download-gsl
If you do not have Internet access, get the tarball manually, copy it
to the same directory as configure
and run again. See the
detailed compilation instructions for an
explanation.
Run test suite (optional)
make check
Install the binary system wide (optional)
sudo make install
To stay up to date, pull and then autogen, configure and make (and optionally install):
git pull
./autogen.sh; ./configure; make -j4
sudo make install
See the Compilation Guide for details. Ask in the GitHub Discussions page for help.
FeenoX is distributed under the terms of the GNU General Public License version 3 or (at your option) any later version. The following text was borrowed from the Gmsh documentation. Replacing “Gmsh” with “FeenoX” gives:
FeenoX is “free software”; this means that everyone is free to use it and to redistribute it on a free basis. FeenoX is not in the public domain; it is copyrighted and there are restrictions on its distribution, but these restrictions are designed to permit everything that a good cooperating citizen would want to do. What is not allowed is to try to prevent others from further sharing any version of FeenoX that they might get from you.
Specifically, we want to make sure that you have the right to give away copies of FeenoX, that you receive source code or else can get it if you want it, that you can change FeenoX or use pieces of FeenoX in new free programs, and that you know you can do these things.
To make sure that everyone has such rights, we have to forbid you to deprive anyone else of these rights. For example, if you distribute copies of FeenoX, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must tell them their rights.
Also, for our own protection, we must make certain that everyone finds out that there is no warranty for FeenoX. If FeenoX is modified by someone else and passed on, we want their recipients to know that what they have is not what we distributed, so that any problems introduced by others will not reflect on our reputation.
The precise conditions of the license for FeenoX are found in the General Public License that accompanies the source code. Further information about this license is available from the GNU Project webpage http://www.gnu.org/copyleft/gpl-faq.html.
FeenoX is licensed under the terms of the GNU General Public License version 3 or, at the user convenience, any later version. This means that users get the four essential freedoms:1
So a free program has to be open source, but it also has to
explicitly provide the four freedoms above both through the written
license and through appropriate mechanisms to get, modify, compile, run
and document these modifications using well-established and/or
reasonable straightforward procedures. That is why licensing FeenoX as
GPLv3+ also implies that the source code and all the scripts and
makefiles needed to compile and run it are available for anyone that
requires it (i.e. it is compiled with
./configure && make
). Anyone wanting to modify the
program either to fix bugs, improve it or add new features is free to do
so. And if they do not know how to program, the have the freedom to hire
a programmer to do it without needing to ask permission to the original
authors. Even more, the
documentation is released under the terms of the GNU Free Documentation
License so these new (or modified) features can be properly
documented as well.
Nevertheless, since these original authors are the copyright holders, they still can use it to either enforce or prevent further actions from the users that receive FeenoX under the GPLv3+. In particular, the license allows re-distribution of modified versions only if
There are also some other subtle technicalities that need not be discussed here such as
These issues are already taken into account in the FeenoX licensing scheme.
It should be noted that not only is FeenoX free and open source, but also all of the libraries it depends on (and their dependencies) also are. It can also be compiled using free and open source build tool chains running over free and open source operating systems.
There are some examples of pieces of computational software which are described as “open source” in which even the first of the four freedoms is denied. The most iconic case is that of Android, whose sources are readily available online but there is no straightforward way of updating one’s mobile phone firmware with a customized version, not to mention vendor and hardware lock ins and the possibility of bricking devices if something unexpected happens. In the nuclear industry, it is the case of a Monte Carlo particle-transport program that requests users to sign an agreement about the objective of its usage before allowing its execution. The software itself might be open source because the source code is provided after signing the agreement, but it is not free (as in freedom) at all.↩︎