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.

Sign up for GitHub

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

Jump to bottom

Remove forced constraint to cuda 11.2 with Graphium 3.0 #512

Open
DomInvivo opened this issue May 1, 2024 · 1 comment · May be fixed by #519
Open

Remove forced constraint to cuda 11.2 with Graphium 3.0 #512

DomInvivo opened this issue May 1, 2024 · 1 comment · May be fixed by #519

Comments

@DomInvivo
Copy link
Collaborator 

          We should try to remove that after. I think it's because of `torchmetrics`

Originally posted by @DomInvivo in #510 (comment)
@DomInvivo DomInvivo changed the title Remove forced constraint to 11.2 with Graphium 2.0 Remove forced constraint to cuda 11.2 with Graphium 2.0 May 1, 2024
@DomInvivo DomInvivo changed the title Remove forced constraint to cuda 11.2 with Graphium 2.0 Remove forced constraint to cuda 11.2 with Graphium 3.0 Jul 9, 2024
@DomInvivo DomInvivo linked a pull request Jul 16, 2024 that will close this issue
Draft
28 tasks
@DomInvivo
Copy link
Collaborator Author

Cuda constrain is no longer there and was fixed by the torchmetrics branch with PR #511 . When #519 closes, this issue will close too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Graphium 3.0 datamol-io/graphium
1 participant
@DomInvivo