Folding Forum

We have a fix for this in core22 0.0.15 that we're testing internally right now and hope to roll out in the next couple of days. Thanks so much for your patience, everyone!

~ John Chodera // MSKCC

We have a fix for this in core22 0.0.15 that we're testing internally right now and hope to roll out in the next couple of days. Thanks so much for your patience, everyone!

~ John Chodera // MSKCC

If anyone who experienced the "missing DLL" issue with core22 0.0.14 has not installed the Visual Studio libraries manually to work around the issue, we could use your help testing a new core22 release! Please private message me an email address where we can reach you for details. ~ John C...

If anyone who experienced the "missing DLL" issue with core22 0.0.14 has not installed the Visual Studio libraries manually to work around the issue, we could use your help testing a new core22 release! Please private message me an email address where we can reach you for details. ~ John C...

If anyone who had the "missing DLL" issue with core22 0.0.14 has not installed the Visual Studio libraries manually to work around this, we could use your help testing a new core22 release! Please private message me an email address where we can reach you for details. Thanks! ~ John Choder...

@JimF: That's super weird. If this happens again, the best way to debug is to try to capture one of the core output logs, though that's hard to do because it exits so quickly. We can look up whatever gets returned to the server on our side, but you'd have to find the project manager corresponding to...

Oh no, this is one of our servers. I've flagged this for the folks in the lab to investigate. Apologies for the trouble here.

~ John Chodera // MSKCC

@WhitehawkEQ: The missing DLL error occurs on 0.0.13? Which DLLs does it complain are missing?

~ John Chodera // MSKCC

@Neil-B and @MrFrizzy: Great suggestions. I've enabled 13456-7 for BETA and will post in the beta forums instructions on what needs to be done if the DLL issue shows up.

~ John Chodera // MSKCC

@Neil-B: Now, that's odd. core22 0.0.13 was built with CUDA 9.2 and OpenMM 7.4.2. core22 0.0.14 was built with CUDA 10.1 and OpenMM 7.5.1. I definitely don't understand why CUDA 9.2 would work but 10.1 wouldn't. If you have the time, perhaps we could invite you to the testing slack so we could run t...

@erich56: After checking with the lead dev, the WU should not get stuck *permanently*, but it may time out for a while. Eventually, it will be dumped automatically, and pick up WUs that use 0.0.13. You can dump the WU manually by stopping your client, purging the work directory, and restarting, but ...

Thanks to everybody who chimed in to help here! OpenCL.DLL should be distributed with your display drivers, and isn't something we can distribute with the core because it's hardware-specific. This thread on the NVIDIA support forums is a similar issue, and has good info on which display driver versi...

@aetch: Huge apologies for the issues 0.0.14 has been causing, and enormous thanks for being quick to post here about the issue and solutions. It certainly has helped others work around the problem and has helped us address the problem, for which we're enormously grateful. We did extensive testing w...

@erich56: So sorry about this. We had temporarily disabled the 0.0.14 projects, but re-enabled them to collect more data on the issues. I hadn't realized it was causing WUs to get _stuck_ however. Can you dump the project (or just delete the WU from it's directory)? If it's truly causing the client ...

Thanks for the feedback! We built core22 0.0.14 against CUDA 10.2, and I realize that support for RTX 30x0s was only added in CUDA 11.1: https://developer.nvidia.com/blog/cuda-11-1-introduces-support-rtx-30-series/ We likely need to build 0.0.15 against the latest CUDA 11 to ensure CUDA will work wi...