Announcement

Collapse
No announcement yet.

C++ API; fluid solver example

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • C++ API; fluid solver example

    Hello and thanks for your open source software! I was just wondering if the situation has changed much regarding the C++ API from this earlier post: https://forums.febio.org/forum/febio...tion#post11494

    If so, do you have any simple example using one of your flow solvers? We are researching how we might link our PhysiCell agent-based modeling software with FEBio.

    thanks, Randy
    Discuss issues related to code development and implementation of FEBio.

  • #2
    Hi,

    What type of example would you like to see: Adding a custom viscous fluid? A custom fluid boundary condition? Or something totally different? If you could suggest an example that would be useful to you we could try to implement and share that.

    Best,

    Gerard

    Comment


    • #3
      Thanks Gerard. I'm not looking for anything custom at this point, I'd just like to see a pure C++ example. For example, is there an equivalent to doing this: https://febio.org/knowledgebase/tuto...n-febiostudio/ in C++ without any GUI?

      Comment


      • #4
        Thanks for clarifying. Unfortunately no, at this time we don't have an API for FEBioStudio. The simple reason is that, as of now, FEBioStudio is not as mature as FEBio. However, Steve maas (the main developer of FEBioStudio) is working on a new version that should bring us a step closer to releasing an API in the future (he is rewriting the code to use FEBio libraries where applicable, which is not the case in the current version).

        Best,

        Gerard

        Comment


        • #5
          OK, I appreciate the replies. We'll take another look once there is a C/C++ API.

          Comment


          • #6
            Hi Randy,

            Just to expand a bit on what we currently support, we do have an API for developing FEBio plugins, and you can find the documentation for this on the developer's manual. We have used this ourselves to link FEBio to other libraries. I imagine that a similar approach might work for you although I would need to know a bit more about your project. The advantage of using a plugin is that in the next major release for febio studio (version 2.0), the UI will support FEBio plugin integration directly and you would be able to edit your plugin settings directly in the febio studio ui, but without the need to actually write UI code. I you want to know more about this, feel free to reach out via email (steve dot maas at utah dot edu).

            Best,

            Steve
            Department of Bioengineering, University of Utah
            Scientific Computing and Imaging institute, University of Utah

            Comment


            • #7
              Thanks Steve, I will indeed email you to follow-up. Let me do a bit more poking around in your github repo first, in order to ask more intelligent questions.

              Comment

              Working...
              X