Whew...hm little bug i guess:
this is what i got :
Task FRA_t396_test_LARS_constraints_hom001_1_S_0001_0003056_0_pdb_IGNORE_THE_REST_1435_1520_0
is 364 y overdue oops. The thing is that my statistic now looks like a straight line with some local background (i subscribed like 2 month ago to rosetta) in it... :-(
Would someone maybe have a look at it?
thx
:-)

---

is the date right on your computer?

---

I guess that is the problem i had to reset my BIOS and missed to set date but it is already corrected by now..
Although rosetta server should know when it distributes work hm...
anyway thx very much for your fast reply :-)

---

Interesting. So could a user who finishes a WU late change the time on the box that produced it and turn it in as though it is on time?

I don't endorse that BTW, but I assume there is something (or someone) server side that would catch it?

The WU would likely already have been sent out to another box, so if the first person is able to turn in the late WU as though it is on time, then this could hurt the second person who turns in a valid result but is beaten to the punch by the first person.

Interesting. So could a user who finishes a WU late change the time on the box that produced it and turn it in as though it is on time?

I don't endorse that BTW, but I assume there is something (or someone) server side that would catch it?

The WU would likely already have been sent out to another box, so if the first person is able to turn in the late WU as though it is on time, then this could hurt the second person who turns in a valid result but is beaten to the punch by the first person.

The client just uses the time on you computer (and is a relative time to when it got the task.
The server uses it own time, not your clients.

---

Team mauisun.org

I'm not clear on what the implications are FC. Could you elaborate?

I'm not clear on what the implications are FC. Could you elaborate?

My understanding it the server tracks it's own time for a task/wu. It send it out to you a 12:00am it time and would like it back 7days after that on its time.

Your computer may think it got it at 11:00am (11hr later), your computer will think it needs to send it back by 11:00am 7days later.

They are independent, you can send it back at 2:00am 7days later* on your computer the server will not see this as 2:00am (i.e. overdue) but a few ours before its deadline.

That is why when the BIOS was reset, it messed up local time so when it did it's check it thinks it is ovedue due to the fact that where I * above it actually think in a unix style incremental timing something or other from some fixed point.
It just messes up the local scheduler, thinking it needs to do thoose task quicker than it needs (say a day out in the date/time) or it could cause it t be overdue (if you time was put in the future).

That is my understanding and is probably the gist of it (though if someone really know please chime in)

---

Team mauisun.org

Okay, thanks. That's what I was thinking.

So a WU could be turned in "overdue" before the deadline but it could not be turned in "on time" after the deadline...

...which means that Gil's WU should have been processed by the server normally (if he returned it before the server's deadline).

Just a little brain exercise.