physics
Here are 2,520 public repositories matching this topic...
-
Updated
Oct 14, 2020 - JavaScript
-
Updated
Jun 21, 2020
-
Updated
Oct 19, 2020 - PureScript
-
Updated
Jan 23, 2019 - JavaScript
Hey all,
I am curious if support exists, or will in the future, for the loading of URDF, SDF and/or MJCF model files into nphysics. This functionality would make nphysics highly desirable for simulating robotics and help Rust expand into the robotics world in general. This is something I could potentially help with if there agreement to support such model files.
Perhaps the library is still
Explain what you would like to see improved
We had CI builds stuck in downloading dependencies, e.g. VecCore. That should timeout.
Optional: share how it could be improved
Add the TIMEOUT parameter to all ExternalProject calls downloading sources.
-
Updated
Oct 18, 2020
Adding multiple ContactMaterials to the World is useful for unique contact equation properties between two specific Materials
const material1 = new CANNON.Material({ name: 'ElasticMaterial1', friction: 0, restitution: 1 })
const material2 = new CANNON.Material({ name: 'ElasticMaterial2', friction: 0.2, restitution: 0.9 })
const contactMaterial = new CANNON.ContactMaterial(material1, ma-
Updated
Oct 19, 2020 - C++
-
Updated
Oct 4, 2020 - Python
Cleanup bit flags
We have quite a few common booleans we use in many places of the code.
Some of them are very simple, like checking for compressible vs incompressible, or for FSI.
But when we want to express something more complicated like is it SA or SST, is the mesh moving or deforming, is this FEM or FVM or FEA, and so on, things are not so simple anymore and we end up with long conditionals repeated in many
-
Updated
Jul 17, 2020 - C
-
Updated
Oct 20, 2020 - TypeScript
-
Updated
Oct 20, 2020 - Python
-
Updated
Oct 17, 2020 - C++
-
Updated
Apr 5, 2020 - C#
-
Updated
Jun 16, 2020 - C++
Exchange a package that is marked as deprecated.
Seen in CI as warning in the apt install step with CUDA 10.1.243.
To Do:
- double check this works with CUDA 9.2 (current docker image; check minimal version constraint for Nvidia NGC) or...
- update Docker image to newer CUDA
-
Updated
Apr 1, 2020 - Python
-
Updated
Jul 28, 2020
-
Updated
Mar 11, 2019 - JavaScript
Hello,
There seem to be an issue in template recognition when creating mappings involving Rigid3d DoFs.
Namely, when creating a BarycentricMapping or a BeamLinearMapping between a mechanical model and a collision model of connected beam elements, I receive the following error messages:
`[ERROR] [InfoComponent(Not created (BarycentricMapping))] Object type BarycentricMapping<Vec3d,Rigid3
-
Updated
Oct 17, 2020 - Python
Improve this page
Add a description, image, and links to the physics topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the physics topic, visit your repo's landing page and select "manage topics."
Links to all modules are broken because of renaming
Version:
Issue type: