MO diagram: phase sketches for ligands of several atoms and for 3-D ligand sets (Oh, Td)
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- c
调研方向
Start with the overlap scenes in tests/modiagram/capture.py and inspect how phase sketches are drawn for single element fragments. Implementations need to place signs at ligand donor atoms and show 3-D Oh and Td arrangements in oblique views while keeping planar sets flat. Done means the specified sigma and pi combinations for Cr(CO)6 and CoCl4(2-) match the cited textbook drawings, and rows accommodate larger sketches.
由索引模型根据 Issue 内容生成。
描述
Phase sketches (the small drawings of a ligand set's signs beside the fragment column) are drawn only for a fragment of one element, flattened onto the atoms' own plane. So the (CO)6 combinations of Cr(CO)6 get none, nor do CN-, NH3, H2O or PR3 ligands. The flattening also cannot show an octahedral or tetrahedral set: the axial ligands land on the equatorial ones.
Design
- One point per ligand: a ligand made of several atoms is drawn at its donor atom (C of CO and CN-, N of NH3, P of PR3, O of H2O). Sign and size come from that atom's coefficient in the set's orbital: s and p along the M–L axis for sigma sets, the p vector perpendicular to it for pi sets.
- 3-D sets drawn in the textbook oblique view: axial ligands up and down, the equatorial four on a slanted square for Oh; the matching cube or tetrahedron view for Td. Planar sets (BF3, PtCl4) stay flat as now.
- Room: a row carrying one of the larger sketches gets the height it needs; the overlap scenes in
tests/modiagram/capture.pycheck it.
Checks: for Cr(CO)6 and CoCl4(2-) the sketches must reproduce the textbook sigma combinations (a1g, eg, t1u in Oh; a1, t2 in Td) and the t2g/t1u pi sets, compared against the drawings in Albright–Burdett–Whangbo, Cotton, and Vincent.
- 主要语言
- C
- 星标
- 10
- 派生
- 8
- 平均合并
- 21 分钟
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
FriendsofECCE/ECCE 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 70/100
FriendsofECCE/ECCE#336 · 1 条评论 ·
-
难度 5/5 一周以上 新手友好度 35/100
FriendsofECCE/ECCE#370 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 48/100
FriendsofECCE/ECCE#369 · 2 条评论 ·
-
难度 5/5 一周以上 新手友好度 25/100
FriendsofECCE/ECCE#367 · 2 条评论 ·
-
难度 5/5 一周以上 新手友好度 35/100
FriendsofECCE/ECCE#366 ·
查看 FriendsofECCE/ECCE 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
FujiNetWIFI/fujinet-firmware#2079 ·
维护者通常 1 天内回复
-
bug
难度 1/5 1 小时以内 新手友好度 84/100
VirusTotal/yara#2255 ·
-
难度 2/5 1-3 小时 新手友好度 66/100
-
state:needs triage
难度 2/5 1-3 小时 新手友好度 78/100
zed-industries/zed#65836 · 1 个 reaction ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
neutralinojs/neutralinojs#1861 ·
维护者通常 1 天内回复