How twiniars/meros works
Project type and purpose
• Its purpose is to define a standardized metamodel (groups of ROS concepts) and to produce human-readable artifacts (documentation, tutorial, poster) that robotics engineers and students can use with SysML tools (e.g., Visual Paradigm).
File structure
• Top-level:
· doc/ – release procedures and thesis guidance (Markdown)
· src/ – all the source artifacts:
• img/ – graphical abstract, requirement packages, profiles, tutorial assets
• turtlesim-doc/ – concrete tutorial example in LaTeX
• meros-stereotypes.tex, meros.bib – core SysML profile definitions and bibliography
• Configuration & automation:
· GitHub Actions workflow (dependent-issues.yml)
· .gitignore, LICENSE, README.md, Tutorial.md
Key insights from README
• Core deliverable: a SysML‐based metamodel for ROS, with grouping concepts and multiple levels of detail.
• Outputs include a PDF documentation, a poster, and practical tutorials.
• Integrates with standard SysML tools for authoring and viewing.
Main components and their relationships
a. Source Artifact Layer
• LaTeX sources (.tex, .bib) for documentation & tutorials
• SysML project files (.vpp) and stereotype XML for the metamodel
b. Toolchain & Build Layer
• LaTeX compiler(s) to produce PDFs
• Visual Paradigm / SysML modeling tool that reads .vpp and XML stereotypes
• GitHub Actions for CI: auto‐build docs or validate dependencies
c. Publication & Distribution Layer
• GitHub Releases (artifact storage: documentation PDF, poster PDF)
• GitHub Pages or raw assets for image embedding
d. Consumer / Integration Layer
• Robotics engineers using ROS and SysML tools
Architectural patterns & design principles
• “Source→Build→Publish” pipeline pattern: clear separation of editable sources, automated build, and published artifacts.
• Modularity: documentation, metamodel, tutorial each in its own sub-folder.
Essential architectural elements
• The distinct separation between metamodel sources, documentation sources, toolchain, and output artifacts.
• The role of external SysML tooling (Visual Paradigm) as both a consumer and validator of the metamodel.