Make a complete table of all tasks called with romi_run_task (Specification > Tasks)
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The table could be something like this:
| Task | linked Module | brief description | typical upstream task | typical Downstream task |
|---|---|---|---|---|
| Scan | Plant Imager | image acquisition with the real robot | ? | ? |
| VirtualPlant | Virtual Plant Imager | generate a virtual plant with Lpy | ? | ? |
| VirtualScan | Virtual Plant Imager | generate virtual 2D rgb images of a virtual 3D plant | ? | ? |
| Undistorted | Plant-3d-Vision | ... | ? | ? |
| Masks | Plant-3d-Vision | ... | ? | ? |
| Voxels | Plant-3d-Vision | ... | ? | ? |
| PointCloud | Plant-3d-Vision | ... | ? | ? |
| TriangleMesh | Plant-3d-Vision | ... | ? | ? |
| TreeGraph | Plant-3d-Vision | ... | ? | ? |
| Segmentation2D | Plant-3d-Vision | ... | ? | ? |
| SegmentedPointCloud | Plant-3d-Vision | ... | ? | ? |
| ClusteredMesh | Plant-3d-Vision | ... | ? | ? |
| OrganSegmentation | Plant-3d-Vision | ... | ? | ? |
| AnglesAndInternodes | Plant-3d-Vision | ... | ? | ? |
| Visualization | Plant-3d-Explorer | ... | ? | ? |
it should integrate links to pages were the task is decribed
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the Specification > Tasks documentation and locate the pages describing each task listed in the issue. Build the requested table with linked modules, brief descriptions, and typical upstream and downstream tasks; it is done when all listed romi_run_task tasks are covered and each description links to its documentation page.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100