NanoSaur

What the archive contains

The repository includes STL parts for the tracks, body and other assemblies, a URDF/Xacro robot description and ROS 2 packages. It also contains meshes representing purchased boards and other components. Those component meshes are not fabrication-ready source for the electronics they represent. A complete native mechanical design, matched electronics source and configuration-specific bill of materials were not established by this review. [S004] [S009]

The project's quick-start page separates the physical build from simulation and points readers to parts, printing, assembly, hardware setup and installation guides. This review preserved that landing page, not all of its linked build artifacts. A prospective builder still needs to reconcile those instructions with the selected repository release before sourcing parts. No current complete build cost is claimed. [S011]

The preserved recipe uses Foxy and JetPack 4.6-era components

The Dockerfile identifies JetPack 4.6 and starts from a ROS 2 Foxy container tagged for L4T r32.6.1. Its build imports this repository from a Foxy branch and obtains separate robot and system-management packages. Several import entries either name moving branches or omit a revision. A saved copy of the main repository therefore does not freeze all of the code used by that build recipe. [S006] [S007]

The Compose file adds a second source of drift: the core image defaults to a latest tag, the web interface uses a main tag, and a Watchtower service checks for updates daily. For a repeatable experiment, record the actual image digests and dependency revisions used, together with the Jetson board and system image. That is an editorial preservation recommendation; no container was built, pulled or run here. [S008]

Check the launch configuration before treating it as a ready setup

The teleoperation launch file uses joy and teleop_twist_joy. In the preserved file, config_filepath is declared twice while joy_config is referenced without a corresponding declaration in that file. That source-level inconsistency needs review when assembling a working launch route. It does not establish the behavior of every external caller or container image. This review did not execute the launch file. [S010]

Code and printed parts have different terms

The root license and overview state MIT for code, while inspected Docker and launch files contain BSD three-clause notices. Preserve those individual notices rather than assuming the root label replaces them. External Jetson software, imported repositories and container images retain their own terms. [S001] [S003] [S006] [S008] [S010]

The STL directory has an explicit CC BY-NC-SA 4.0 license. Its noncommercial restriction means these printable files are not presented here as unrestricted open hardware. Availability of a printable part also does not establish dimensional accuracy or assembly success. The profile remains partial: no printing, wiring, installation, driving or autonomous behavior was tested. [S005]