Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Fragments: one definition (atoms, charge, multiplicity) for paramagnetic systems, MO guesses, counterpoise, MO diagrams and QM/MM

Aberta
  • Algo errado?
#252 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
12/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Domínio
desktop

Direção de pesquisa

This is a design proposal, not a starter task: the payload names no source files, tests or entry points. Read the linked issues #132, #172, #178, #201 and #242 to see how fragments are defined today, then the Builder's atom list and selection code in the repository. Done means a fragment definition in the Builder (selection, charge, multiplicity, storage) that works for one paramagnetic example, such as a Cu(II) dimer, with generated high-spin and broken-symmetry inputs checked by running the code. Agree the design with the maintainers before writing code.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Many calculation types need parts of a molecule defined as fragments, each with its own properties. Today each feature that needs them defines its own: the MO diagram (#132, #172), fragment-orbital analysis (#201), counterpoise (#178), MD force-field parts (#242). This issue proposes one fragment definition, kept with the structure and used by all of them.

Defining fragments (Builder)

  • Select atoms in the viewer (picking, box, by molecule (connected component), by residue or by element) or in the Builder's atom list (rows, with shift/ctrl for ranges), and assign them to a numbered or named fragment. The atom list gets a Fragment column, editable there too. Show fragments by colour.
  • Per fragment: charge and spin multiplicity, plus a name.
    • Check consistency: the sum of fragment charges equals the total charge; electron count and multiplicity parity per fragment.
    • The total multiplicity follows from the fragments' spins and how they couple: ferromagnetic (high spin) or antiferromagnetic (broken symmetry). The user chooses.
  • Fragments are stored with the structure and survive saving, duplicating a calculation and editing atoms (new atoms get no fragment).

Uses

  1. Paramagnetic and broken-symmetry systems (first target). Unrestricted DFT on systems with several metal centres or radicals: a fragment guess with per-fragment charge and multiplicity, then high-spin and broken-symmetry solutions (e.g. exchange coupling J).
    • Gaussian: atom tags (Fragment=n), Guess=Fragment=N with per-fragment charge/multiplicity pairs on the charge line.
    • ORCA: atom fragment tags, ! BrokenSym M,N or %scf FlipSpin, or a fragment-based guess.
    • NWChem: fragment guess (vectors fragment) from separate fragment calculations.
    • ECCE-QM: a fragment-superposition guess with spin flips, as a later step.
  2. Initial guess from fragment MOs (with #75, basis projection): converge each fragment, combine.
  3. Counterpoise / BSSE (#178): fragments define the ghost-atom calculations (Gaussian Counterpoise=N; ORCA and NWChem via generated ghost-atom jobs).
  4. MO diagrams and fragment-orbital analysis (#132, #172, #201): fragments from this definition instead of a separate one.
  5. QM/MM and ONIOM layers: fragments marked as QM or MM region (Gaussian ONIOM, ORCA QM/MM, NWChem QM/MM); with #242 for force-field assignment of MM parts.
  6. Energy decomposition where a code supports it (e.g. ORCA LED/EDA, NWChem fragment-based methods).

First step

The fragment definition in the Builder (selection, charge, multiplicity, storage), and its use for paramagnetic systems with one code (Gaussian or ORCA): a two-centre example (e.g. a Cu(II) dimer) set up entirely in the GUI, high-spin and broken-symmetry inputs generated and checked by running the code.

Linguagem predominante
C
Estrelas
10
Forks
8
Merge médio
2h 7min
PRs com merge (30d)
4

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de FriendsofECCE/ECCE

Todas as issues de FriendsofECCE/ECCE

Issues semelhantes

Mais issues de C

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.