The client itself minizes the energy. In the stats is shown the energy, because it tells us the real worth of the structure ....
I thought we would be trying to minimize crease energy. But looking at the charts for the top ten results it is clear that the client is making no effort at all to minimize crease energy. None of the other charts look like there's any attempt to optimize them, either. So what is the client trying to minimize?
The client itself minizes the energy. In the stats is shown the energy, because it tells us the real worth of the structure ....
The German DC Community : Team Rechenkraft.net - Join now ! Rechenkraft.net
dfGUI always reported that the RMS trended DOWN initially at least for the previous three proteins, BUT this is not the case with this client. It is reporting the "Energy" value, and in the three cases I've looked at so far, the trend is moving UP!!!
I'm not sure if the RMS value that isn't shown until it gets to the server is trending down or not...
Seems like the wrong direction though...
My two cents worth...
Ned
That's one of the things (energy going up - and down) I mentioned in http://www.free-dc.org/forum/showthr...&threadid=4567 - Howard replied saying that
Does seem a bit odd when compared to the good ol' RMS going down that we are used toIt may do great, it may not, but the important difference now is we are not using ANY information about the true structure now, it is true 'ab initio' prediction. We are treading on unexplored territory now. Thus even if the energy goes down, the RMSD may not, and vice-versa. We will watch how this run goes carefully, and 'tweak' parameters as we feel necessary for the next protein to try to improve things even more.
More precisely, if you are looking at the graphs, the client is minimizing the 'fitness score'. This is a combination of crease energy, Secondary structure content compared to predicted, and Rgyr.
Howard Feldman
Ok, more calculations than previous client to do the comparisons... Hence, warmer CPU's.The client is minimizing the 'fitness score'. This is a combination of crease energy, Secondary structure content compared to predicted, and Rgyr.
I can see that you expected the crease energy to be minimized with the fitness score and that's why you had the progress.txt report "energy"... However, if this is your new criteria, please use the "fitness score" in progress.txt so that we can easily see the success of the algorithm...
My two cents worth...
Ned
progress.txt is NOT for human eyes...
Howard Feldman
so why does the readme1st.txt file sayOriginally posted by Brian the Fist
progress.txt is NOT for human eyes...
To check progress while in quiet mode/running as a service, a file called
"progress.txt" will be written to the directory where the program is installed
so you can monitor its progress still
.. those of us running DF as a service aren't considered human? That really explains a lot. *snicker*
www.thegenomecollective.com
Borging.. it's not just an addiction. It's...
I think what he meant was the last line in progress.txt isn't really intended for human eyes. The other information is quite readable by humans.
Probably as good a reason as any why there are now only 1,505 active "participants" out of 26,458 registered...Originally posted by tpdooley
.. those of us running DF as a service aren't considered human? That really explains a lot. *snicker*
If that's the case then why is it there? What else is using (DF-wise, not 3rd party-wise) progress.txt for that info (iirc, the energy is also in filelist.txt)?Originally posted by Digital Parasite
I think what he meant was the last line in progress.txt isn't really intended for human eyes. The other information is quite readable by humans.
It is there essentially for dfGUI. If you want to look at it, go ahead but don't interpret the contents too literally
Howard Feldman
I won't - as long as you don't mind me using the value in my monitoring appOriginally posted by Brian the Fist
It is there essentially for dfGUI. If you want to look at it, go ahead but don't interpret the contents too literally