-
Notifications
You must be signed in to change notification settings - Fork 683
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
{bio,vis}[foss/2022a] n2v v0.3.2, CSBDeep v0.7.4 w/ CUDA 11.7.0 #19030
base: develop
Are you sure you want to change the base?
Conversation
…4-foss-2022a-CUDA-11.7.0.eb
Test report by @boegel |
@boegelbot please test @ jsc-zen2 |
@boegel: Request for testing this PR well received on jsczen2l1.int.jsc-zen2.easybuild-test.cluster PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1766800165 processed Message to humans: this is just bookkeeping information for me, |
@boegelbot please test @ generoso |
Test report by @boegelbot |
Test report by @boegel |
|
||
name = 'n2v' | ||
version = '0.3.2' | ||
versionsuffix = '-CUDA-11.7.0' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm curious, why did you remove CUDA
as a direct dependency (which then prevented you from using the %(cudaver)s
template here), is it the case that n2v
itself doesn't use CUDA
, only via CSBDeep
, and you wanted to make that clear?
If that's the case, is this a distinction we should be looking out for in PRs?
(created using
eb --new-pr
)