Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Submit Qiskit results for https://metriq.info/Task/28 #33

Open
1ucian0 opened this issue Aug 30, 2023 · 4 comments
Open

Submit Qiskit results for https://metriq.info/Task/28 #33

1ucian0 opened this issue Aug 30, 2023 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@1ucian0
Copy link
Contributor

1ucian0 commented Aug 30, 2023

Once the submission for https://metriq.info/Task/25 (and related) is polished, it might be a good time for more complex tasks, such as https://metriq.info/Task/28

OPENQASM 2.0;
include "qelib1.inc";
qreg q[24];
cx q[3], q[2];
cx q[8], q[7];
cx q[14], q[13];
cx q[21], q[20];
cx q[3], q[4];
cx q[8], q[9];
cx q[14], q[15];
cx q[21], q[22];
ccx q[0], q[1], q[3];
ccx q[5], q[6], q[8];
ccx q[11], q[12], q[14];
ccx q[18], q[19], q[21];
ccx q[2], q[3], q[4];
ccx q[7], q[8], q[9];
ccx q[7], q[8], q[10];
ccx q[13], q[14], q[15];
ccx q[13], q[14], q[16];
ccx q[20], q[21], q[22];
ccx q[20], q[21], q[23];
cx q[6], q[5];
cx q[12], q[11];
cx q[19], q[18];
cx q[5], q[8];
cx q[11], q[14];
cx q[18], q[21];
ccx q[7], q[8], q[10];
ccx q[13], q[14], q[16];
ccx q[20], q[21], q[23];
ccx q[16], q[23], q[17];
ccx q[15], q[23], q[22];
ccx q[4], q[10], q[9];
ccx q[9], q[17], q[22];
ccx q[9], q[16], q[15];
ccx q[16], q[23], q[17];
ccx q[7], q[8], q[10];
ccx q[13], q[14], q[16];
ccx q[20], q[21], q[23];
cx q[5], q[8];
cx q[11], q[14];
cx q[18], q[21];
cx q[6], q[5];
cx q[12], q[11];
cx q[19], q[18];
ccx q[7], q[8], q[10];
ccx q[13], q[14], q[16];
ccx q[20], q[21], q[23];
ccx q[0], q[1], q[3];
ccx q[5], q[6], q[8];
ccx q[11], q[12], q[14];
ccx q[18], q[19], q[21];
cx q[3], q[2];
cx q[8], q[7];
cx q[14], q[13];
cx q[21], q[20];
cx q[6], q[5];
cx q[12], q[11];
cx q[19], q[18];
cx q[6], q[8];
cx q[12], q[14];
cx q[19], q[21];
cx q[4], q[6];
cx q[9], q[12];
cx q[15], q[19];
ccx q[0], q[1], q[3];
ccx q[5], q[6], q[8];
ccx q[11], q[12], q[14];
ccx q[18], q[19], q[21];
cx q[3], q[2];
cx q[8], q[7];
cx q[14], q[13];
cx q[21], q[20];
ccx q[0], q[1], q[3];
ccx q[5], q[6], q[8];
ccx q[11], q[12], q[14];
ccx q[18], q[19], q[21];
cx q[6], q[5];
cx q[12], q[11];
cx q[19], q[18];
cx q[4], q[6];
cx q[9], q[12];
cx q[15], q[19];
cx q[6], q[8];
cx q[12], q[14];
cx q[19], q[21];
cx q[1], q[0];
cx q[6], q[5];
cx q[12], q[11];
cx q[19], q[18];
x q[0];
x q[2];
x q[5];
x q[7];
x q[11];
x q[13];
cx q[3], q[2];
cx q[8], q[7];
cx q[14], q[13];
ccx q[0], q[1], q[3];
ccx q[5], q[6], q[8];
ccx q[11], q[12], q[14];
cx q[6], q[5];
cx q[12], q[11];
ccx q[7], q[8], q[10];
ccx q[13], q[14], q[16];
cx q[5], q[8];
cx q[11], q[14];
ccx q[7], q[8], q[10];
ccx q[13], q[14], q[16];
ccx q[9], q[16], q[15];
ccx q[4], q[10], q[9];
ccx q[7], q[8], q[10];
ccx q[13], q[14], q[16];
cx q[5], q[8];
cx q[11], q[14];
ccx q[7], q[8], q[10];
ccx q[13], q[14], q[16];
cx q[6], q[5];
cx q[12], q[11];
ccx q[7], q[8], q[9];
ccx q[13], q[14], q[15];
ccx q[2], q[3], q[4];
ccx q[0], q[1], q[3];
ccx q[5], q[6], q[8];
ccx q[11], q[12], q[14];
cx q[3], q[4];
cx q[8], q[9];
cx q[14], q[15];
cx q[3], q[2];
cx q[8], q[7];
cx q[14], q[13];
x q[0];
x q[2];
x q[5];
x q[7];
x q[11];
x q[13];
@karlaspuldaro
Copy link
Collaborator

@karlaspuldaro karlaspuldaro self-assigned this Oct 24, 2023
@karlaspuldaro
Copy link
Collaborator

@vprusso @WrathfulSpatula
What would the best way to submit Qiskit compilation historical results for task 28? Seems like the chart is categorized by method not by date, all 2020 results:
image

@WrathfulSpatula
Copy link

@karlaspuldaro The x-axis type is conditional: since all results are from the same exact day, there is no time series. However, if additional data points are added with "result dates" besides the original date, the chart will automatically switch to the usual time series view.

(By the way, I'm trying to approve your submissions. However, I'll be transparent: I was hacked. As the AWS server keys were on my work machine, I immediately changed them. However, it's been a few days of digging out, and I think I need to redeploy the server with new keys, again. Luckily, we're not "enterprise scale," and there will be no data loss. However, it might take a little more time.)

@karlaspuldaro
Copy link
Collaborator

@WrathfulSpatula Oh ok it makes sense now, so we can just submit more data as usual then.

And sorry to hear about the hassle, totally understand any delays. The submissions approvals are not high priority for us, the charts are always updated regardless.

@karlaspuldaro karlaspuldaro added the enhancement New feature or request label Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants