Folding Forum

The Glycome is clearly important, but one can come up with drugs for cancer, Alzheimers', infectious disease, and many other areas w/o having to address it. So why get more complex than you have to in order to solve these key problems. I'm sure it's something that we'll get involved with sooner or l...

Thanks. I'll keep this in mind for future issues like this.

I just asked. "The bug ID is internal in our system."

Also, if people contact NVIDIA regarding this bug, that might get their attention.

We reported this to NVIDIA in March of 2014 BTW. We've pinged them again recently and "they're working on it".

It's already happening in our lab. We've written grants to help take it to FAH (it will take some serious engineering to do, hence requiring more funding to get it done).

Yes, unfortunately, the issue here is in the Maxwell driver, which we don't have control over. We did a workaround to make Core18 work at all on Maxwell, but it does come at a performance hit. We're reported this to NVIDIA to correct this in a future driver release.

We are continuing to look into core18 PPD issues. The push or Core18 comes in part due to some critical issues in Core17 science-wise that are addressed in core18. If anyone is curious, the discussion of this is completely public at the OpenMM git hub page.

The techniques we use in Folding@home are geared towards coming up with new lead compounds, such as our work in Alzheimer's Disease (http://pubs.acs.org/doi/abs/10.1021/jm201332p). Ebola has been an area of interest and I've been advising a company to use other computational techniques, leading to a...

yes, we are working on it and made some progress yesterday on ways to diagnose the situation. The container it's running in is running out of memory and we're looking into what's the best way to handle it. For now, if it does go down, it only misses a single stats update and cleans up on its own, wh...

Can you guys give links for the pages you're finding aren't working? Note the "fast team pages" are only updated for a certain number of teams.

UPDATE: We've put in some new code to help handle the stats being down in a more automated fashion. The upshot is that if the stats goes down during an update, it will take care of itself on the next update, so hopefully the longest you'll see the stats down is a single update.

We're going to continue manually running it when it goes down to better understand what the problem is. Given the pattern, it seems like a good bet that it will go down tomorrow -- I think I know what's going on and have a way to fix it, likely implementing that Sunday or Monday.

Thanks -- this is great to have.

We run the stats in a container of sorts and it's looking like the container isn't behaving well (the host server is doing great). We're looking to see what's the best solution here. It might be that we have to migrate from a container to a full server, although that's undesirable for several reason...