Deadline passed?

[Hookj5]

The WU I had running in VMware SMP said " Unit's deadline (Feb 6 06:29) has passed". I got this unit Feb 4, Sun. Is the deadline so short? How do I tell what the deadline is? I am kinda bent about this bcuz that WU was at 89%. Anything I can do to save all that work?

[leelegend]

nope....the SMP deadlines are harsh, if you are not leaving the rig on 24hours, i dont think you will make it.

check the stanford site for the deadlines on the project summery page, but they are all between 1.5 to 3 days (max)

lee

[Macaholic]

First figure out which unit your SMP client is working on by checking the logfile or the terminal window. Then check out the work unit summary page (http://fah-web.stanford.edu/psummary.html). You will notice the the GRO-SMP units usually have a final deadline of 2.0 days (p3020, p3023, p3025, and p3027). The units for p3024 are 1.5 days. Finally p3036 and p3037 are 3.0 days. Yes, the deadlines are EXTREMELY tight for SMP units and that is unlikely to ever change. If you can't make those deadlines it would be best to switch to the GPU client or regular CPU client. There is really nothing you can do at this point. It has already been reassigned to another donor since you missed the final deadline. Sorry. Fold on.

[Hookj5]

Thanks guys.

[dfonda]

It makes it hard to work on a good OC worrying about the deadlines. Its a perfect envirement for an Overclock too. My basement is like 10 F right now. Wicked cold for PA.

[Hack30]

Just check the "unitinfo" file it will tell u the deadline.:)

[Hookj5]

Thanks guys. I have another question, when I run F@H in Ubuntu, it thinks it's 15:25 when its 9:31 . How do I fix this? While i'm on the subject, the time for this post says 3:31 pm when here in Texas its 9:31 am. Whats up with that?

[WarriorII]

I think you need to sync your system clock.

There's a setting for it under Admin I think.

[Rav]

You could use the 'Ignore deadlines' option in the config if your VM is getting too far off and you are sure they are actually on time.

[Macaholic]

Thanks guys. I have another question, when I run F@H in Ubuntu, it thinks it's 15:25 when its 9:31 . How do I fix this? While i'm on the subject, the time for this post says 3:31 pm when here in Texas its 9:31 am. Whats up with that?

What machine specs are we talking about here? If you are running an A64 X2 or Dual-Core Opteron you should consider installing AMD Dual-Core Optimizer (http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_13118,00.html) to fix the clock sync problem.

AMD Dual-Core Optimizer - The AMD Dual-Core Optimizer can help improve some PC gaming video performance by compensating for those applications that bypass the Windows API for timing by directly using the RDTSC (Read Time Stamp Counter) instruction. Applications that rely on RDTSC do not benefit from the logic in the operating system to properly account for the affect of power management mechanisms on the rate at which a processor core's Time Stamp Counter (TSC) is incremented. The AMD Dual-Core Optimizer helps to correct the resulting video performance effects or other incorrect timing effects that these applications may experience on dual-core processor systems, by periodically adjusting the core time-stamp-counters, so that they are synchronized.

[Hookj5]

Sorry I haven't updated my sig. I am running a C2D E6600 with 1 F@H in windows and 1 F@H SMP in Ubuantu in a VMware window. My clock in the windows toolbar and the clock in the upper right corner of Ubuantu are 1 min. different. The terminal where F@H SMP is running shows a time 6 hours faster than the actual time. Right now it shows [17:53:44] when the clock shows 11:54 am. Is this a problem? Is there a fix?

[Macaholic]

The terminal where F@H SMP is running shows a time 6 hours faster than the actual time. Right now it shows [17:53:44] when the clock shows 11:54 am. Is this a problem? Is there a fix?

That is normal. The logfile/terminal timestamps are set to sync, IIRC, with GMT. For example my terminal window shows right now;

[17:43:16] Completed 4850000 out of 5000000 steps (97)
[17:58:17] Timered checkpoint triggered.
[18:06:06] Writing local files
[18:06:07] Completed 4900000 out of 5000000 steps (98)
[18:21:06] Timered checkpoint triggered.

And the current time is 12:24 PM. No problems. Fold on. :thup:

[Hookj5]

Thanks Mac and all who posted to help a total n00b.

[dfonda]

Yeah thanks here too. I was hoping it was a time zone thing. But thought the difference in time between east coast and west coast(Stanford) didn't jive.