Skip to content

PQID: QuYAML parser reuse terms and related QEnergic notice #1

Description

@Elias-Abebe-Gasparini

Hello Ahmed,

I am Elias Abebe Gasparini from the Human and Artificial Intelligence Research (HAIR) Laboratory, Yonsei University. PQID pairs source-derived Qiskit code with LLM-generated instructions for quantum-programming research, model training and evaluation. Our manuscript is in revision at Scientific Data. We document source versions, licensing and attribution as part of our Open Science work, keeping generated text distinct from source-author code.

Our QThink review concerns quyaml_parser.py, Git blob 0ba7c0fae33a3f71059c994e632fdd6653882fb4, which matches the current file. I could not locate reuse terms in the README, parser or repository tree. Could you identify or document the applicable licence or permission terms for adapting and publicly redistributing implementation and comment excerpts in PQID for research, model training and evaluation? Please flag any third-party portions and required contributor credit for this parser.

There is also one concrete notice question for your QEnergic repository: its README states MIT License and requests the Farhani et al. GECCO 2026 paper citation, which we have recorded. For generate_plots.py, Git blob edc60a30f0ee29d0aefef2d27e1082a4a5f3d200 (also matching the current file), where can we find the accompanying MIT copyright/licence notice to preserve with code excerpts? I could not locate that notice in the file or a separate licence file.

These are file-content hashes, not commit IDs. The scope is these two implementations and their comments, excluding the Ethiopia site data, papers, generated figures and dependency code.

Thank you,
Elias Abebe Gasparini
HAIR Laboratory, Yonsei University

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions