I live in America so I use American time. But in my PC I use year-month-day so today is 2011.04.11

---

Personally I do yyyy-mm-dd for everything. Excellent for sorting, because you start with the slowest timescale. Windows and Linux like sorting things dated in that format, and then it's always chronological. I even use that format on official documents and forms that just have a blank for the date and don't force you to use a specific format.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

OK final one - Julian date for 11th April : 2455662.5

5771 Nisan 7

And to provide equal time (so to speak)...
1432 Jumada l-Ula 7

---

Monday, 2 Tammuz, 5771 - Another Independent date

---

or is it 1390 hamal 22

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

It's Tuesday.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

It's Tuesday.

Tomorrow and there'll be a 'Down Time', for maintenance and whatever is necessary ;^) , to keep everything going......boinc......... boinc.....boinc......|- \/

---

It's Tuesday.

Tomorrow and there'll be a 'Down Time', for maintenance and whatever is necessary ;^) , to keep everything going......boinc......... boinc.....boinc......|- \/

It's already Tuesday Down Unda, Fred.

(check Jason's flag...)

...April 11th 2011 1 second past midnight Stardate -311726.0

Why one second past midnight?

What about the time period from 00:00:00~00:00:01?

Good news - the 5AM AP is now running (but not as "High Priority") and should finish easily before 5AM (EDT).

Actually, both of the 4/11 APs finished in time. So (as usual) I was wrong. But I still think that BOINC overthinks things, and should just process FIFO, at least in cases like mine, where I process 24/7, so there is no uncertainty about processing-time-available-to-due-date/time.

---

Good news - the 5AM AP is now running (but not as "High Priority") and should finish easily before 5AM (EDT).

Actually, both of the 4/11 APs finished in time. So (as usual) I was wrong. But I still think that BOINC overthinks things, and should just process FIFO, at least in cases like mine, where I process 24/7, so there is no uncertainty about processing-time-available-to-due-date/time.

Exactly my point of view.

---

With each crime and every kindness we birth our future.

Good news - the 5AM AP is now running (but not as "High Priority") and should finish easily before 5AM (EDT).

Actually, both of the 4/11 APs finished in time. So (as usual) I was wrong. But I still think that BOINC overthinks things, and should just process FIFO, at least in cases like mine, where I process 24/7, so there is no uncertainty about processing-time-available-to-due-date/time.

Maybe the BOINC Manager should have three views, not just two.

Simple : Advanced : Obsessive

- the last one would disable all BOINC's decision-making functions, and ask you which task to run next every time it finished one.....

:-)

Good news - the 5AM AP is now running (but not as "High Priority") and should finish easily before 5AM (EDT).

Actually, both of the 4/11 APs finished in time. So (as usual) I was wrong. But I still think that BOINC overthinks things, and should just process FIFO, at least in cases like mine, where I process 24/7, so there is no uncertainty about processing-time-available-to-due-date/time.

Maybe the BOINC Manager should have three views, not just two.

Simple : Advanced : Obsessive

- the last one would disable all BOINC's decision-making functions, and ask you which task to run next every time it finished one.....

:-)

Or just run in FIFO or EDF mode would be nice.
Maybe one day the officals will realize some want it this way.
Until then i will just suspend the units i dont want to get touched.
Like i did the last 6 month.

---

With each crime and every kindness we birth our future.

Good news - the 5AM AP is now running (but not as "High Priority") and should finish easily before 5AM (EDT).

Actually, both of the 4/11 APs finished in time. So (as usual) I was wrong. But I still think that BOINC overthinks things, and should just process FIFO, at least in cases like mine, where I process 24/7, so there is no uncertainty about processing-time-available-to-due-date/time.

Maybe the BOINC Manager should have three views, not just two.

Simple : Advanced : Obsessive

- the last one would disable all BOINC's decision-making functions, and ask you which task to run next every time it finished one.....

:-)

Now who is being insulting?

Anyway, IMHO the death of any process is when it gets too complicated for its own good. FIFO is plenty good enough - I agree with Mike on this one.

---

Now who is being insulting?

Sorry, wasn't meaning it to be insulting, just a joke. Apologies if it came over the wrong way.

Good news - the 5AM AP is now running (but not as "High Priority") and should finish easily before 5AM (EDT).

Actually, both of the 4/11 APs finished in time. So (as usual) I was wrong. But I still think that BOINC overthinks things, and should just process FIFO, at least in cases like mine, where I process 24/7, so there is no uncertainty about processing-time-available-to-due-date/time.

Want to make BOINC finish and report days before the deadline? - "regroup" your cache!

For example 10 day cache can be done in many ways, e.g. 0+10, 2+8, 5+5, 7+3, 10+0 ...

0+10 BOINC may sometimes finish and report 0 days before the deadline

10+0 BOINC will try to finish and report 10 days before the deadline

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Want to make BOINC finish and report days before the deadline? - "regroup" your cache!

For example 10 day cache can be done in many ways, e.g. 0+10, 2+8, 5+5, 7+3, 10+0 ...

0+10 BOINC may sometimes finish and report 0 days before the deadline

10+0 BOINC will try to finish and report 10 days before the deadline

OK - how do I do that?

---

Want to make BOINC finish and report days before the deadline? - "regroup" your cache!

For example 10 day cache can be done in many ways, e.g. 0+10, 2+8, 5+5, 7+3, 10+0 ...

0+10 BOINC may sometimes finish and report 0 days before the deadline

10+0 BOINC will try to finish and report 10 days before the deadline

OK - how do I do that?

the 10+0 one?

website: account, computing preferences set connected to internet about every to 10 and maintain enough work for additional to 0.

local: boinc manager preferences, network usage tab, connect about every to 10 and additional work buffer to 0.

I would however suggest a smaller (e.g. max 5 day total) cache.
Large caches and shorter report deadlines (i.e. most non-seti) don't work too well together.

---

Carola
-------
I'm multilingual - I can misunderstand people in several languages!

I don't see what's wrong with just letting it run? I've yet to have anything turned in late shy of hardware failure or user error. So maybe I'm missing something here but what exactly does it matter? Although I agree it seems most reasonable for FIFO on my machine it may not make much sense on others under certain circumstances though.

---

Traveling through space at ~67,000mph!

OK final one - Julian date for 11th April : 2455662.5

Nitpicking: that’s the Julian Day (at 0h00 UT). A “Julian date” is the date according to the Julian calendar—which was 29 March on the day in question. The two systems have nothing to do with each other, despite their shared name (from two different namesakes).

---