home.social
Sign in Create account

#fluidstructureinteraction — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #fluidstructureinteraction, aggregated by home.social.

  1. Ramiro Godoy-Diana @[email protected] ·

    📢 New post! Aerodynamic consequences of wing damage in dragonfly flapping flight blog.espci.fr/ramiro/aerodynam #Publications #Research #Aerodynamics #Flapping #Fluidstructureinteraction #Insectflight

    #publications #research #aerodynamics #flapping #fluidstructureinteraction #insectflight
  2. Giuseppe Bilotta @[email protected] ·

    I believe our approach to “develop what we need when we need it”, which has been a staple in the development of #GPUSPH, has been a strong point. We *do* depend on a few external dependencies, but most of the code has been developed “in-house”.

    Fun fact: the only “hard dependency” for GPUSPH is NVIDIA's Thrust library, which we depend on for particle sorting (and in a few other places, but for optional features, like the segmented reductions used to collect body forces when doing #FSI i.e. #FluidStructureInteraction aka #FluidSolidInteraction).

    And this hard dependency has been a *pain*.

    We first had issues in the Maxwell architecture era, which stalled our work for months because all simulations would consistently lead to a hardware lock-up
    github.com/NVIDIA/thrust/issue
    and a few years later we had another issue —luckily one we could work around within GPUSPH this time:
    github.com/NVIDIA/thrust/issue

    5/

    #gpusph #fsi #fluidstructureinteraction #fluidsolidinteraction
  3. Giuseppe Bilotta @[email protected] ·

    I believe our approach to “develop what we need when we need it”, which has been a staple in the development of #GPUSPH, has been a strong point. We *do* depend on a few external dependencies, but most of the code has been developed “in-house”.

    Fun fact: the only “hard dependency” for GPUSPH is NVIDIA's Thrust library, which we depend on for particle sorting (and in a few other places, but for optional features, like the segmented reductions used to collect body forces when doing #FSI i.e. #FluidStructureInteraction aka #FluidSolidInteraction).

    And this hard dependency has been a *pain*.

    We first had issues in the Maxwell architecture era, which stalled our work for months because all simulations would consistently lead to a hardware lock-up
    github.com/NVIDIA/thrust/issue
    and a few years later we had another issue —luckily one we could work around within GPUSPH this time:
    github.com/NVIDIA/thrust/issue

    5/

    #gpusph #fsi #fluidstructureinteraction #fluidsolidinteraction
  4. Giuseppe Bilotta @[email protected] ·

    I believe our approach to “develop what we need when we need it”, which has been a staple in the development of #GPUSPH, has been a strong point. We *do* depend on a few external dependencies, but most of the code has been developed “in-house”.

    Fun fact: the only “hard dependency” for GPUSPH is NVIDIA's Thrust library, which we depend on for particle sorting (and in a few other places, but for optional features, like the segmented reductions used to collect body forces when doing #FSI i.e. #FluidStructureInteraction aka #FluidSolidInteraction).

    And this hard dependency has been a *pain*.

    We first had issues in the Maxwell architecture era, which stalled our work for months because all simulations would consistently lead to a hardware lock-up
    github.com/NVIDIA/thrust/issue
    and a few years later we had another issue —luckily one we could work around within GPUSPH this time:
    github.com/NVIDIA/thrust/issue

    5/

    #gpusph #fsi #fluidstructureinteraction #fluidsolidinteraction
  5. Giuseppe Bilotta @[email protected] ·

    I believe our approach to “develop what we need when we need it”, which has been a staple in the development of #GPUSPH, has been a strong point. We *do* depend on a few external dependencies, but most of the code has been developed “in-house”.

    Fun fact: the only “hard dependency” for GPUSPH is NVIDIA's Thrust library, which we depend on for particle sorting (and in a few other places, but for optional features, like the segmented reductions used to collect body forces when doing #FSI i.e. #FluidStructureInteraction aka #FluidSolidInteraction).

    And this hard dependency has been a *pain*.

    We first had issues in the Maxwell architecture era, which stalled our work for months because all simulations would consistently lead to a hardware lock-up
    github.com/NVIDIA/thrust/issue
    and a few years later we had another issue —luckily one we could work around within GPUSPH this time:
    github.com/NVIDIA/thrust/issue

    5/

    #fluidsolidinteraction #fluidstructureinteraction #fsi #gpusph
  6. Giuseppe Bilotta @[email protected] ·

    I believe our approach to “develop what we need when we need it”, which has been a staple in the development of #GPUSPH, has been a strong point. We *do* depend on a few external dependencies, but most of the code has been developed “in-house”.

    Fun fact: the only “hard dependency” for GPUSPH is NVIDIA's Thrust library, which we depend on for particle sorting (and in a few other places, but for optional features, like the segmented reductions used to collect body forces when doing #FSI i.e. #FluidStructureInteraction aka #FluidSolidInteraction).

    And this hard dependency has been a *pain*.

    We first had issues in the Maxwell architecture era, which stalled our work for months because all simulations would consistently lead to a hardware lock-up
    github.com/NVIDIA/thrust/issue
    and a few years later we had another issue —luckily one we could work around within GPUSPH this time:
    github.com/NVIDIA/thrust/issue

    5/

    #gpusph #fsi #fluidstructureinteraction #fluidsolidinteraction