General Chemistry Atoms/ionisation examples: wrong menu in one note, help lists ions that are not there, closed-shell titles say unrestricted

Open Beginner friendly
#1,018 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown
Domain
documentation

Research direction

Start with help/src/example-calculations.md, which holds the Atoms, cation and anion lists that need correcting, then find the Ne_HF_neutral note and change its Tools menu item to Energy Calculator. The input titles for He, Be, Ne, Mg and Ar need '(unrestricted)' replaced with the restricted wording, and their stored copies need the same change. Done means the menu name, the atom ranges and the ion lists match what the examples contain, and the closed-shell titles no longer say unrestricted.

Written by the indexing model from the issue text.

Description

bug

Found while writing about the Atoms, Ionisation energies and Koopmans topics:

  1. Ne_HF_neutral's note says Tools > Compare Energies gives the ionisation energy; every other note (correctly) says Tools > Energy Calculator (Compare Energies is the right-click item for same-composition sets).
  2. help/src/example-calculations.md: Atoms is described as "the neutral atoms hydrogen to argon"; it also holds Ca, Cr and Cu.
  3. The same page lists cations "lithium to neon" and anions "lithium to fluorine"; there is no boron cation or anion, and no PBE0 cations.
  4. The input titles of the closed-shell atoms He, Be, Ne, Mg and Ar say "(unrestricted)" but they ran restricted (rks), as ECCE-QM does for a closed shell; fix the titles (and the stored copies).
Dominant language
C
Stars
10
Forks
8
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FriendsofECCE/ECCE

All issues in FriendsofECCE/ECCE

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.