AutoDock-GPU
FluidX3D
| AutoDock-GPU | FluidX3D | |
|---|---|---|
| 2 | 53 | |
| 349 | 3,210 | |
| 2.3% | - | |
| 6.6 | 8.6 | |
| 2 months ago | 3 days ago | |
| C++ | C++ | |
| GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
AutoDock-GPU
- Is there any current way to do molecular docking in MacOS?
-
Non organic ligand in AutoDock
I think you receive dumped output. I guess it will be solved by the newer versions of Autodock. Try optimized source code instead of the binary version (probably) installed by your package manager.
FluidX3D
- FluidX3D
-
Earthquake in Japan yesterday may have shifted land 1.3 meters
Could even use this as a revers GLOBAL ORBITING SYSTEM [GoS] - Whereby a single satellite|probe dispels a lander to a planet with the Quantum Magnetic Cannister, and that QMC signals its global location to the satellite launcher, and the satellit can extrap its location based on the absolute location of the ground guys... (might need more than one ground magnet-moles?)
How can this be measured? Can fluidx3d do martian magnetics? [0]
--
[0] https://github.com/ProjectPhysX/FluidX3D
---
EDIT: "Mars does not have a magnetosphere"
ELI5: "how do electronics work when there is zero magnetic field around them? A complete antimagnetic environ?"
I've never heard any mention about making any electrical device work on a planet (such as mars) in a complete magnetically dark location?
How is there gravity on mars if there is no magnetic field for a planet, and how can mass, the size of a planet not produce magnetism/gravity if its not made of iron-sh (the RED of the planet)
ELI5, please.
-
Challenging projects every programmer should try
See my post in this thread about dimples/barnacles...
But have you seen this guys package: https://github.com/ProjectPhysX/FluidX3D
- Fast and Memory efficient lattice Boltzmann CFD software, running on all GPUs
-
What 8x AMD Instinct MI200 GPUs can do with a combined 512GB VRAM: Bell 222 Helicopter in FluidX3D CFD - 10 Billion Cells, 75k Time Steps, 71TB vizualized - 6.4 hours compute+rendering with OpenCL
Yes, I've made that super easy. You can change the VRAM capacity of your hardware as one number in the setup script and it will automatically scale the simulation up or down. See the documentation for details.
-
Need help : I' using FluidX3D, and this model is taken from the game Assetto Corsa (.kn5 file) and converted in stl using blender. In blender and many stl file viewer it shows fine but when I try to use FluidX3D it shows weird lines and I don't know why. I tried using other methods to convert t
Also see this GitHub Issue on the problem: https://github.com/ProjectPhysX/FluidX3D/issues/59
-
Real time CFD with FluidX3D - Cessna 172 - 20 million cells - Titan Xp GPU
If you want to play with the software yourself, FluidX3D is on GitHub: https://github.com/ProjectPhysX/FluidX3D
-
GPUs in CFD
This is my opinion about what is happening. Production CFD solvers are really complicated and take a lot of time and energy to write. Engineers learning to use a CFD solver to get a job done is really time consuming and there are all sorts of issue that come up like actually trusting the new solver. Both of these things have really held back GPUs in this area. There are really only two ways out of this, either you write a solver from scratch and get people to adopt it (double hard) or you take an existing solver and modify it to run on GPUs (still pretty hard). The first option is very hard but ultimately the way to go in my opinion. The second option results in very poorly optimized GPU code and honestly just gives a bad name to GPU computing in my opinion. Take OpenLB for example, https://www.openlb.net/show-cases/highly-resolved-nozzle-simulation-performed-using-multi-gpu-support/. Terrible terrible performance compared to what you could get if you wrote the solver from scratch on the GPU, for example, https://github.com/ProjectPhysX/FluidX3D.
- Where to try/test (and learn) CFD models for free?
- FluidX3D: Fast, memory efficient lattice Boltzmann CFD software /w OpenCL
What are some alternatives?
cuda_memtest - Fork of CUDA GPU memtest :eyeglasses:
HPX - The C++ Standard Library for Parallelism and Concurrency
cuda-api-wrappers - Thin C++-flavored header-only wrappers for core CUDA APIs: Runtime, Driver, NVRTC, NVTX.
OpenCL-examples - Simple OpenCL examples for exploiting GPU computing
AdaptiveCpp - Implementation of SYCL and C++ standard parallelism for CPUs and GPUs from all vendors: The independent, community-driven compiler for C++-based heterogeneous programming models. Lets applications adapt themselves to all the hardware in the system - even at runtime!
McCode - The home of the McStas (neutrons) and McXtrace (x-rays) Monte-Carlo ray-tracing instrument simulation codes.
pysph - A framework for Smoothed Particle Hydrodynamics in Python
lbm - A simple full-python 2D lattice-boltzmann code
intel-extension-for-tensorflow - Intel® Extension for TensorFlow*
FsRayTracer - This project is an F# implementation of a raytracer based on the book "The Ray Tracer Challenge: A Test-Driven Guide to Your First 3D Renderer" by James Buck
OpenCL-Wrapper - OpenCL is the most powerful programming language ever created. Yet the OpenCL C++ bindings are cumbersome and the code overhead prevents many people from getting started. I created this lightweight OpenCL-Wrapper to greatly simplify OpenCL software development with C++ while keeping functionality and performance.
ADIOS2 - Next generation of ADIOS developed in the Exascale Computing Program