Results 1 to 1 of 1

Thread: FEBio2

  1. #1
    Join Date
    Nov 2007
    Salt Lake City, UTAH

    Default FEBio2

    The development of a new FEBio branch has started, entitled FEBio2. At this point, the branch is purely experimental, but it is hoped that in the future it will be able to replace the current development version of FEBio. The main goal of this new branch is to address several limitations in FEBio and propose alternative structures to overcome them. Here are some of the issues that are being worked on.

    1. Restructuring of the source code folder hierarchy. The FEBio folder is split in the following sub-folders:

    - FECore: core functionality and SDK implementation
    - FEBioLib: implementation of FEBio as a library.
    - FEBio2: front-end to FEBio library.
    - VS2008: solution for Visual Studio 2008
    - VS2010: solution for Visual Studio 2010

    Some of the advantages of this restructuring are: VS08 and VS10 solutions can now work independently without clashing. The FECore library will implement the SDK (see below) which will be the interface for FEBio plugins. The separation of the main code into a library and a front-end opens the possibility to build diferent front-ends (e.g. GUI front-end) or easier integration of FEBio into other custom codes.

    2. FEBio SDK: a plugin framework for FEBio. Users will be able to write plugins to FEBio without the need to recompile the FEBio executable. A simple plugin mechanism is currently implemented which allows users to implement custom materials, bodyforces, plot data and task classes.

    3. Removal of the UnpackElement functions. These Domain member functions prepared some data structures for accessing element data. Unfortunatly, a severe limitation is that only one element can be unpacked at a time, making multi-threading nearly impossible. These functions will be removed and replaced with alternative structures and functions that will overcome the limitation, and preparing the code for multi-threading.

    4. To facilitate user customizations to FEBio, the current framework will be expanded to allow easier integration with FEBio's input and output formats. One important change will be that all classes that can be customized will be able to define parameter lists. Since FEBio will automatically read parameter lists from the input file, users will not have to modify the input functions and classes.

    In addition, we hope to expand FEBio's capabilities even further by adding more analysis modes and solution strategies, especially those useful in the field of computational biomechanics.

    If you would like to learn more about FEBio2, feel free to post a question, suggestion or comment. We would love to hear from you.


    Last edited by maas; 08-10-2011 at 02:16 PM.
    Department of Bioengineering, University of Utah
    Scientific Computing and Imaging institute, University of Utah

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts