Skip to content

History / Tips for working with Dummy Atoms

Revisions

  • Drop pinned version numbers from the wiki so pages do not go stale

    @HiroYokoyama HiroYokoyama committed Aug 7, 2026
    3e7670c

  • Apply house style to remaining Tips pages; fix Official-Plugins link Tips-for-2D-to-3D-conversion(-JP): retitle to match page name, sentence-case headings, See also section. Tips-for-working-with-Dummy-Atoms: rewrite in house style, verified PLUGIN_SUPPORTED_MOLEDITPY_VERSION against the actual XYZ_Editor plugin source, fix the dead Official-Plugins link. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

    @HiroYokoyama HiroYokoyama committed Aug 5, 2026
    44bffdf

  • Expand force-field tips with backend/menu locations; fix stale dummy-atom version claim Tips-for-force-field-selection: added where the force field is actually chosen (Settings > 3D Optimization Settings, Constrained Optimization dropdown, Optimize 3D right-click), the full RDKit vs Open Babel force field lists (GAFF/Ghemical are Open Babel-only), the Linux caveat (moleditpy-linux has no Open Babel), and the automatic MMFF->UFF fallback behavior for unsupported elements. JP kept in sync. Tips-for-working-with-Dummy-Atoms: "MoleditPy: Version 2 or higher" was meaningless boilerplate (current release is 4.5.1). Replaced with the XYZ Editor plugin's actual declared compatibility range (PLUGIN_SUPPORTED_MOLEDITPY_VERSION = ">=4.0.0, <5.0.0", checked against moleditpy-plugins/plugins/XYZ_Editor/xyz_editor.py) and linked to the new Using-Plugins/Official-Plugins pages. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

    @HiroYokoyama HiroYokoyama committed Aug 4, 2026
    746222f

  • Updated Tips for working with Dummy Atoms (*) (markdown)

    @HiroYokoyama HiroYokoyama committed Feb 26, 2026
    7bca394