FeenoX documentation is released under the terms of the GNU Free Documentation License v1.3, or any later version.
Every bit of FeenoX documentation is written in Pandoc-flavored Markdown. It is then converted to HTML, PDF, Unix manpage or Texinfo as needed.
As per the GNU Coding Standards, “a manual should serve both as tutorial and reference.” Due to the formatting restrictions, the Texinfo version contains only the description and not the full reference.
The sources are in the doc directory of the Git repository.
The FeenoX project starts as an offer to an imaginary “request for quotations” that defines software requirements specifications for an open source computational tool.
Then a fictitious “offer” to the above tender is given in a software design specifications document that explains the design decisions and features included in FeenoX.
Why FeenoX works the way it works (i.e. why it does not run in Windows)
Check out FeenoX’ Frequently Asked Questions * Ask yours on GitHub Discussions * Check also the GitHub Issues
manpage converted to HTML. It should be accessible with
man feenox after (global) installation and its sources are
available in the Git repository.
Go directly to the point and see how to solve problems with FeenoX. Everything (except the case files) is included in the Git repository.
Annotated examples can be found in the examples directory of the Github repository.
These are simple and quick (but varied) cases. They are based on the August 2021 presentation:
The regression tests can also be used as quick examples:
Step-by-step instructions and explanations to solve increasingly-complex problems are given in the tutorials directory.
The FeenoX project starts as an offer to an imaginary “request for quotations” that defines software requirements specifications for a computational tool.
The “quotation” to the above tender is given in a software design specifications document that explains the design decisions and features included in FeenoX.
See the FeenoX history.
Any contribution is welcome, especially new types of PDEs and new formulations of existing PDEs. For elliptic operators feel free to use the Laplace equation as a template.
It is mandatory to observe the Code of Conduct.
TO BE DONE