Folding Forum

The servers look happy. There's a vague note in the University of Virginia network status updates that engineers have received reports of connectivity problems. Sometimes we have dropouts if one of the upstream routers goes flaky. That said, we don't see anything of that nature right now. But what y...

The quick, approximate answer is likely PB but not EB. The intent is to retain analyzed data, but it is not always feasible to retain all "primary" data since the start of the project. We always try to retain as many data as we think feasible and that might be useful for other scientists i...

Project 8105 in this series is also being released to bigadv.

The server should be back up and running now.

We are taking server 128.143.199.96 down for a brief time this morning to allow for a software upgrade. Thanks for your patience!

We are releasing project 8104 to bigadv. Thanks for folding!

We are moving project 7520 to full FAH assignments. Please let us know of any problems. Thanks!

That (access forbidden) is the correct response for these servers. They are functioning normally and currently accepting work units. I would suggest checking your local networking.

We are pleased to announce the publication of some of our recent folding results. Per Larsson in my lab is the lead author on this publication, and it details how influenza proteins interact with membranes (and change shape i.e. refold in the membranes). We also look at how some important mutations ...

Kind of in between--the projects should look very much 8103, but there are some subtle (and scientifically important) differences. There may be some performance differences as well--we're just starting to benchmark. We're planning some additional project that will be a bit more different, but those ...

We're working on it (both availability of current project WU's on 128.143.231.201 and hopefully new projects coming online).
130.237.232.141 has reached end of support by the supercomputing center staff in Stockholm. Our collaborators have asked us to take it offline.

We tweaked a couple new settings, and the backlog appears to be clearing now. Thanks for bringing this to our attention.

I also found a configuration change that accompanied the upgrade (a new default was blocking job assigns). I think that should be fixed now.

We're looking at it. Unfortunately, Gromacs 4.6 sets CPU optimizations at compile time rather than run time (which is when Gromacs 4.5 and prior set optimizations). Therefore it presents a more complicated set of options for FAH. We definitely have plans to develop 4.6-based FAH cores, however.

Apologies--I noted the server incorrectly. The server is up and running now, although it was low on jobs at last check.