Copy ground state before passing to adiabatic evolution

[stavros11]

Fixes #824. @MatteoRobbiati indeed you are right, it is a qibojit issue.

Checklist:

• Reviewers confirm new code works as expected.
• Tests are passing.
• Coverage does not decrease.
• Documentation is updated.

[scarrazza]

Good point, thanks.

[scarrazza]

@MatteoRobbiati please let us know if this works also for you.

[codecov]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (87ed54f) 100.00% compared to head (6a8abdf) 100.00%.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #863   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           48        48           
  Lines         6370      6370           
=========================================
  Hits          6370      6370           

Flag	Coverage Δ
unittests	100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/qibo/models/evolution.py	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[MatteoRobbiati]

I confirm it works as expected also using the qibojit backend.
Thank you @stavros11!

[MatteoRobbiati]

Only to be sure it is a problem of mine: is it normal that the execution time of the #824 code requires 1sec using numpy and 2min using qibojit @stavros11?

[stavros11]

Only to be sure it is a problem of mine: is it normal that the execution time of the #824 code requires 1sec using numpy and 2min using qibojit @stavros11?

With @andrea-pasquale we have observed this issue in the past for the NumbaBackend, see for example
#839 (comment)
We suspect something is wrong but we did not investigate. I will try to have a look when I have time. This problem seems to appear only with numba, not cupy.

[MatteoRobbiati]

With @andrea-pasquale we have observed this issue in the past for the NumbaBackend, see for example #839 (comment) We suspect something is wrong but we did not investigate. I will try to have a look when I have time. This problem seems to appear only with numba, not cupy.

Ok perfect. I will have a look too with some python profiler.