Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

JOSS paper on ECCE 9

Offen
  • Stimmt etwas nicht?
#271 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Dokumentation
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Bereich
documentation

Rechercherichtung

Before drafting, verify the PNNL ECCE publications and real references, confirm co-authorship and permission for teaching-use evidence, and decide whether to wait for the Umeå lab evidence. Follow the linked JOSS paper format and policies; gather evidence for the outline, then draft within JOSS’s word and section requirements. Done when the manuscript and figure meet those requirements and all claims and references have been verified by the authors.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

A paper in the Journal of Open Source Software, submitted after 9.0 leaves beta (reviewers install and test the software). JOSS: 750–1,750 words; required sections Summary, Statement of need, State of the field, Software design, Research impact statement, AI usage disclosure (format, policies).

Outline

Section ~Words Content
Summary 150 what a quantum-chemistry calculation is; what ECCE does (build, set up for several codes, run locally or on a cluster, keep calculations with results, view orbitals/spectra/geometries); free on Linux, Windows, macOS
Statement of need 250 researchers using several codes and clusters; teaching (students build, run and inspect calculations); one interface and data store; ECCE-QM for teaching without installs
State of the field 300 fair, sourced comparison (Avogadro, Gabedit, IQmol, Jmol/ChimeraX, WebMO, SEAMM, commercial front ends); build-vs-contribute: reviving the original design (code registration, managed data, central server)
Software design 400 code registration; client/server split and local mode; modernisation without a rewrite (2013 behaviour as reference, seven bundled libraries replaced); ECCE-QM (libcint + libxc); verification (teaching set, CI on three systems)
Research impact 250 evidence only: PNNL-era use and publications, NWChem's GUI; teaching use (with permission); releases, downloads, packages, Zenodo DOI; regression suite
AI usage disclosure 150 Claude (model/version), where used (code, tests, documentation, manuscript drafting), kind of help, human review and validation, design decisions by the authors
Acknowledgements 50 PNNL/EMSL's original team and DOE funding; testers

One figure: the client/server/compute diagram, or a composite screenshot.

Before drafting: PNNL's ECCE publications (real references only); co-authorship and permission to cite teaching use; whether to wait for the Umeå lab as evidence.

AI rules (JOSS): drafting with AI is allowed and disclosed. The authors verify every claim and reference and are responsible for them. Replies to editors and reviewers in the review thread are written by the authors themselves (AI only for translation); code and paper changes requested in review may be made with AI help as before. Related: #250 (citation).

Vorherrschende Sprache
C
Sterne
10
Forks
8
Ø Merge
21 Min.
Gemergte PRs (30 T.)
1

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus FriendsofECCE/ECCE

Alle Issues in FriendsofECCE/ECCE

Ähnliche Issues

Weitere Issues zu C

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.