There are some informations abput the new Protein:
http://www.rcsb.org/pdb/cgi/explore.cgi?job=summary&pdbId=1YCC&page=0&pid=257001067368462
Type: Posts; User: Keller
There are some informations abput the new Protein:
http://www.rcsb.org/pdb/cgi/explore.cgi?job=summary&pdbId=1YCC&page=0&pid=257001067368462
The client itself minizes the energy. In the stats is shown the energy, because it tells us the real worth of the structure ....
Ōne simple question:
Is it faster to determine the RMSD or the energy or is it the same ?
I had some buffered generations from the previous Client/Protein .
Then I started the client and the autoupdate proceeded successfully. I restartet the client and the client crashed (it said caugh...
Thanks ... I noticed the same problem and thought my work was lost.
You dont have to reset i think ... the download is cancelled and the download will restart if you start the client again ... (you dont have to clear the buffer or something like that)
While you were downloadng the server crashed. therefore the download has been canceled what causes the file size error, because the client didn´t got the whole file download
Of course Team rechenkraft.net has teams on other projects, too :D
A similar one to our current, "small and well characterized" (reading the news would answer some questions :) )
Well, i think this is the kind of a prev gen missing error, that is caused by a server slowdown ...
try to start the client with the argument -purgeuploadlist 1 (make a backup before) and start it...
I dont have control about all my boxes ... some are a few miles away ...
I hope it wont be so long until the servers are back up, because some of my clients try to contact the server for some minutes after each generation ... a lot of time that is lost !!!
The problem is, we cant go faster through it ... a completely random computation is the fastest way to generate those structures we need to go through the other 250 generations.
Atm, our project...
many programs create temporary files ...
Generally, DF clears his temporary files. Therfore I think these temporary files are from other applications and have nothing to do with df.
Look at the "Users movement page" and you will understand how this could happen
Well, there really is nothing then a bit ( more :) ) good german beer
:cheers: :cheers: :cheers:
The thread is here
You dont lose your work ...
BUT: if the last generation on your box is uploaded to the server and you try to upload it agian you receive this message(can be caused by an server overload or an abrupt...
Did you try the -purgeuploadlist switch as described in other threads or the readme file ?
I think an overloaded Server could cause this error ...
At a protein changeover or a client update the server goes offline and if you start the client you need to press the "Enter" button. After the...
Well, this error message simply means that the client wasnīt abl to read/write data of/to the RAM. This can be caused by temperature problems, overclocked RAM chips or to less RAM. Are you having...
Now the CLient says "MAIN SERVER IS DOWN FOR PROTEIN CHANGEOVER" .
The servers seem to be back on soon ... I hope :D
I dont think so because there is nothing more to put in the memory ...
Alls files that need to be cached are at most 80 mb.
When will we change to the next Protein ? I think he 10,000,000 structures goal is a non-sense because the new client needs less time to calculate better results.
On my P3 667 (256 mb ram) i needed 24 hours to complete only 6 gens (92-98)!!! (the average time per gen is 4h ... ) i think this is really to much.
I canīt believe this isnīt a bug, because in this...