@oqtopus-team/pi-qcaleval 0.0.0-stage → 0.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +201 -0
- package/README.md +141 -2
- package/extensions/qcaleval.ts +946 -0
- package/package.json +52 -4
- package/skills/qcaleval/SKILL.md +62 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright yyyy OQTOPUS Team
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
CHANGED
|
@@ -1,3 +1,142 @@
|
|
|
1
|
-
#
|
|
1
|
+
# pi-qcaleval
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
A [pi](https://github.com/badlogic/pi-mono) extension that sends superconducting
|
|
4
|
+
qubit calibration plots to a dedicated calibration-evaluation VLM and returns a
|
|
5
|
+
structured diagnosis. The default model is
|
|
6
|
+
[NVIDIA Ising-Calibration](https://build.nvidia.com/nvidia/ising-calibration-1.5-31b/modelcard)
|
|
7
|
+
served by vLLM, and the questions are the ones it was trained and benchmarked
|
|
8
|
+
on: the six questions of
|
|
9
|
+
[QCalEval](https://arxiv.org/abs/2604.25884), asked the way the benchmark asks
|
|
10
|
+
them.
|
|
11
|
+
|
|
12
|
+
The planner model keeps the conversation; `qcal_evaluate` is the tool it calls
|
|
13
|
+
whenever a calibration figure needs a fit-quality judgement, parameter
|
|
14
|
+
extraction, or a status verdict. The extension has no QDash dependency, so it
|
|
15
|
+
works from the pi CLI and from the QDash Copilot runtime alike.
|
|
16
|
+
|
|
17
|
+
## Tool
|
|
18
|
+
|
|
19
|
+
`qcal_evaluate(context, question?, task_name?, knowledge?, criteria?, images?, max_images?, use_examples?, examples?, questions?)`
|
|
20
|
+
asks the evaluation model six questions, each in its own single-turn request
|
|
21
|
+
(no system prompt), with the figure at the position the benchmark's templates
|
|
22
|
+
put it, and returns the parsed answers as `details.diagnosis`:
|
|
23
|
+
|
|
24
|
+
| key | the benchmark's question | parsed answer |
|
|
25
|
+
| --- | --- | --- |
|
|
26
|
+
| `technical_description` | Q1 Describe the figure in JSON | `{plot_type, x_axis, y_axis, main_features}`, or the text when not JSON |
|
|
27
|
+
| `experimental_conclusion` | Q2 Classify the outcome | `{classification: expected \| suboptimal \| anomalous \| apparatus, reason}` |
|
|
28
|
+
| `experimental_significance` | Q3 What does this result imply | text |
|
|
29
|
+
| `fit_reliability` | Q4 Is the fit reliable for extraction | `{assessment: reliable \| unreliable \| no_fit, reason}` |
|
|
30
|
+
| `parameter_extraction` | Q5 Extract parameters in JSON | the object, or the text when not JSON |
|
|
31
|
+
| `calibration_diagnosis` | Q6 Determine the status | `{status: CODE, suggested_range, notes}` |
|
|
32
|
+
|
|
33
|
+
plus `success`: whether the status is `SUCCESS` (or, when the status question
|
|
34
|
+
was not asked, whether the outcome is `expected`). `details.answers` keeps every
|
|
35
|
+
answer as returned, `details.questions` the questions asked, `details.prompt`
|
|
36
|
+
every user turn the model received (with `[figure]` where an image was), and
|
|
37
|
+
`details.calls` each question's call with its duration, stop reason, and input
|
|
38
|
+
and output tokens. A call that fails is retried once, as the benchmark retries API
|
|
39
|
+
failures; nothing is re-asked for its content. Questions that got no answer are
|
|
40
|
+
listed in `details.missing_keys`. `questions` asks a subset. `dry_run` builds
|
|
41
|
+
the prompts and returns them (`details.prompts` by question, `details.prompt`
|
|
42
|
+
as one text) without asking the model, so a host can show what a task's
|
|
43
|
+
reference and examples turn into; the figure may be omitted then.
|
|
44
|
+
|
|
45
|
+
`knowledge` is the experiment background the benchmark prepends to Q2–Q6: a few
|
|
46
|
+
sentences on what the experiment sweeps and what a successful result looks like.
|
|
47
|
+
`criteria` fills the family-specific parts of the templates: `guidance` (the
|
|
48
|
+
points Q3 should explain), `parameters` (the Q5 schema, name to type),
|
|
49
|
+
`statuses` (the Q6 decision criteria, code to criterion, `SUCCESS` first) and
|
|
50
|
+
`range_format`. A host that keeps such knowledge per task fills both in from
|
|
51
|
+
`task_name`, so the planner only names the task. Without them the templates use
|
|
52
|
+
generic guidance, ask for whatever parameters the plot determines, and offer
|
|
53
|
+
`SUCCESS` / `SUBOPTIMAL` / `NO_SIGNAL` / `ANOMALOUS`.
|
|
54
|
+
|
|
55
|
+
`context` is what the background cannot know (the task, the target, a swept
|
|
56
|
+
range); the model reads values off the plot, so do not pass fitted results. A
|
|
57
|
+
`question` is added to Q3 as one more point to address.
|
|
58
|
+
|
|
59
|
+
`images` are base64 image blocks. A host may fill them in from the most recent
|
|
60
|
+
figures of the conversation, so the planner does not have to pass image bytes;
|
|
61
|
+
`max_images` (default 1, up to 4) says how many of the newest figures to supply,
|
|
62
|
+
for example 2 when an expected reference figure precedes the measured result.
|
|
63
|
+
The last figure is the one judged; earlier ones are shown as references.
|
|
64
|
+
|
|
65
|
+
### Labeled examples (in-context)
|
|
66
|
+
|
|
67
|
+
With `use_examples`, the host supplies `examples`: each is one or more figures
|
|
68
|
+
with the answers an expert validated (`scenario`, `analysis`, `parameters`,
|
|
69
|
+
`status`, `suggested_range`). They are laid out as the benchmark's few-shot
|
|
70
|
+
split lays them out, examples first and the query figure last, and only for the
|
|
71
|
+
three questions the benchmark uses them for: Q3 shows each example's
|
|
72
|
+
`analysis` under `Scenario "<scenario>":`, Q5 shows one example's
|
|
73
|
+
`parameters`, Q6 shows each example's `Status:` and `Suggested range:`. Up to
|
|
74
|
+
six examples and six example figures are shown; the rest are dropped in order.
|
|
75
|
+
|
|
76
|
+
## Configuration
|
|
77
|
+
|
|
78
|
+
No setting is required. The evaluation model is resolved in this order:
|
|
79
|
+
|
|
80
|
+
1. the call's `model` (`provider/modelId`), when the host offers several evaluation models, then
|
|
81
|
+
`QCALEVAL_MODEL`, an explicit override for pi CLI use;
|
|
82
|
+
2. a configured calibration VLM, recognised by its id (`Ising-Calibration`);
|
|
83
|
+
3. the conversation's own model, when it accepts images. The result is then
|
|
84
|
+
marked `fallback: true` in `details`, so a host without an Ising deployment
|
|
85
|
+
still gets a diagnosis from the vision model it already runs.
|
|
86
|
+
|
|
87
|
+
The output budget per answer follows the model's `maxTokens` (at most 4096). The
|
|
88
|
+
benchmark decodes greedily; set the model's temperature to 0 for reproducible
|
|
89
|
+
answers.
|
|
90
|
+
|
|
91
|
+
The provider must be declared in pi's `models.json` with its base URL and
|
|
92
|
+
credential, for example:
|
|
93
|
+
|
|
94
|
+
```json
|
|
95
|
+
{
|
|
96
|
+
"providers": {
|
|
97
|
+
"vllm": {
|
|
98
|
+
"baseUrl": "https://llm.example/v1",
|
|
99
|
+
"api": "openai-completions",
|
|
100
|
+
"apiKey": "$VLLM_API_KEY",
|
|
101
|
+
"models": [{ "id": "nvidia/Ising-Calibration-1.5-31B-NVFP4", "contextWindow": 16384, "maxTokens": 2048, "input": ["text", "image"] }]
|
|
102
|
+
}
|
|
103
|
+
}
|
|
104
|
+
}
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
Each request carries one plot, the background and one question, so an
|
|
108
|
+
evaluation fits comfortably in a 16k-token deployment; the six requests run at
|
|
109
|
+
once.
|
|
110
|
+
|
|
111
|
+
## Installation
|
|
112
|
+
|
|
113
|
+
```bash
|
|
114
|
+
pi install npm:@oqtopus-team/pi-qcaleval
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
The package is now published as `@oqtopus-team/pi-qcaleval`. Existing pi CLI users
|
|
118
|
+
should remove `@orangekame3/pi-qcaleval` before installing the new package to avoid
|
|
119
|
+
loading both extensions. Historical releases remain available under the old name.
|
|
120
|
+
|
|
121
|
+
Releases use QDash tags `pi-qcaleval/vX.Y.Z` and publish to npm as `latest`.
|
|
122
|
+
Changes to the pi packages on QDash's `develop` branch publish `beta` prereleases
|
|
123
|
+
(`npm:@oqtopus-team/pi-qcaleval@beta`).
|
|
124
|
+
|
|
125
|
+
## Development
|
|
126
|
+
|
|
127
|
+
From the QDash repository root:
|
|
128
|
+
|
|
129
|
+
```bash
|
|
130
|
+
bun install --frozen-lockfile
|
|
131
|
+
task ci-pi-packages
|
|
132
|
+
task ci-agent-runtime
|
|
133
|
+
pi -e ./packages/pi-qcaleval
|
|
134
|
+
```
|
|
135
|
+
|
|
136
|
+
The QDash runtime includes this package from the same checkout. Rebuild it after
|
|
137
|
+
editing with `docker compose up -d --build agent-runtime`. See the
|
|
138
|
+
[package release guide](../../docs/developer-guide/copilot/packages.md).
|
|
139
|
+
|
|
140
|
+
## License
|
|
141
|
+
|
|
142
|
+
Apache-2.0
|