PDA

View Full Version : Predictor is Running !



Nflight
02-22-2007, 05:56 PM
02/14/07

Some good news! In the last 24 hours the success rate for Linux has climbed to over %95. There are still some problems with validation we need to look at after we get the Mac version up to par.
It looks like version 0.13 is the magic version for Mac Powerpc. So far none of them have complained about missing libraries.
A new version of dTASSER for Macintosh PowerPC has been released. This is to correct a problem where the client states it is running version 0.10 but is actually running version 0.07. The new version is version 0.11.
NOTICE: The largest grouping of failed work units for the Macintosh platform are the missing libraries for versions of dTASSER less than 0.10. If you have a dTASSER version less than 0.10 on a Mac it won't work unless you have gfortran installed. To fix the problem you do not need to install gfortran. Please update the project or reset the project. When your client connects to the server it should download version 0.10.



02/16/07

We are still having problems producing a Mac PPC binary that will run on anything other than 10.4. We will continue to look into it.
There is a plan in place to reduce dTASSER's virtual memory requirement. We are working on implementing it.



02/21/07

NOTE: If your host runs Windows and you have not upgraded your client recently you may want to. The current client looks impressive.
One issue that has already come up with the Windows machines is that the work unit won't run unless you have 1.2GB of virtual memory. This is an issue which we are in the process of addressing.
New workunits have been created and all unsent work units have been canceled. The new work units are short and have a ~512MB memory requirement. This is mainly to test the Windows version of dTASSER. We are still working on making the Mac version available to Macs running MacOS X versions less than 10.4. We are aware of other issues such as the 'exited with zero status but no finished file' problem and will look into it as soon as we can.
dTASSER for Windows has been released. There may be a delay in downloading work units until some space is made in the shared memory so please don't be concerned if you see a message about work being committed to other platforms.
A Windows version of dTASSER may be available soon. We are also working on reducing the memory requirements.



***Please note we only have two members crunching, and have fallen into 21st place as of this writing! :sad5: :blob3: :blob3: :blob3:

Evil-Dragon
02-22-2007, 06:28 PM
I'd love to get some work for Windows but it keeps complaining that i don't have a 1GB of memory free, also it needs a 1.2GB page file.

They are fixing it i think?

gatekeeper53
02-22-2007, 07:08 PM
If this is what you call running:

2/22/2007 2:04:31 PM|Predictor @ Home|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
2/22/2007 2:04:31 PM|Predictor @ Home|Reason: Requested by user
2/22/2007 2:04:31 PM|Predictor @ Home|Requesting 43200 seconds of new work
2/22/2007 2:04:36 PM|Predictor @ Home|Scheduler request succeeded
2/22/2007 2:04:36 PM|Predictor @ Home|Message from server: No work sent
2/22/2007 2:04:36 PM|Predictor @ Home|Message from server: (there was work but it was committed to other platforms)
2/22/2007 2:04:46 PM|Predictor @ Home|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
2/22/2007 2:04:46 PM|Predictor @ Home|Reason: Requested by user
2/22/2007 2:04:46 PM|Predictor @ Home|Requesting 43200 seconds of new work
2/22/2007 2:04:52 PM|Predictor @ Home|Scheduler request succeeded
2/22/2007 2:04:52 PM|Predictor @ Home|Message from server: No work sent
2/22/2007 2:04:52 PM|Predictor @ Home|Message from server: (there was work but it was committed to other platforms)
2/22/2007 2:05:02 PM|Predictor @ Home|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
2/22/2007 2:05:02 PM|Predictor @ Home|Reason: To fetch work
2/22/2007 2:05:02 PM|Predictor @ Home|Requesting 43200 seconds of new work
2/22/2007 2:05:07 PM|Predictor @ Home|Scheduler request succeeded
2/22/2007 2:05:07 PM|Predictor @ Home|Message from server: No work sent
2/22/2007 2:05:07 PM|Predictor @ Home|Message from server: (there was work but it was committed to other platforms)
2/22/2007 2:05:07 PM|Predictor @ Home|No work from project
2/22/2007 2:05:07 PM|Predictor @ Home|Deferring scheduler requests for 1 minutes and 0 seconds
2/22/2007 2:06:07 PM|Predictor @ Home|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
2/22/2007 2:06:07 PM|Predictor @ Home|Reason: To fetch work
2/22/2007 2:06:07 PM|Predictor @ Home|Requesting 43200 seconds of new work
2/22/2007 2:06:12 PM|Predictor @ Home|Scheduler request succeeded
2/22/2007 2:06:12 PM|Predictor @ Home|Message from server: No work sent
2/22/2007 2:06:12 PM|Predictor @ Home|Message from server: (there was work but it was committed to other platforms)
2/22/2007 2:06:12 PM|Predictor @ Home|No work from project
2/22/2007 2:06:12 PM|Predictor @ Home|Deferring scheduler requests for 1 minutes and 0 seconds
2/22/2007 2:06:52 PM|Predictor @ Home|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
2/22/2007 2:06:52 PM|Predictor @ Home|Reason: Requested by user
2/22/2007 2:06:52 PM|Predictor @ Home|Requesting 43200 seconds of new work
2/22/2007 2:06:57 PM|Predictor @ Home|Scheduler request succeeded
2/22/2007 2:06:57 PM|Predictor @ Home|Message from server: No work sent
2/22/2007 2:06:57 PM|Predictor @ Home|Message from server: (there was work but it was committed to other platforms)
2/22/2007 2:07:07 PM|Predictor @ Home|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
2/22/2007 2:07:07 PM|Predictor @ Home|Reason: To fetch work
2/22/2007 2:07:07 PM|Predictor @ Home|Requesting 43200 seconds of new work
2/22/2007 2:07:13 PM|Predictor @ Home|Scheduler request succeeded
2/22/2007 2:07:13 PM|Predictor @ Home|Message from server: No work sent
2/22/2007 2:07:13 PM|Predictor @ Home|Message from server: (there was work but it was committed to other platforms)
2/22/2007 2:07:13 PM|Predictor @ Home|No work from project
2/22/2007 2:07:13 PM|Predictor @ Home|Deferring scheduler requests for 1 minutes and 0 seconds

