native.val should be 33202 bytes
Both update packages have the new native.val in them as far as I can tell.
One of my PCs has just done gen 0 of the new protein and then stopped with :
Upon checking native.val it is still saying that the protein is 96 and not 56...I can't download a fresh install as the server times out...anyone experiencing this?Code:ERROR: [001.009] {foldtrajlite2.c, line 5597} Error occured while aligning structures ERROR: [001.023] {rotate.c, line 677} iResCounts do not match 96 56 ERROR: [001.010] {foldtrajlite2.c, line 5601} Abnormally small RMSD: 0.000000 (96 1 1) FATAL ERROR: [096.056] {foldtrajlite2.c, line 5608} Invalid/corrupt native structure, please download a fresh copy of the software
/edit: both the Linux and Windows updates have native.val as 96...
Last edited by pfb; 08-13-2003 at 05:49 PM.
native.val should be 33202 bytes
Both update packages have the new native.val in them as far as I can tell.
Howard Feldman
looks like you have a corrupted update, probably just need to blow it up and start fresh
good luck!
Use the right tool for the right job!
The native.val I have after the update is 58,181 bytes and a modified time/date of 13 August 2003, 2:12:06 PM - so I guess it's not right...
Time to kick back and try and get a fresh Windows and Linux download from the server - not looking to good at the moment though as it keeps timing out
========================[ Aug 13, 2003 3:26 PM ]========================
ERROR: [001.001] {trajtools.c, line 3512} Unable to open trajectory distribution file handle_protein_1.trj
FATAL ERROR: [002.003] {foldtrajlite2.c, line 5307} Unable to read trajectory distribution handle_protein_1, please create a new one
This was a fresh manual download.
I deleted filelist.txt, progress.txt and any work it had done, not much yet.
Edit found 4 zombie foldtrajlite.ex running in task manager under XP - not sure how that happened, starting fresh again.
I got that after the iResCounts error
Still trying to get a fresh install down...
So WTF is the deal this time? My whole team is hosed again. Not one person has uploaded since the update? Was it another botched auto update or what? I only see like two people putting up any numbers for the entire project!
Not looking forward to coming home and finding 4 computers burning energy for nothing.....again....
us users--> <-- D.F. staff
To many smilies to work with.
Crunchin D.F. for www.procooling.com
This means they got it right the second time around, cause the first zip file had a native.val file size of 58,181 bytes.Originally posted by Brian the Fist
native.val should be 33202 bytes
Both update packages have the new native.val in them as far as I can tell.
So here we are, tryin to download again!
Ok, so in idiot terms this means the "auto" update was a failure for all and we have to download the "fixed" client?Originally posted by Paratima
This means they got it right the second time around, cause the first zip file had a native.val file size of 58,181 bytes.
So here we are, tryin to download again!
Be another 2 hours before I get home to the crunchers....
Crunchin D.F. for www.procooling.com
Yup! AND ya can't get in now fer nuttin'.
Well, hey, did you REALLY have anything better to do tonight?
Argh!
Just manged to get the full Linux package down (after an hour) and...
and the just got the Windows full package:
Ummmmm...errrrr....well....no.Originally posted by Paratima
Yup! AND ya can't get in now fer nuttin'.
Well, hey, did you REALLY have anything better to do tonight?
Crunchin D.F. for www.procooling.com
AAAAARRRRRRGGGGGHHHHHH!
I FINALLY got thru, downloaded the zip file & guess what?
native.val = 58,181 bytes!!
I going home. Start folding tomorrow. Plenty of time later. Nighty.
The Windows screen-saver has the right native.val in it...
/me goes off to test....
Last edited by pfb; 08-13-2003 at 08:02 PM.
well, using the native.val from the Windows screensaver seems to work...not sure Howard would be happy with that but I'll go with it until the main packages are updated...
The Linux updates I got(Not the full tar.gz) seem to be the correct size 33k, still waiting to get through gen 0 to be sure all is working.
The Windows client crashed on all my Windows systems though, they have the 58k file.
I just got this exact same error on one of my systems. It had the auto update not manual. Trying again!Originally posted by pfb
One of my PCs has just done gen 0 of the new protein and then stopped with :
Upon checking native.val it is still saying that the protein is 96 and not 56...I can't download a fresh install as the server times out...anyone experiencing this?Code:ERROR: [001.009] {foldtrajlite2.c, line 5597} Error occured while aligning structures ERROR: [001.023] {rotate.c, line 677} iResCounts do not match 96 56 ERROR: [001.010] {foldtrajlite2.c, line 5601} Abnormally small RMSD: 0.000000 (96 1 1) FATAL ERROR: [096.056] {foldtrajlite2.c, line 5608} Invalid/corrupt native structure, please download a fresh copy of the software
/edit: both the Linux and Windows updates have native.val as 96...
Edit: Make that 2 system's 1 manual update and 1 auto!
Last edited by Rbreb13; 08-13-2003 at 11:09 PM.
www.hardcoreware.net
I auto-updated about 1 1/2 hours ago (it's 7:36 pm Mountain Standard Time right now). And my native.val file is 33K.
I must be the lucky one...
i also grabbed a 33k native.val from the SS, thanks to pfb's post, thank you!Originally posted by Paratima
Thank you, pfb !
i had just started installing to a new 23 PC/26 Ghz crack rack, only had done 3 installs when i read through this
Use the right tool for the right job!
I just downloaded the linux client and the native.val is too big 58k ?
ftp'd it from mine using binary mode.Originally posted by PCZ
I just downloaded the linux client and the native.val is too big 58k ?
It working fine and the correct size to www.dbestern.com/native.val
This runs fine under Mandrake 9.1+
I would think native.val is the same across all platforms /me shrugs
Thanks IB that done the trick
Looks like I got all my crunchers back up and my team is slowly following suit. Other than Gen 0 everything is twice as fast on my comps. My output is so far double. I also noticed rediculously low RMS already. Low 3's on the stats page.
Crunchin D.F. for www.procooling.com
Howard says: Get a fresh download and start clean
Code:08/13/2003 - Our new protein is underway, we are now studying the folding of Protein G, soon to be followed by Protein L. These are small, well-characterized proteins that have been studied by other methods, and this will allow us to compare our 'folding movies' to other, more tried and tested studies of protein folding. - Please note if you manually downloaded (not autoupdate) the new client (NOT screensaver) before 11PM EST today, it seems that the package still had the old native.val in it from the last protein. Strangely its date stamp is current though so that's how we managed to miss it. Not sure what happened but the packages linked from the download page should have the correct file now. If in doubt, or if you receive an error message about being unable to compute RMSD, check - your native.val should now be 33202 bytes if you have the latest client. Sorry for any inconvenience.
So what happened to that "very thorough testing"?!
You can't have tested it much when you didn't catch that error (the wrong native.val file)
I'll not be surprised if we/you will loose *a lot* of participants because of this
I have a client that had been offline since the start of this month. I started it yesterday a few times to see if it would update properly, but the ftp was overloaded. I then tried it again this morning and it downloaded the update (with the correct native.val), but it'll not run any longer
Howard You got mail
I have some offlines boxes yet to update. Should I try the autoupdate or just delete everything a start anew?
Proud member of the Dutch Power Cows
Personally, I would see if the autoupdate works first.
We tested the auto-update and it worked fine for us. Anyone who did the auto-update should have received the correct native.val. If you did the auto-update and did not receive the correct native.val I cannot understand how at the moment.
And yes, the 'fresh' packages had the incorrect file in them for a few hours, but we fixed it as soon as we learned of it. We do not explicitly try downloading the posted packages and running them prior to release (but rather just test our own local copies) which is how this packaging error was missed.
Howard Feldman
/me gets another idea
Betatesting has been discussed before and this is yet another suggestion
Since it is not really possible to setup a test server so we could test new releases before they were released, I'm thinking of doing it differently. When we change to a new protein, it's possible to upload "old" data for the next 48 hours. Why not use part of that time to beta test?
Besically, it should be possible to set a "beta switch" in the client. If true, the client will load the update right away, if false, the client will continue crunching on the old protein for a little longer - how long I don't know, maybe 12 hours or something?
That would make it possible to report bugs and get them fixed before the majority of the clients is starting to update.
It would also distribute the load on the server, at least a little bit
Stupid idea or?
All machines at my place were set to auto update from the Daemon I have up and running. They all puked for some reason. Either the wrong native file or for some reason it was unzipping and gave off an error and hung there (Windows machines only). All were coming from the same place. Looked in error logs and it said something about wrong size or something. Haven't bothered to open the 15MB error.log file from the update Daemon yet .... (I hope you fix that soon please! )Originally posted by Brian the Fist
We tested the auto-update and it worked fine for us. Anyone who did the auto-update should have received the correct native.val. If you did the auto-update and did not receive the correct native.val I cannot understand how at the moment.
And yes, the 'fresh' packages had the incorrect file in them for a few hours, but we fixed it as soon as we learned of it. We do not explicitly try downloading the posted packages and running them prior to release (but rather just test our own local copies) which is how this packaging error was missed.
Linux Machines went through ok.
For the Windows machines I stopped each process and manually updated the neccesary files from the .zip I downloaded from the site. After that everything was on it's way.
So far running this Daemon hasn't done me any good. Hopefully it will next time though
(I'm not ranting or anything just in case someone gets the wrong idea about my post, hence the smilies in it)
OK, what size is the Protein supposed to be ...56, 33 or 3.14
I am not a Stats Ho, it is just more satisfying to see that my numbers are better than yours.
Proteine size is 56.
Proud member of the Dutch Power Cows
56 ehh, but I take it there is a good 56 and a bad 56
I am not a Stats Ho, it is just more satisfying to see that my numbers are better than yours.
Protein size = 56, Native.val size = 33Kb
I have a new version which you might want to try (not posted yet) that should remove the excessive logging I think. Let me know if you want me to send it to you.Originally posted by ^7_of_9
Haven't bothered to open the 15MB error.log file from the update Daemon yet .... (I hope you fix that soon please! )
Howard Feldman