Core 22 version 0.0.14 issue

[aetch]

Please repackage this core. An announcement for it wouldn't hurt either.

It has a requirement for the VC++ 2015 Runtime (missing vcruntime140.dll), not everyone has it installed.
https://support.microsoft.com/en-us/top ... f26a218cc0

viewtopic.php?f=108&t=37348

[toTOW]

See my answer (and John's too) here : viewtopic.php?p=352578#p352578

[aetch]

I'll be straight, your "reply" here feels like a punch in the gut or a stab in the back.
I had already figured out the problem with the missing runtime and posted the solution earlier in the same thread you linked to.
This specific thread was simply to highlight it was an issue with the new core and not with any work unit being processed by that core.
I didn't mind helping John as that's the level it needs to be pushed to to get things fixed but you're taking credit for the work I had already done.
Not that it really matters to me because I already had the 2015-2019 Visual C++ runtime installed on my system.

Next time someone asks for help, I'll think twice about giving it.

[JohnChodera]

@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 with core22 0.0.14 with the friendly slack testers (let us know if you want an invite!) and then rolled out to full FAH rapidly because we needed the capabilities of this core for an urgent COVID Moonshot sprint. In retrospect, this was a mistake, for which I accept full responsibility: We should have done a day with BETA and ADVANCED first to make sure there were no hidden issues, which may have allowed us to catch this one early. We'll alter our SOP to make sure this happens next time.

For now, we've halted these projects on full FAH. Our core22 developer is somewhere inaccessible by the internet right now, but is back on Wednesday and will rebuild/repackage the core, bundling the VS DLLs this time.

Again, huge apologies here. We did end up getting a lot of useful data in the short time the sprint was running, which will definitely help us move forward.

And again, thanks from all of us.

~ John Chodera // MSKCC

[Neil-B]

Daft suggestion but if it would continue to help get results leaving this on beta flag might work? ... I would most beta team members would be able to sort out the dll issues and the lack of cuda on the rtx30*0 and depressed opencl ppds (still as good as the other ppds out there at the moment) should be acceptable until new core gets sorted ... not sure if the beta tester pool is big enough to make a difference but just a thought

[MrFrizzy]

Daft suggestion but if it would continue to help get results leaving this on beta flag might work? ... I would most beta team members would be able to sort out the dll issues and the lack of cuda on the rtx30*0 and depressed opencl ppds (still as good as the other ppds out there at the moment) should be acceptable until new core gets sorted ... not sure if the beta tester pool is big enough to make a difference but just a thought

I second this (I am also part of the beta group). No issues with p13456 on Windows 10 Pro Build 2004 and a GTX 1650.

[JohnChodera]

@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

[aetch]

@JohnChodera - No need to apologise.
Core 22 version 0.0.14 has given me zero issues
I've had 2 work units for project 13456, they've given me zero issues.
1). Project: 13456 (Run 7, Clone 41, Gen 0)
2). Project: 13456 (Run 295, Clone 18, Gen 0)

There's a beta team for testing, having a group of "friendly slack testers" kinda defeats the beta testers' role. I mean, isn't it the role of the beta tester to try and break whatever is thrown at them?
I would like to become a member of the beta team but it's not clear how to apply.

I'm not sure what help I would be as my system is pretty rock solid. Win 10 64-bit 20H2, NVidia drivers 471.11, just about every runtime under the sun installed from years of gaming.
Also, when I bring my linux system back on-line the RTX 2070 will very likely be transferred back to that system.

[toTOW]

To apply to the beta team, just read this thread and post a reply there : viewtopic.php?f=16&t=8

[JohnChodera]

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 Chodera // MSKCC

[JohnChodera]

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