{"id":"859350b2-ca81-4014-aa89-4d02919b404b","arxiv_id":"2501.01446","paper_version":1,"verdict":"REJECT","confidence":"HIGH","novelty_score":4.0,"correctness_risk":"high","formal_verification":"none","parameter_count":0,"one_line_summary":"The authors outline a structured six-step teaching approach for quantum computer programming using Docker, Qiskit, PennyLane, and D-Wave's Ocean SDK, based on their courses in Finland and Spain.","lead":"This paper proposes a six-step curriculum for teaching quantum programming courses, integrating Docker containers with three quantum SDKs: Qiskit, PennyLane, and Ocean. It is a teaching agenda for educators, but it presents no empirical data on whether the approach improves learning.","discovery_kind":"new_method","skeptic_critique":{"model":"deepseek-v4-flash","headline":"Effectiveness claim is self-admittedly untested: Section VIII-C defers comparative evaluation, so curriculum superiority is asserted, not demonstrated.","rationale":"The paper is a teaching-proposal/experience report, not a validated empirical study. The reader's weakest_assumption correctly identifies the load-bearing issue: the effectiveness claim rests on the authors' teaching experience alone. My independent read confirms this, and the manuscript's own text strengthens the concern. Section VIII-C does not merely omit evidence; it explicitly postpones the evaluation needed to support the claim. The claim in Section IV about a 'more efficient learning experience' from Docker-before-programming is a causal assertion with no measured outcome. The distinctness claim in Section VIII-B is also unsupported, but it is not the most load-bearing: even a perfectly unique curriculum is of no demonstrated value if its learning gains are unverified. I see no internal inconsistency or technical error in the proposed curriculum, but that is not enough for the central claim to stand. A controlled comparative study, or even a well-designed pre/post assessment, would be the minimal check. Until then, REJECT remains the appropriate verdict. I agree with the reader's assessment and recommend no change.","tokens_in":6550,"tokens_out":2222,"duration_ms":24008,"concrete_test":"Run a controlled comparison of the proposed six-step sequence against a baseline course covering the same frameworks without the separate Docker pre-step (or with Docker introduced later). Measure objective learning outcomes at identical time points: completion rates on standard Qiskit/PennyLane/Ocean programming tasks, quiz scores on quantum concepts, and perceived workload. If the Docker-first group does not outperform the baseline on these measures, the central benefit claim fails. If a control group is not feasible, a pre/post assessment of the next course offering would provide limited evidence, but only a controlled comparison can settle the superiority claim that Section VIII-C itself identifies as open.","verdict_should_be":"UNCHANGED","load_bearing_attack":"The central claim is that the six-step curriculum with Docker, Qiskit, PennyLane, and Ocean is a distinct and beneficial pedagogical pattern. The load-bearing condition is that this arrangement improves learning. The paper never tests this. Section IV asserts that 'By incorporating Docker into the quantum computer programming curriculum before introducing practical quantum programming concepts, instructors can provide a more efficient learning experience' — a causal claim with no supporting data. Section VIII-C explicitly states the authors 'plan to conduct an empirical evaluation and publish the preliminary results' and that a 'comparative analysis will help us determine if our approach is superior to existing methods.' This is the authors' own admission that superiority is unresolved. No learning-outcome data, control group, or validated instruments appear anywhere in the manuscript. Therefore the recommendations (Docker first, three SDKs, six-step order) rest on experience-based plausibility, not evidence. The distinctness claim is factually checkable but secondary; even if the combination is unique, the pedagogical benefit is the load-bearing part. Because the manuscript itself disclaims current empirical backing, the headline claim is unsupported as stated.","agreement_with_reader":"agree"},"referee_report":{"model":"deepseek-v4-flash","summary":"The paper describes a six-step curriculum for teaching quantum computer programming and quantum software engineering, developed collaboratively by lecturers in Finland and Spain. The proposed sequence covers quantum foundations, quantum software engineering and development lifecycles, containerization with Docker, and hands-on programming with three SDKs (Qiskit, PennyLane, and Ocean SDK). The authors claim that the curriculum structure is distinct from existing courses and that introducing Docker before practical quantum programming provides a more efficient learning experience. The manuscript is a descriptive pedagogical proposal; it contains no student learning-outcome data, no comparison with other teaching approaches, and no assessment instruments, and it explicitly defers empirical evaluation to future work in Section VIII-C.","tokens_in":6695,"tokens_out":2286,"duration_ms":25369,"significance":"If validated, the proposed pattern of combining Docker, three quantum SDKs, and a six-step sequence would be a useful, concrete resource for instructors building quantum programming courses. The paper also provides a helpful catalog of existing teaching resources and vendor-provided materials, such as the Xanadu Codebook, and it makes specific, actionable suggestions about environment setup and real-QPU access. However, the central claims of distinctness and pedagogical benefit are not supported by evidence within the manuscript; the paper is best read as an experience report or curriculum proposal rather than as a demonstrated contribution to physics education research. Its value to the community currently rests on plausibility and practical experience, not on measured outcomes.","major_comments":[{"comment":"The paper's central effectiveness claim is explicitly untested. Section IV asserts that 'By incorporating Docker into the quantum computer programming curriculum before introducing practical quantum programming concepts, instructors can provide a more efficient learning experience,' but no data, control group, learning-outcome measure, or validated instrument is presented anywhere in the manuscript. Section VIII-C then states that the authors 'plan to conduct an empirical evaluation and publish the preliminary results' and that a 'comparative analysis will help us determine if our approach is superior to existing methods.' This is an admission that superiority and efficiency have not yet been demonstrated. Because every practical recommendation in Sections IV–VII depends on this unsupported causal claim, the headline contribution of the paper is not established.","section":"§IV and §VIII-C"},{"comment":"The claim that the curriculum is 'distinct from most existing courses' and that 'we have yet to encounter a course on quantum computer programming that offers and discusses three different SDKs' is presented without any systematic survey or search methodology. This claim is factually checkable, and the manuscript provides no basis for verifying it beyond the authors' personal experience. While this issue is secondary to the effectiveness claim, it contributes to the paper's current framing as a novel contribution without supporting evidence.","section":"§VIII-B"}],"minor_comments":[{"comment":"The phrase 'simulation optimization, data processing' likely should read 'simulation, optimization, and data processing'; the current wording may confuse readers.","section":"Abstract"},{"comment":"Capitalization of 'PennyLane' is inconsistent (e.g., 'Pennylane' appears in Section III and in the Index Terms); the vendor's official spelling should be used consistently.","section":"Throughout"},{"comment":"The acronym QPU is used in the first item of the numbered list without being expanded; please define it at first use.","section":"§V"},{"comment":"The term 'codercises' is used without explanation; since it is likely a contraction of 'coding exercises,' it would help to define it on first use.","section":"§VI-A"},{"comment":"The sentence 'Our paper would greatly benefit from explicitly making the teaching materials available to a wider audience' reads as a future suggestion rather than a description of what the paper currently offers; if the authors intend to share materials, a link or repository would strengthen the contribution.","section":"§VIII-C"}],"recommendation":"reject","confidential_remarks":"The paper is a curriculum proposal with reasonable practical suggestions, but its central claims are self-admittedly unvalidated. A path to acceptance would require either an empirical study with learning-outcome data and a comparison condition, or a substantial reframing as a pedagogical proposal with clearly hedged claims and a detailed basis for the proposed ordering. Given that Section VIII-C explicitly identifies the missing evaluation as future work, the current manuscript does not meet the evidentiary standard for publication as a research contribution in this venue."},"author_rebuttal":null,"desk_editor":{"model":"deepseek-v4-flash","letter":"This paper is a concrete, hands-on curriculum proposal for teaching quantum programming with Docker, Qiskit, PennyLane, and Ocean. It is not an empirical study. The central claim of a 'more efficient learning experience' is asserted in Section IV without data, and the authors admit in Section VIII-C that they plan to conduct an empirical evaluation later. That admission is honest, but it means the paper's load-bearing recommendation rests on experience and plausibility, not evidence.\n\nWhat is genuinely useful: the six-step structure is a clear, replicable order—foundations, software engineering, containerization, then three SDKs. The practical details are valuable: setting up Docker images, using HELMI as a real QPU example, walking through D-Wave's account and SAPI token workflow, pointing to the Xanadu Codebook. An instructor looking for a template would find this helpful. The combination of three SDKs plus Docker-first is new enough to be a reasonable contribution to the teaching literature.\n\nThe soft spots are real but proportionate. The effectiveness claim is the main one, and it is untested. There is no control group, no learning outcome data, no student feedback. The distinctness claim is secondary; the authors say they haven't seen such a course, but they don't do a systematic literature search. The self-citations are not problematic per se, but the paper leans heavily on the authors' own prior work for the software engineering content.\n\nGiven the venue (physics.ed-ph), this could pass peer review if the journal accepts design-based teaching papers and the authors are willing to either soften the causal language or add some qualitative evidence from their joint teaching experience in Finland and Spain. As it stands, the abstract and Section IV overstate what is known.\n\nI would send it to review with a clear request: either produce preliminary student feedback or reframe the contribution as a proposed curriculum. The paper is a serious teaching proposal, not a serious effectiveness claim. For someone teaching quantum programming, it is worth reading. For someone looking for validated pedagogy, it isn't there yet.","headline":"A practical but unvalidated curriculum proposal: useful as an instructor's blueprint, not as evidence that the approach improves learning.","tokens_in":7244,"tokens_out":1998,"would_cite":false,"duration_ms":21821,"reading_group":"maybe","serious_thinker":"yes","would_accept_peer_review":true},"rs_alignment":null,"lean_confirmation":null,"pith_extraction":{"msc":[],"pacs":[],"model":"deepseek-v4-flash","headline":"A six-step curriculum that teaches quantum programming through three SDKs is proposed as a distinct new pedagogical pattern.","keywords":["quantum computer programming education","quantum software engineering","Qiskit","PennyLane","Ocean SDK","Docker containerization","curriculum design","quantum computing pedagogy"],"falsifier":"A controlled comparison in which equivalent student groups take a Docker-first, three-SDK course versus a direct-Qiskit course would settle the efficiency claim if the Docker-first group neither reaches working quantum programs faster nor scores higher on the same assessment; discovering an existing course that already teaches all three SDKs would settle the distinctiveness claim.","tokens_in":6337,"feed_emoji":"🎓","tokens_out":10504,"duration_ms":95397,"temperature":0.7,"pith_summary":"Quantum programming is hard to teach because students must absorb new concepts and manage fast-changing toolchains at once. This paper proposes a six-step course structure—quantum foundations; quantum software engineering and the development lifecycle; containerization with Docker; then hands-on programming with Qiskit, PennyLane, and the Ocean SDK—as a reusable pattern for university courses. The authors' central pedagogical claims are that the sequence is distinct from existing courses, since they have not seen another course presenting three different quantum SDKs side by side, and that putting Docker before hands-on programming gives a more efficient learning experience. The curriculum is grounded in the authors' teaching in Finland and Spain and is offered as a template for other instructors; they state that a comparative empirical evaluation is planned as future work.","feed_headline":"Six-step curriculum teaches quantum coding via three SDKs","feed_subtitle":"The sequence adds Docker before hands-on labs and covers Qiskit, PennyLane, and Ocean SDK side by side.","key_machinery":"The load-bearing object is the six-step curriculum sequence itself: (1) establishing the quantum foundation, (2) quantum software engineering and the quantum software development lifecycle, (3) containerization for quantum programming education, (4) programming with Qiskit, (5) programming with PennyLane, and (6) programming with the Ocean SDK. Within the sequence, Docker is the enabling mechanism: pre-configured containers give each student an identical, isolated environment before quantum code is written, which the paper argues removes setup overhead and makes later SDK labs run smoothly. The three-SDK comparison carries the breadth of the course, with each framework embodying a different style of quantum programming, and the final labs on real quantum devices carry the transfer from theory to practice.","core_discovery":"The paper's central claim is that quantum computer programming can be taught by deliberately combining one environment-management strategy—Docker containers—with three SDKs chosen to represent different quantum computing paradigms: Qiskit for gate-based circuit execution, PennyLane for hybrid quantum-classical and quantum machine learning, and Ocean for annealing-based computation. The proposed ordering builds from quantum foundations to quantum software engineering and the hybrid classical-quantum development lifecycle, moves to containerization, and only then enters SDK-specific programming. The authors maintain that this structure is distinct from most existing courses and that it gives fair, balanced exposure to the current tool landscape. They present the six steps as a pattern generalized from their own teaching experience, with an empirical comparison against other methods left explicitly to future work.","pith_inferences":["A testable extension the paper leaves implicit: if Docker-first ordering is what improves learning, students in a Docker-first section should reach their first successful quantum program measurably faster than students who install each SDK directly.","The three-SDK pattern suggests a broader curriculum principle: treat the quantum tool landscape itself as part of the subject, so the course stays relevant even when these particular frameworks are superseded.","The same Docker-first strategy could transfer to other fast-changing programming domains where environment setup, rather than language concepts, is the main source of friction."],"forward_implications":["If the six-step sequence is adopted, students master Docker-based environment setup before writing quantum code, so SDK labs start from identical working installations.","Covering Qiskit, PennyLane, and Ocean side by side gives students a direct comparison of gate-based, hybrid machine-learning, and annealing-based programming styles.","Instructors can align the six steps to available course hours and, at the containerization stage, optionally introduce orchestration and quantum serverless concepts.","Because the course includes submitting jobs to real quantum devices, students learn how to retrieve and interpret results from actual hardware rather than only simulators."],"supporting_citations":[{"why":"Supplies the Qiskit framework and the hardware access model that the fourth curriculum step uses.","marker":"[1]"},{"why":"Supplies the PennyLane framework and hybrid quantum-classical material for the fifth curriculum step.","marker":"[5]"},{"why":"Supplies the Ocean SDK and the solver tooling that the sixth step teaches.","marker":"[6]"},{"why":"Provides the quantum software engineering and development lifecycle survey on which Step 2 is built.","marker":"[18]"},{"why":"Provides the PennyLane codebook with structured lessons and exercises that the fifth step follows.","marker":"[23]"}],"fun_headline_variants":["Six steps combine Docker with three quantum SDKs","Docker plus Qiskit, PennyLane, Ocean teach quantum coding","Six-step curriculum uses Docker and three SDKs","Quantum programming course: six steps, three SDKs, one Docker","How to teach quantum coding: Docker plus three SDKs"],"cache_read_input_tokens":3200,"weakest_assumption_plain":"The practical value of the curriculum rests on the assumption that the authors' own teaching experience is sufficient evidence that this six-step order and three-SDK coverage improve learning; the paper states that a comparative empirical evaluation is still future work.","fun_headline_variants_meta":{"raw":{"variants":["Six steps combine Docker with three quantum SDKs","Docker plus Qiskit, PennyLane, Ocean teach quantum coding","Six-step curriculum uses Docker and three SDKs","Quantum programming course: six steps, three SDKs, one Docker","How to teach quantum coding: Docker plus three SDKs"]},"model":"deepseek-v4-flash","effort":"low","cost_usd":0.000512,"raw_usage":{"total_tokens":2421,"prompt_tokens":809,"completion_tokens":1612,"prompt_tokens_details":{"cached_tokens":384},"prompt_cache_hit_tokens":384,"prompt_cache_miss_tokens":425,"completion_tokens_details":{"reasoning_tokens":1529}},"tokens_in":425,"tokens_out":1612,"duration_ms":10270,"temperature":1.0,"reasoning_tokens":1529,"cache_read_input_tokens":384,"cache_creation_input_tokens":0},"cache_creation_input_tokens":0},"created_at":"2026-08-10T23:16:46.474762+00:00","model_set":{"reader":"deepseek-v4-flash"},"falsifier":"A controlled comparison in which equivalent student groups take a Docker-first, three-SDK course versus a direct-Qiskit course would settle the efficiency claim if the Docker-first group neither reaches working quantum programs faster nor scores higher on the same assessment; discovering an existing course that already teaches all three SDKs would settle the distinctiveness claim.","supporting_citations":[{"cited_title":"D-wave ocean software documentation","cited_arxiv_id":null,"evidence_quote":"Supplies the Ocean SDK and the solver tooling that the sixth step teaches."},{"cited_title":"Xana du quantum codebook,","cited_arxiv_id":null,"evidence_quote":"Provides the PennyLane codebook with structured lessons and exercises that the fifth step follows."}],"review_version":1}