Dev

.github/workflows/ci.yml

@@ -0,0 +1,120 @@
+name: CI
+
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+      - master
+      - dev
+
+jobs:
+  build-and-test:
+    name: Build and test (thais_urdf)
+    runs-on: ubuntu-latest
+    container:
+      image: osrf/ros:humble-desktop
+    # Colcon tree must live next to the checkout, not under it: copying $GITHUB_WORKSPACE
+    # into workspace/ws/... would copy a directory into its own subtree ("cannot copy into itself").
+    # COLCON_WS must be canonical (no ..): upload-artifact@v4 rejects paths with relative segments.
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set COLCON_WS
+        run: |
+          echo "COLCON_WS=$(cd "${GITHUB_WORKSPACE}/.." && pwd)/colcon_ws" >> "${GITHUB_ENV}"
+
+      - name: Install tooling
+        run: |
+          apt-get update && apt-get install -y --no-install-recommends \
+            python3-rosdep \
+            python3-pytest \
+            python3-pytest-cov \
+            python3-yaml \
+            build-essential \
+            cmake \
+            git
+          # Do not rm -rf /var/lib/apt/lists/* here; rosdep uses apt next and needs indexes.
+          rosdep init || true
+          rosdep update
+
+      # Full-stack tests with lucy_ros2_control belong in the lucy_ros_packages repo once
+      # lucy_ros2_control is on the default branch there; this repo only declares runtime
+      # integration with that package, not a test_depend.
+      - name: Workspace layout
+        run: |
+          set -e
+          mkdir -p "${COLCON_WS}/src"
+          cp -a "${GITHUB_WORKSPACE}" "${COLCON_WS}/src/thais_urdf"
+
+      - name: rosdep install
+        working-directory: ${{ env.COLCON_WS }}
+        shell: bash
+        run: |
+          set -e
+          apt-get update
+          source /opt/ros/humble/setup.bash
+          rosdep install --from-paths src --ignore-src -r -y
+
+      - name: colcon build
+        working-directory: ${{ env.COLCON_WS }}
+        shell: bash
+        run: |
+          source /opt/ros/humble/setup.bash
+          colcon build --symlink-install \
+            --packages-select thais_urdf \
+            --cmake-args -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTING=ON
+
+      - name: colcon test
+        working-directory: ${{ env.COLCON_WS }}
+        shell: bash
+        run: |
+          source /opt/ros/humble/setup.bash
+          source install/setup.bash
+          colcon test \
+            --packages-select thais_urdf \
+            --event-handlers console_direct+ \
+            --pytest-args "--tb=short -vv"
+
+      - name: colcon test-result
+        working-directory: ${{ env.COLCON_WS }}
+        shell: bash
+        run: |
+          source /opt/ros/humble/setup.bash
+          source install/setup.bash
+          colcon test-result --verbose
+
+      - name: Code coverage (pytest-cov)
+        working-directory: ${{ env.COLCON_WS }}
+        shell: bash
+        if: success()
+        run: |
+          set -e
+          source /opt/ros/humble/setup.bash
+          source install/setup.bash
+          mkdir -p build/coverage_reports
+          python3 -m pytest src/thais_urdf/test/ \
+            --cov=src/thais_urdf/launch \
+            --cov=src/thais_urdf/test \
+            --cov-report=xml:build/coverage_reports/thais_urdf.xml \
+            --cov-report=html:build/coverage_reports/html_thais_urdf \
+            --cov-report=term-missing \
+            --cov-branch
+
+      - name: Upload coverage to Codecov
+        uses: codecov/codecov-action@v4
+        if: success()
+        with:
+          token: ${{ secrets.CODECOV_TOKEN }}
+          files: ${{ env.COLCON_WS }}/build/coverage_reports/thais_urdf.xml
+          flags: thais_urdf
+          name: thais_urdf
+          fail_ci_if_error: false
+
+      - name: Upload coverage artifacts (XML + HTML)
+        uses: actions/upload-artifact@v4
+        if: always()
+        with:
+          name: coverage-thais_urdf
+          path: ${{ env.COLCON_WS }}/build/coverage_reports/
+          retention-days: 14

.gitignore

@@ -49,3 +49,6 @@ qtcreator-*
 
 # Catkin custom files
 CATKIN_IGNORE
+
+*.log
+.DS_Store

CMakeLists.txt

@@ -0,0 +1,20 @@
+cmake_minimum_required(VERSION 3.8)
+project(thais_urdf)
+
+find_package(ament_cmake REQUIRED)
+
+install(
+  DIRECTORY launch config inmoov
+  DESTINATION share/${PROJECT_NAME}/
+)
+
+if(BUILD_TESTING)
+  find_package(ament_cmake_pytest REQUIRED)
+  find_package(ament_lint_auto REQUIRED)
+  ament_lint_auto_find_test_dependencies()
+  ament_add_pytest_test(xacro_smoke test/test_xacro_smoke.py
+    TIMEOUT 180
+  )
+endif()
+
+ament_package()

CONTRIBUTING.md

@@ -1,154 +1,8 @@
-<!-- omit in toc -->
-# Contributing to Title
+Any contribution that you make to this repository will
+be under the GNU General Public License, as dictated by that
+[license](https://opensource.org/licenses/GPL-3.0).
 
-First off, thanks for taking the time to contribute! ❤️
+# More information
 
-All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
-
-> And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
-> - Star the project
-> - Tweet about it
-> - Refer this project in your project's readme
-> - Mention the project at local meetups and tell your friends/colleagues
-
-<!-- omit in toc -->
-## Table of Contents
-
-- [Code of Conduct](#code-of-conduct)
-- [I Have a Question](#i-have-a-question)
-  - [I Want To Contribute](#i-want-to-contribute)
-  - [Reporting Bugs](#reporting-bugs)
-  - [Suggesting Enhancements](#suggesting-enhancements)
-  - [Your First Code Contribution](#your-first-code-contribution)
-  - [Improving The Documentation](#improving-the-documentation)
-- [Styleguides](#styleguides)
-
-
-## Code of Conduct
-
-This project and everyone participating in it is governed by the
-[Code of Conduct](CODE_OF_CONDUCT.md).
-By participating, you are expected to uphold this code. Please report unacceptable behavior
-to [contact@sentience-robotics.fr](mailto:contact@sentience-robotics.fr).
-
-
-## I Have a Question
-
-> If you want to ask a question, we assume that you have read the available [Documentation](https://docs.sentience-robotics.fr).
-
-Before you ask a question, it is best to search for existing [Issues](https://github.com/Sentience-Robotics/<project>/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
-
-If you then still feel the need to ask a question and need clarification, we recommend the following:
-
-- Open an [Issue](https://github.com/Sentience-Robotics/<project>/issues/new).
-- Provide as much context as you can about what you're running into.
-- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
-
-We will then take care of the issue as soon as possible.
-
-<!--
-You might want to create a separate issue tag for questions and include it in this description. People should then tag their issues accordingly.
-
-Depending on how large the project is, you may want to outsource the questioning, e.g. to Stack Overflow or Gitter. You may add additional contact and information possibilities:
-- IRC
-- Slack
-- Gitter
-- Stack Overflow tag
-- Blog
-- FAQ
-- Roadmap
-- E-Mail List
-- Forum
--->
-
-## I Want To Contribute
-
-> ### Legal Notice <!-- omit in toc -->
-> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project licence.
-
-### Reporting Bugs
-
-<!-- omit in toc -->
-#### Before Submitting a Bug Report
-
-A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
-
-- Make sure that you are using the latest version.
-- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://docs.sentience-robotics.fr). If you are looking for support, you might want to check [this section](#i-have-a-question)).
-- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/Sentience-Robotics/<project>/issues?q=label%3Abug).
-- Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
-- Collect information about the bug:
-  - Stack trace (Traceback)
-  - OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
-  - Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
-  - Possibly your input and the output
-  - Can you reliably reproduce the issue? And can you also reproduce it with older versions?
-
-<!-- omit in toc -->
-#### How Do I Submit a Good Bug Report?
-
-> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to [security@sentience-robotics.fr](mailto:security@sentience-robotics.fr).
-
-We use GitHub issues to track bugs and errors. If you run into an issue with the project:
-
-- Open an [Issue](https://github.com/Sentience-Robotics/<project>/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
-- Explain the behavior you would expect and the actual behavior.
-- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
-- Provide the information you collected in the previous section.
-
-Once it's filed:
-
-- The project team will label the issue accordingly.
-- A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Bugs with the `needs-repro` tag will not be addressed until they are reproduced.
-- If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](#your-first-code-contribution).
-
-<!-- You might want to create an issue template for bugs and errors that can be used as a guide and that defines the structure of the information to be included. If you do so, reference it here in the description. -->
-
-
-### Suggesting Enhancements
-
-This section guides you through submitting an enhancement suggestion for Title, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
-
-<!-- omit in toc -->
-#### Before Submitting an Enhancement
-
-- Make sure that you are using the latest version.
-- Read the [documentation](https://docs.sentience-robotics.fr) carefully and find out if the functionality is already covered, maybe by an individual configuration.
-- Perform a [search](https://github.com/Sentience-Robotics/<project>/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
-- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
-
-<!-- omit in toc -->
-#### How Do I Submit a Good Enhancement Suggestion?
-
-Enhancement suggestions are tracked as [GitHub issues](https://github.com/Sentience-Robotics/<project>/issues).
-
-- Use a **clear and descriptive title** for the issue to identify the suggestion.
-- Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
-- **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you.
-- You may want to **include screenshots or screen recordings** which help you demonstrate the steps or point out the part which the suggestion is related to. You can use [LICEcap](https://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and the built-in [screen recorder in GNOME](https://help.gnome.org/users/gnome-help/stable/screen-shot-record.html.en) or [SimpleScreenRecorder](https://github.com/MaartenBaert/ssr) on Linux. <!-- this should only be included if the project has a GUI -->
-- **Explain why this enhancement would be useful** to most Title users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
-
-<!-- You might want to create an issue template for enhancement suggestions that can be used as a guide and that defines the structure of the information to be included. If you do so, reference it here in the description. -->
-
-## Styleguides
-
-Follow these steps to contribute:
-
-- 1️⃣ **Fork** the repository<br>
-- 2️⃣ **Create a feature branch:**<br>
-    ```bash
-    git switch -C '<trigram>/#<issue>/<amzing-feature>'
-    ```
-- 3️⃣ **Commit your changes:**<br>
-    ```bash
-    git commit -sm '<feat|evol|fix>(<scope>): <amzing-feature>'
-    ```
-- 4️⃣ **Push to your branch:**<br>
-    ```bash
-    git push origin '<feat|evol|fix>/<amzing-feature>'
-    ```
-- 5️⃣ **Open a Pull Request**<br>
-
-<!-- omit in toc -->
-## Attribution
-This guide is based on the [contributing.md](https://contributing.md/generator)!
+- [Developer guide](doc/DEVELOPER.md) — workflow, CI, layout, style
+- [Code of Conduct](CODE_OF_CONDUCT.md)

InMoov-IsaacSim/meshes/stl/ATTRIBUTION.md

@@ -0,0 +1,8 @@
+# Attribution for InMoov-Derived Files
+
+The 3D models, CAD files, Blender files, and STL files in this directory are derived from InMoov by Gael Langevin.
+
+**Original Creator:** Gael Langevin  
+**Original Work:** InMoov (http://inmoov.fr/)  
+**License:** Creative Commons Attribution-NonCommercial (CC BY-NC) 4.0  
+**Modifications:** Original blender files exported to STL files split for URDF meshes

InMoov-IsaacSim/urdf/InMoov.urdf

@@ -1,4 +1,4 @@
-<robot name="InMoov" version="1.0">
+<robot name="inmoov" version="1.0">
   <joint name="Empty.001_link_joint" type="fixed">
     <origin rpy="0.00000 0.00000 0.00000" xyz="-0.00394 0.00025 -0.19163"/>
     <parent link="base_node"/>