And AGAIN they're only showing one trickle. :(
I've sent an email about it.

I have gotten used to that. In the case of these two, it does not matter much since I got the first and only trickle about half way through.

The ones that bothered me were the ones that got me one trickle after a day or so, and then ran a week or two with no more trickles and no more credits, and then terminated successfully.

Since I seem to get only a few work units a year these days, it does not matter all that much anymore. Maybe I will get some more by Easter.

---

We have about 7000 active Users running about 9000 active systems and there are about 103000 WU's out being worked now.

That works out to 11 WU's per active system.

I have a system that needs a WU but there are none available.

Under the heading of Orphaned WU's if the system has a WU that has not Trickled in 90 days and the WU is not one of the known groups with Trickle issues. Could these be aborted by the Project and reissued ?

Science is science it should be completed !!!


Thanks
Bill F

---

In October 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

Under the heading of Orphaned WU's if the system has a WU that has not Trickled in 90 days and the WU is not one of the known groups with Trickle issues. Could these be aborted by the Project and reissued ?

Perhaps a simpler system would be to just reduce the time limit on tasks? It may not release as many tasks as you think however. The figure is tasks/computer and I suspect the average number of CPUs/computer may be quite a lot higher than the three between my two boxes. With BOINC estimating even the quicker tasks as taking over ten days and some over 30 days on my boxes I am not getting any in the queue at the moment. (That is a problem with between WINE and BOINC that results in the GFLOPS value for my computers being greatly under reported.

Under the heading of Orphaned WU's if the system has a WU that has not Trickled in 90 days and the WU is not one of the known groups with Trickle issues. Could these be aborted by the Project and reissued ?

I would not mind, but it would not help me at all.

I got two work units 2018 October 15 that completed 2018 October 17.
The previous two work units I received were 2018 February 14 and completed 2018 Feb 29 and March 1.
I got two before that 2017 October 11 that completed 2017 October 25.

A big reason for my receiving the paucity of work units is that I run a Linux system with a 4-core processor. And no matter what fiddling with completion dates, it will not get me more work units. And the work units I do get send only one work unit near the beginning, and none after that -- none that are acknowledged anyway, and no credits ensue after that, even though they eventually complete correctly.

---

Perhaps a simpler system would be to just reduce the time limit on tasks?

Yes! The climate will have changed before some of them get back.

Well to restate my original thought about a WU with no Trickle in 90 Days (assuming that it is not one of the batches known to have trickle issues.

If a USER has so many WU's queued that he can't get it started in 90 days they have too many WU's and needs to release so others can do science.

OR

If the user has reloaded an OS and no longer has access to the "assigned" WU to work it... Then it is Orphaned and should be re-cycled

How hard would this be to implement ?

Bill F

---

In October 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

I'll ask. Might take a while.

"Project Aborts" aren't possible, but changes are going to be made. Which will take time, I guess.

These include deprecating the older, unused applications, (so those numbers will disappear from the total), and using "project kill" to remove the old, not needed, tasks from people's computers. This should also improve the appearance of the total number running.

Already used, is "no resends" when a batch is closed.

Back to the orginial reason for this thread. Does anyone know when there will be new work? I am starting to see empty cores on my machines.

---

Not me. But it might be next academic term (Quarter or Semester) before another deluge of batches is dropped into the queue -- as we experienced after Summer break. (That is conjecture, admittedly of limited value.)

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

I am starting to see empty cores on my machines.

Not me, because, even though I get very few work units (I run Linux), I run also Seti@home, Rosetta, and World Community grid.

My priorities are CPDN 44%, WCG 30%, Seti 13%, and Rosetta 13%.

Back when there were Linux work units, I usually kept three cores running CPDN 24/7 for weeks or months at a time. But in the last year or so, only four work units altogether.

---

Not me, because, even though I get very few work units (I run Linux), I run also Seti@home, Rosetta, and World Community grid.

My priorities are CPDN 44%, WCG 30%, Seti 13%, and Rosetta 13%.

Windows is the problem. What works the best for me is Rosetta, set to the 24-hour work units, since that best approximates the length of the CPDN work. Then, I set the Rosetta resource share to "0", so that it downloads work only when needed. I don't like to do that on other projects where the work units are short, since the PC must keep downloading new ones.

But I have long advocated reducing the timeouts also, to prevent hoarding the work and allowing it to reach the people who can turn it around more quickly. Isn't that what the project (any project) is for?

There are six new batches of SAM25 models, Batch #760-765, in a range of model durations - 60 month, 61 month, 72 month and 73 month (batch list).

Batch 760 which are 60 month runs and batch 761 which are 72 months. Long estimated times.

And they're sam25's.

That's climate research for you. :)

Joyful news! Nothing new in SAM25 land!

Had three contaminate my i7, one each from batches 763/4/5 (initial estimate in late 40s of days! [Haven't seen anything like that in a long time.]).

They died the premature death of their earlier peers: two in 3m 21s, one in 3m 20s.

{Edited for typo.)

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

They sure don't seem to like Windows.

I've started up my Linux/WINE machines again.
Might get some re-do's.

One out of two running: the failed one had already performed the two-minute self-destruct on two other machines before doing the same on mine.

Been running three 764 and 765 tasks for 21 hours now and doing fine. The computer is a virtual machine, XP 32-bit in VirtualBox on Ubuntu 16.04.
https://www.cpdn.org/cpdnboinc/show_host_detail.php?hostid=1469687

The estimated time is 5-6 months. Should I let them run or abort?

RUN!

The "early failings" are a problem with people's computers.
Once you're past that, it should be smooth sailing.

And running Linux with WINE also works.