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

Temporary fixes to support pytorch backend migration #45

Merged
merged 3 commits into from
Nov 18, 2024

Conversation

MatteoRobbiati
Copy link
Contributor

@MatteoRobbiati MatteoRobbiati commented Oct 30, 2024

This is needed to complete the Pytorch backend migration from Qibo to Qiboml.

Copy link

codecov bot commented Oct 30, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.59%. Comparing base (50a13e2) to head (cb66755).
Report is 4 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main      #45   +/-   ##
=======================================
  Coverage   66.59%   66.59%           
=======================================
  Files          11       11           
  Lines         488      488           
=======================================
  Hits          325      325           
  Misses        163      163           
Flag Coverage Δ
unittests 66.59% <ø> (ø)

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

Files with missing lines Coverage Δ
src/qiboml/backends/__init__.py 100.00% <ø> (ø)

@BrunoLiegiBastonLiegi
Copy link
Contributor

Are these just the recent modifications added in qiboteam/qibo#1450 ?

@MatteoRobbiati
Copy link
Contributor Author

MatteoRobbiati commented Nov 5, 2024

Are these just the recent modifications added in qiboteam/qibo#1450 ?

Required for the backend migration.

Comment on lines 10 to 13
AVAILABLE_PLATFORMS = [
"tensorflow",
"pytorch",
] # temporary: to remove once pytorch and tensorflow are migrated and jax is fully working
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what's the plan here? now that we are migrating pytorch, we could get rid of this, right?

Copy link
Contributor Author

@MatteoRobbiati MatteoRobbiati Nov 18, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would keep it until Jax is ready, if we still plan to support Jax soon.

@MatteoRobbiati MatteoRobbiati merged commit 800e800 into main Nov 18, 2024
26 checks passed
@MatteoRobbiati MatteoRobbiati deleted the pytorch_migration branch November 18, 2024 08:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants