Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

refactor(ets): follow-ups to fixjoint (#740)

未关闭
#825 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
52/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
python

调研方向

Start by comparing fixjoint in ETS.py and ETS2.py, then read BaseETS in ets/_ETS.py and the existing tests to understand shared behavior and joint indexing. Update the named ETS and IK documentation pages as needed. Done means the shared implementation and tests cover the requested edge cases, the docstring and documentation are updated, and the locked-joint IK example is included.

由索引模型根据 Issue 内容生成。

描述

enhancement help wanted

Follow-up to #740, which added ETS.fixjoint and ETS2.fixjoint (closes #724). The feature works and is tested; these are the tidy-ups found in review, none of them blocking.

Help wanted, all small:

  • fixjoint is the same code in ETS.py and ETS2.py. Move it once into BaseETS (ets/_ETS.py), with the tests shared, so a fix is made in one place.
  • Add a worked example to the docstring, under .. runblock:: pycon, showing a flipped joint, unit="deg", and a robot's ets() with a joint fixed. Add .. versionadded:: too.
  • Add fixjoint to the Modification tables on the ETS documentation pages (docs/source/ets_3d.rst and ets_2d.rst) and to the lists of members in the Details sections.
  • Reject a bool as the joint index. isinstance(True, int) is true, so fixjoint(True, 0.1) currently fixes joint 1.
  • Check what happens to a joint with explicit jindex values that leave a gap after fixing (the surviving indices are kept, as for split), and say so in the docstring; this ties in with #803, where jindices that are not a permutation of 0..n-1 are not handled consistently.
  • Use it: an IK example that solves a 7-joint arm with one joint locked, in the IK documentation.
主要语言
C++
星标
3.5k
派生
639
平均合并
1 天 8 小时
30 天内合并 PR
113

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

petercorke/robotics-toolbox-python 的其他 Issue

查看 petercorke/robotics-toolbox-python 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。