Nflight
02-22-2007, 07:13 PM
Sorry I did not try to attach yet, kind of busy catching up being out of the office most of the week till today!

gatekeeper53
02-22-2007, 10:24 PM
No Problem. That was the 8th time I have tried to attach so it might be that they have very little work. The 2 people that we have on it have only gotten 25 wu's between them.

BobCat13
02-22-2007, 10:56 PM
gatekeeper53,

I have processed 11 wu's so far on my Athlon linux box. All copies of each wu have been sent to AMD processors running linux, so it appears they are using homogeneous redundancy.

The tasks in shared memory don't match your HR class, so just let the client keep contacting Predictor and you should eventually receive some work (if you have enough RAM) as the tasks in shared memory are allocated to others and replaced by new tasks.

gatekeeper53
02-23-2007, 02:49 AM
The ram's not a problem as this system has 4 gig. I just dislike letting my system spin in circles while a project gets it @@@@ together. I'll wait and come back when they are up and running. But thank you for letting me know what was going on.

AMDave
02-23-2007, 01:48 PM
Whaaaa?
I saw that memory message about 2 days ago but I wasn't paying attention so I never realised it was Predictor.
Don't that beat all!
It will be interesting to see if this turns into a resurrection or we have a "Zombie" running about the place. Hehe.
I hope it comes back and slots back into the CASP challenge.
That would be cool.

AMDave
02-26-2007, 06:53 AM
Excellent Sig BobCat13
saw you dropped out of uptime.
Does that mean I can reboot boxen#5, at long last? LOL

BobCat13
02-27-2007, 02:11 AM
Shortly after receiving the email from the uptime project, we had an extended power outage. When power was restored I decided to remove the client from both boxes.

I was trying to catch you, but my battery backup doesn't last 4 hours. :(

sentient_life
03-31-2008, 05:05 PM
Predictor has returned yet again! You need to detach and reattach, because their URL has changed after the move to Michigan:

http://predictor.chem.lsa.umich.edu

vaughan
04-04-2008, 10:25 AM
Predictor has returned yet again!
With tasks that take 40+ hours to run. :icon_neutral:

PoorBoy
04-04-2008, 11:24 AM
With tasks that take 40+ hours to run. :icon_neutral:

:icon_rolleyes: ... With those Wu Lengths I hope none of my Quads get Accidentally Attached to this project ... :icon_lol:

sentient_life
04-04-2008, 04:11 PM
As far as I can remember, Predictor has always had long running workunits. They are roughly the same length (12.5-17 hrs. on my quad) as Einstein@Home and give pretty good credit once validated (no pesky wingman needed). My laptop is going to take about 31 hrs. if the estimate of remaining time is accurate, but I don't think your "mildly" overclocked quads would be anywhere close to that!:icon_lol: