Folding Forum

We built core22 0.0.14 with CUDA 10.2, with the goal of having a wide range of supported cards. This may unfortunately no longer support Kepler GPUs. We're working on a way to support multiple CUDA versions to expand support to more generations of GPUs. Hopefully, we can restore this soon! ~ John Ch...

@Tashgan @Neil-B: Thanks for the heads up!
Thankfully, it looks like it falls back to OpenCL smoothly.

Any chance either of you have the CUDA Toolkit installed? If so, which version(s)?

~ John Chodera // MSKCC

@psaam001: We're still working on the linux build for core22 0.0.14! There's a dependency we're working to eliminate there before we can release it.

Best

~ John Chodera // MSKCC

Thanks, toTOW! It looks like we overlooked the need to include the Visual Studio DLLs.

We're working on this now.

~ John Chodera // MSKCC

Thanks, @Gary480six and @erich56!

Did anyone have to install a DLL *besides* one these two? Did anyone require just one?

Also, it would help us if anyone who ran into this problem let us know which version of Win you're using.

~ John Chodera // MSKCC

@Gary480six: Can you let us know which exact DLLs you needed to install? Besides `VCRUNTIME140.dll`, what was the other DLL?

~ John Chodera // MSKCC

Hi folks! So sorry about this. Our initial testing with volunteers didn't reveal this issue, so we're surprised by this---we intend to distribute all DLLs you need for core22 0.0.14. We've disabled these 0.0.14 projects for full FAH right now until we can address this issue. All other projects shoul...

Thanks, @aetch! We _should_ be distributing any runtime packages that are necessary for 0.0.14---if not, that's a bug, and on us to fix!

Thanks for the pointer!

~ John Chodera // MSKCC

Oh no!

Can you give s any more information about which DLLs it thinks are missing? And perhaps a log showing which version of the core is being downloaded or used (should be 0.0.14)?

Thanks so much for helping us track this down.

~ John Chodera // MSKCC

@JimF: I have to apologize for what the lack of updates from our end. We've been so incredibly busy with the sprint to nominate a clinical candidate that we haven't had a chance to provide detailed updates as frequently as we'd like. We hope to have some significant good news to announce very soon, ...

It looks like there was an issue where the max assign rate exceeded the rate that these servers could keep up with (due to either networking or storage bandwidth---we're still working to diagnose). This has been corrected by folks in the lab.

Thanks!

~ John Chodera // MSKCC

We're not quite sure what's responsible, but we've restarted the server and are just waiting for it to come back online.

On it---thanks!

~ John Chodera

Thanks for bringing this to my attention, @bruce. I've just put in an inquiry with Networking. Will update you when I have more information.

Apologies for the technical issues here. This certainly isn't intended behavior!

~ John Chodera // MSKCC