mujoco

bootc-image-builder and Native Containers and ublue-os/image-template, ublue-os/akmods, ublue-os/toolboxes w/ "quadlets and systemd" (and tini is already built-in to Docker and Podman) though ublue/bazzite has too many patches for a robot: > ostree native containers are bootable host images that can also be built and signed with a SLSA provenance attestation; https://coreos.github.io/rpm-ostree/container/ SBOM tools can scan hosts, VMs, and containers to identify software versions and licenses for citation and attribution. (CC-BY-SA requires Attribution if the derivative work is distributed. AGPL applies to hosted but not necessarily distributed derivative works. There's choosealicense.com , which has a table of open source license requirements in an Appendix: https://choosealicense.com/appendix/ ) BibTeX doesn't support schema.org/SoftwareApplication or subproperties of schema:identifier for e.g. the DOI URN of the primary schema.org/ScholarlyArticle and it's :funder(s). ... ROS on devices, ROS in development and simulation environments; Conda-forge and RoboStack host ROS Robot Operating System as conda packages. RoboStack/ros-noetic is ROS as conda packages: https://github.com/RoboStack/ros-noetic gz-sim is the new version of gazebosim, a simulator for ROS development: https://github.com/conda-forge/gz-sim-feedstock From https://news.ycombinator.com/item?id=44372666 : > mujoco_menagerie has Mujoco MJCF XML models of various robots. Mujoco ROS-compatibility: https://github.com/google-deepmind/mujoco/discussions/990 Moveit2: https://github.com/moveit/moveit2 : > Combine Gazebo, ROS Control, and MoveIt for a powerful robotics development platform. RoboStack has moveit2 as conda packages with clearly-indicated patches for Lin/Mac/Win: ros-noetic-moveit-ros-visualization.patch: https://github.com/RoboStack/ros-noetic/blob/main/patch/ros-... ... Devcontainer.json has been helpful for switching between projects lately. devcontainer.json can reference a local container/image:name or a path to a ../Dockerfile. I personally prefer to build a named image with a Makefile, though vscode Remote Containers (devcontainers extension) can build from a Dockerfile and, if the devcontainer build succeeds, start code-server in the devcontainer and restart vscode as a client of the code-server running in the container so that all of the tools for developing the software can be reproducibly installed in a container isolated from the host system. It looks like it's bootc or bootc-image-builder for building native container images? bootc-image-builder: https://github.com/osbuild/bootc-image-builder

iles/ErinCatto_SoftConstraints_GDC2011.pd... Furthermore, impulse/velocity-level LCP based constraint solving can be combined with finite element method (FEM) or mass-spring based deformable contact solving if higher-accuracy contact and friction modeling is needed.