Download

Source code

The Fatlab source code is hosted on SourceForge. To download, click the button below and go to the Files tab to download a .zip file containing the source code.

Download Fatlab

The source version requires Matlab R2016a or later. Due to compiled mex-files, it runs on Windows 64bit machines only. It does not draw on any additional toolboxes, just the plain version of Matlab. It can optionally use the Parallel Computing Toolbox.

Using Fatlab with earlier releases of Matlab or other operating systems requires all mex files to be re-compiled, since these are specific to the Windows 64bit platform and not backwards compatible. Help for this is available in make.m. Alternatively, all the .m versions of the compiled files can be used (just delete “_mex” from all function calls) although this is much slower.

Referencing

Fatlab is briefly described in the following paper. If you use Fatlab in an academic context, please cite it as follows:

M.M. Pedersen, “Multiaxial fatigue analysis software – Fatlab”, Proceedings of the 30th Nordic Seminar on Computational Mechanics, October 25-27, DTU, Copenhagen, 2017.


License

Fatlab

Copyright (c) 2017, Mikkel M. Pedersen, Aarhus University
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
* Neither the name of the nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


Fatlab uses the following components, primarily from Matlab Fileexchange (license files included in the download). Thanks to everybody sharing their code.

Rainflow counting algorithm by Adam Niesłony
ClickAPoint3D by Babak Taati
m3arrow by Georg Stillfried
Racetrack Filter (part of MLife) by Greg Hayman
AWAITBAR by Durga Lal Shrestha
3D mouse support using classes and events by Nick Clark
DRAGZOOM by Evgeny Pr

11 thoughts on “Download

    1. admin Post author

      I have put the last ever compiled version on SourceForge also. It contains some minor errors which are only corrected in the source version, so it is meant as a demonstration only.

      I discontinued the compiled version because I have no time to maintain it, so going forward it will only be the source version. The source version runs approximately 4x faster and includes possibility of parallelization. It requires a standard Matlab license only (no toolboxes).

      Reply
    1. admin Post author

      Dear Marko

      I would rather not maintain two different source locations. But I’m sure you can find a home computer outside the domain to download it, in order to circumvent the block. Or you can try using Google’s DNS service to avoid any blocking.

      BR Mikkel

      Reply
  1. Martin Prochazka

    Hi Mikkel,

    I would like ask you, if the Fatlab is compatible also with other softwares for ex. Octave and the others FEA softwares (Mecway, Freecad – CCX,…)…sorry, that I´m using this comment like support, but I don´t found on your websites some support page…:-)

    thank you for answere and best regards

    Martin Prochazka

    Reply
    1. admin Post author

      Hi Martin

      Fatlab is not compatible with any of the free alternatives to Matlab, sorry. It can take inputs from other programs, if you “disguise” them as e.g. ANSYS output, i.e. changing the format in script.

      BR Mikkel

      Reply
      1. Martin Prochazka

        Hi Mikkel,
        Thank you for your answere…I asked you,because I use Octave (freeware alternative to Matlab,maybe you know it) and whole starting process droped on the subfile,which is on the 3288 row of your m-file ,,fatlab.m,,…And it seems, that the Octave don’t know just this concreete subfile,because the previously orders,which are ending .mat, can open or are minimal readeble from Octave.

        Best Regards

        Martin

        Reply
        1. admin Post author

          Hi Martin

          I’m pretty confident that most of the core of the calculations will port easily to Octave, but all the GUI stuff is very Matlab specific, which I don’t think Octave can handle…

          BR Mikkel

          Reply
  2. Filip

    Hello Mikkel,

    Is there a possibility to make an executable version for non-matlab users? I believe the Matlab Compiler Toolbox has the ability to do this. I’m sure a lot of people would appreciate that.

    Thank you,

    Best regards,

    Filip

    Reply
    1. admin Post author

      Hi Filip

      I tried this in the past, however, the performance of the executable version is rather poor and some feature malfunctions. It thus became too much for me to maintain, so I discontinued that version. There is an old one you can try on SourceForge (in the Files section) , called Fatlab_deplyed_2.017.

      BR Mikkel

      Reply
      1. Filip

        Hi Mikkel,

        I have done some testing and some very useful features work quite well.
        I understand that maintaining the executable version is frustrating, but please consider, for example, doing an exe version once every two years (or whenever you see fit).
        I think the compiler toolbox is also evolving, so compiling might be more feasible with updated versions.

        Filip

        Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.