You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm a PhD student writing a short survey on quantum circuit simulators. I want to include the quil qvm in my list, and so I've read up on its documentation and gone through the source code, but am still not clear on a couple of points:
Am I correct in understanding that the state vector or the density matrix are kept as dense arrays in memory? The abstraction over qams makes it hard to be sure of this. In other words: there's no Feynman-style path summation, correct?
Is there any source of further information on what the JIT compiler does, at a technical level?
Thank you in advance, and I'd be happy to chat via another channel if this is not the right place.
The text was updated successfully, but these errors were encountered:
Hello,
I'm a PhD student writing a short survey on quantum circuit simulators. I want to include the quil qvm in my list, and so I've read up on its documentation and gone through the source code, but am still not clear on a couple of points:
lparallel
is required inqvm.asd
, but I see no mention of parallelizing methods inlinear-algebra.lisp
. Since I'm unfamiliar with lisp, I'm guessing thatlparallel
may act behind the scenes, but I'm looking for confirmation. Edit: I'd missed the use oflparallel
in some of the algebra; see also issues Parallelization limit causes unintuitive timing benchmarks (was: Multi-thread support is unclear) #29 , Determine parallelization limit per machine #30. So the question is, in fact: is parallelization used for anything other than accelerating algebra for matrix-vector products above a certain size?qam
s makes it hard to be sure of this. In other words: there's no Feynman-style path summation, correct?Thank you in advance, and I'd be happy to chat via another channel if this is not the right place.
The text was updated successfully, but these errors were encountered: