Example for hardware job #99
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #99 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 7 7
Lines 254 254
=========================================
Hits 254 254
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
Thanks, however from this example it is not clear when the user should really define and pass wires, e.g. is this mandatory when verbatim is set to False? What happens otherwise? |
|
Now I am puzzled, why do you need the wire names here? The online system is setting 17 qubits to etna, we can reduce it to 16. |
|
I tried running the example both with the Traceback (most recent call last):
File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "/nfs/users/tiiq/webappdaemon/src/daemon/slurm_circuit_computation.py", line 92, in <module>
main(args.job_folder)
File "/nfs/users/tiiq/webappdaemon/src/daemon/slurm_circuit_computation.py", line 66, in main
c, _ = transpiler(c)
File "/nfs/tools/qibo/lib/python3.10/site-packages/qibo/transpiler/pipeline.py", line 84, in __call__
circuit = transpiler_pass(circuit)
File "/nfs/tools/qibo/lib/python3.10/site-packages/qibo/transpiler/optimizer.py", line 23, in __call__
raise_error(
File "/nfs/tools/qibo/lib/python3.10/site-packages/qibo/config.py", line 46, in raise_error
raise exception(message)
ValueError: The circuit qubits are not in the connectivity graph.with |
|
@alecandido is this expected? |
At first sight, no. It is definitely unexpected. There has been a bug related, in which the disconnect qubits were not considered at all. But this has been found early and already solved qiboteam/qibo#1540 (though, as you can see, the reported error was the exact same...). EDIT: that code has been merged after the latest release, so the bug is only solved in |
|
Thanks, this should probably be fixed by the next release. |
|
@BrunoLiegiBastonLiegi by chance, have you tried with the new Qibo release (or previously with |
|
I think right now there is a problem with an ssl error that marco has to address, I will try again once that's solved. |
|
Ok I tried some different configurations with
Traceback (most recent call last):
File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "/nfs/users/tiiq/webappdaemon/src/daemon/slurm_circuit_computation.py", line 92, in <module>
main(args.job_folder)
File "/nfs/users/tiiq/webappdaemon/src/daemon/slurm_circuit_computation.py", line 66, in main
c, _ = transpiler(c)
File "/nfs/tools/qibo/lib/python3.10/site-packages/qibo/transpiler/pipeline.py", line 87, in __call__
circuit = transpiler_pass(circuit)
File "/nfs/tools/qibo/lib/python3.10/site-packages/qibo/transpiler/optimizer.py", line 23, in __call__
raise_error(
File "/nfs/tools/qibo/lib/python3.10/site-packages/qibo/config.py", line 46, in raise_error
raise exception(message)
ValueError: Some wire_names in the circuit are not in the connectivity graph.
|
|
@alecandido can you double check whether I am doing everything right? Because I am still getting the transpiler error above even when specifying the correct |
|
@BrunoLiegiBastonLiegi since the transpiler seems not to be invoked on the client side, are you sure that the Most likely, that's the case. But it's worth checking the simplest issues first, even if unlikely. |
|
Ok by running directly on the cluster in my environment with |
At this point, I wonder whether the version logged is related to the daemon itself, or rather the client that sent the request... |
|
The daemon is using |
|
Everything seems to be alright even with the only thing I wasn't expecting is the decomposition in |
I would say yes, by default Though the default transpiler is actually backend dependent And Qibolab 0.1 has still compilation for the So, it's not surprising. But |
As per title adds and example for running jobs on etna.