Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

NEB-TS / QST: warn when the reactant or product was optimised at another level of theory

Open
#468 1 comment 0 reactions 1 assignee View on GitHub

@ohlincha is already working on this.

Since Oct 23, 2026.

Assessment

This issue has not been assessed yet.

Description

Found in testing (#419, HCN -> HNC): the reactant and product were optimised in their own calculations at one level of theory, the NEB-TS calculation ran at HF/6-31G*. ORCA then reported both ends as not converged (reactant RMS force 0.030, max 0.068 Eh/bohr) and suggested free-end NEB or preopt_ends. The NEB did not converge in 169 iterations, the TS optimisation reached its cycle limit, and ORCA ended with an error in the property step (SHARK: failed to read orca.orcain.SHARKINP.tmp).

Wanted:

  1. When reactant or product come from a calculation with a different theory or basis than the TS calculation, warn (never block) in the Calculation Editor, naming both levels.
  2. Offer ORCA's preopt_ends true (re-optimise the ends at the NEB level) as a Runtype details option, and consider making it the default when the levels differ.
  3. Check separately whether the SHARK property-step error after a non-converged NEB-TS is ORCA's own behaviour or something in how ECCE runs the job.
Dominant language
C
Stars
10
Forks
8
Avg merge
57m
Merged PRs (30d)
2

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.