Building of TSs with reactant and product species geometries
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start with the proposed entry points autotst.reaction and autotst.conformer.systematic, then review how optimized geometries, bounds matrices, and conformer analysis are currently handled. The work is done when optimized reactant and product geometries can be read or generated with a warning, TS construction uses tighter bounds for bound atoms, and conformer analysis covers rotatable torsions without cis/trans bonds or chiral centers.
Written by the indexing model from the issue text.
Description
Conformational changes like inversion of chiral centers and rotation about double bonds rarely occur when reactants go to TSs (e.g. a reactant containing a cis double bond will probably have a TS with that corresponding double bond being cis). This is similar to the templating idea proposed in #33, but with a variation. I'm proposing that we do the following when building a TS geometry:
- Read in QM optimized geometries, if they exist, for reactants and products.
- Perform conformer analysis and QM optimization for reactants and products that have no optimized geometries and read them in.
- Using optimized geometries for reactants and products, construct a TS geometry using a tighter bounds matrix for bound atoms (because we trust these values)
- Perform a conformer analysis on rotatable torsions only because cis/trans bonds and chiral centers probably won't invert.
This would require us to do the following:
- Create a database of optimized geometries for autotst.reaction to read from
- Possibly build the geometry with RDKit if a reactant or product geometry isn't available but post a warning.
- Revise the way the bounds matrix is edited in autotst.reaction
- Revise the conformer analysis in autotst.conformer.systematic to not include cit/trans bonds and chiral centers
- Dominant language
- Python
- Stars
- 51
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ReactionMechanismGenerator/AutoTST
-
ReactionMechanismGenerator/AutoTST#94 · 2 comments · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
ReactionMechanismGenerator/AutoTST#91 · 2 comments ·
-
How to run AutoTST Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
ReactionMechanismGenerator/AutoTST#81 · 3 comments ·
-
log to TS Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ReactionMechanismGenerator/AutoTST#73 · 1 comment ·
All issues in ReactionMechanismGenerator/AutoTST
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100