ProjectPhysX / ProjectPhysX/FluidX3D
Coriolis force implementation
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 5.3k
- Forks
- 472
- PR merge metrics
- No merged PRs in 30d
Description
Hi! I wonder is there any more optimal way to model the Coriolis force than rhis
while (true) { // main simulation loop
lbm.u.read_from_device();
for (uint z = 1u; z < Nz - 1u; z++) {
for (uint y = 1u; y < Ny-1u; y++) {
for (uint x = 1u; x < Nx - 1u; x++) {
const uint n = x + (y + z * Ny) * Nx;
lbm.F.x[n] = -Co * lbm.u.y[n];
lbm.F.y[n] = Co * lbm.u.x[n];
lbm.F.z[n] = 0.0f;
}
}
}
lbm.F.write_to_device();
lbm.run(1u);
}
It slows down a thousand times :(
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the simulation loop shown in the issue and trace lbm.u.read_from_device(), lbm.F.write_to_device(), and lbm.run(1u). Measure the individual transfer and loop costs, then compare possible implementation approaches while preserving the Coriolis force behavior. Done means the force is modeled correctly without the reported severe slowdown, supported by a reproducible benchmark.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- hpc, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100