Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Reaction studies: smoke test, clearer names, and what replaces DirDyVTST (2008)

Ouverte
  • Quelque chose ne va pas ?
#330 3 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
15/100
Type d'issue
Refactorisation
Clarté
Plutôt claire
Activité
Active
Stack technique
c
Domaine
desktop

Piste de recherche

Start with the GUI suite, which only checks that the Gas Phase and Condensed Phase study editors open, and with the DirDyVTST, Polyrate and MetaDyn task editors the issue names. Create each study, open every task editor, generate the input, and run a small case only where a code is installed. Done means both study types run end to end, and the DirDyVTST keep/rebuild/hide decision is recorded on the issue (see #221 and #62).

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

The two reaction study types have not been run end to end in this fork; the GUI suite only checks that their editors open.

  • Gas Phase Reaction Study: reactants, products and transition state, DirDyVTST (dirdyed) with NWChem, and the Polyrate editor for rate constants.
  • Condensed Phase Reaction Study: one Solvate task (Solvation Editor), then chained Metadynamics tasks (the MetaDyn registration: NWChem plane-wave PSPW, Car-Parrinello only).

Status of the external programs

  • DirDyVTST: last version 2008, and it is listed among the programs no longer distributed from the University of Minnesota.
  • Polyrate 17-C (2018, manual 2022): Apache 2.0. It reaches electronic-structure codes through interface programs (Gaussrate, Nwchemrate, ...). There is none for ORCA, and interfaces from before 2016 do not work with it.
  • Pilgrim 2.0 (2020): MIT, Python, the same group. It does VTST with SCT tunnelling, multi-structural VTST, dual-level ISPE and kinetic Monte Carlo. Which codes it reads still has to be checked.

To do

  1. Smoke test of both study types: create the study, open each task's editor, generate the input, and run a small case where a code is available.
  2. Names that say what is computed, e.g. "Reaction Rates (VTST)" and "Reaction in Solution (Metadynamics)".
  3. Decide between keeping DirDyVTST, rebuilding the study on Pilgrim or on Polyrate with Gaussrate (ORCA/Gaussian instead of NWChem), or hiding it. The condensed phase study could take CP2K AIMD/metadynamics as a second code (#329).

Related: #221 (DirDyVTST editor redesign), #62 (DirDyGauss).

Langage dominant
C
Étoiles
10
Forks
8
Merge moyen
21 min
PR mergées (30 j)
1

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de FriendsofECCE/ECCE

Toutes les issues de FriendsofECCE/ECCE

Issues similaires

Plus d'issues C

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.