I just noticed a new Feature on my Account Page, it's called Pending (Hours), neat feature IMO ... :)
____________
https://signature.statseb.fr/sig-1323.png

Interesting! I wonder how that is calculated.
____________
Reno, NV
Team: SETI.USA

IMO "pending" here is sum of runtime of started but not finished wu's on your computers at the moment the last wuprop wu was finished at this computer

IMO "pending" here is sum of runtime of started but not finished wu's on your computers at the moment the last wuprop wu was finished at this computer

Yes, it's the amount of time that an app has already run for, where it has not yet been reported. This is calculated by tallying totals from previously returned WUProp apps, and doesn't include what is presently being run AFAICT.

I've just checked this against some climate models I'm running:
climateprediction.net UK Met Office Coupled Model Full Resolution Ocean 27.32 629.98
My total run time is presently around 635, so that adds up to the last WUProp WU I returned from that system. The 27.32h was from a previous run on a different system, which failed after 27.32h.

A good addition. It might allow you to see new apps that you are crunching for even before you report any WU's.
It's definitely useful for projects that you contribute heavily towards and long projects with WU's.

Interesting to say the least.

I noticed that my Physicsathome app "Rendering nano xx" dropped in time from 11.78 hours to 8.83 hours (I have had trouble getting enough work units so have not had a lot of work).

Other than that one it even shows a SLinCA work unit type I have yet to report (a Z34 which I haven't started as yet).

Like STEVE I have RNA World pending showing, mine is 524 hours which is how much I probably have done so far as I still have an estimated 3,100 hours to go on a couple of very long ones (that should get me to Emerald).

Conan
____________

Pending (hours) isn't adding up!

Earlier today:
Total credit 382,632
FreeHAL@home FreeHAL 2012 app 3,810.38 219.23

Slightly Later today:
Total credit 382,702
FreeHAL@home FreeHAL 2012 app 3,816.72 140.63 (Lost at least 73h)

Later again:
Total credit 382,800
FreeHAL@home FreeHAL 2012 app 3,827.23 170.43

A few minutes ago:
Total credit 382,842
FreeHAL@home FreeHAL 2012 app 3,852.33 157.03 (3827+170>3852)
____________
=sticky tape=

Pending (hours) isn't adding up!

Earlier today:
Total credit 382,632
FreeHAL@home FreeHAL 2012 app 3,810.38 219.23

Slightly Later today:
Total credit 382,702
FreeHAL@home FreeHAL 2012 app 3,816.72 140.63 (Lost at least 73h)

Later again:
Total credit 382,800
FreeHAL@home FreeHAL 2012 app 3,827.23 170.43

A few minutes ago:
Total credit 382,842
FreeHAL@home FreeHAL 2012 app 3,852.33 157.03 (3827+170>3852)

Hi Conan, I'm not far off 5K, which is the highest app milestone here, so that's not a concern; I'll get there soon enough. While we might want to switch other apps Hal is NCI, so that's not an issue either. My point isn't necessarily about HAL; it's the concept - you would think that the Run Time Total + Pending Total could only increase. Instead, I've seen a fairly substantial decrease of 73h between two checks only hours apart. While the Run Time Total didn't fall the combined Run Time Total + Pending Total did fall, and hasn't recovered; RTT+P is now < RTT+P earlier. So, what's the point in having Pending Credit if you aren't going to get it, and on what criteria does Pending Validate? At HAL I only have 5 tasks in progress and none pending, though they do clear the database quickly. Something seems amiss. This might be a WUProp issue or perhaps some tasks just didn't report in time or were server aborted? That said, you would think you would still get credit here; aborted/crashed/not_reported_in_time... you still spent the time running the WU's.

I have noticed that the Pending hours seem to vanish fairly soon after the wuprop task reports from a computer that has completed and reported it's task but the Running time hours can take a while to increment. This means for a time it would look like hours had vanished.

I have not paid close enough attention to the actual hours to know if my totals are correctly increasing by the vanished pendings but they are increasing at reasonable rates based on what I am running.
____________

This is what I don't understand, I had over 4000 Hr's some Hr's ago on the ciencia-em-sua-casa Mr.Wilson App, I should have 4200-4300 by now if not more but now I only have 3,975.02 Hr's & 82.97 Pending, what the heck happened to the Hr's over 4000 that I had ... 0_o
____________
https://signature.statseb.fr/sig-1323.png

A few hours ago:
climateprediction.net UK Met Office Coupled Model Full Resolution Ocean 643.00 380.32

Now:
climateprediction.net UK Met Office Coupled Model Full Resolution Ocean 643.00 0.00

I have one model with 194h CPU time and 49h remaining.
The other has completed 188h and has an estimated 59h remaining.
Pending (h) should have moved to 382 rather than 0.00.
They are still running, so there wasn't a hiccup.

I guess there could be a db glitch or perhaps there is some sort of timeout and reset after so many hours/days Pending.
Maybe Pending should just be seen as a rough guide to how much work is unreported and what extra you might expect but only for some projects?

FreeHAL@home
3,810.38 219.23 - yesterday morning
3,816.72 140.63 -
3,827.23 170.43 -
3,852.33 157.03 - yesterday evening
3,891.57 308.97 - now

Thanks for debugging, the pending hours are back :)
climateprediction.net UK Met Office Coupled Model Full Resolution Ocean 643.00 385.37

I have started up a dual core host and it is running Asteroids only. I have just completed my first wuprop but my pending is showing only 3 hours not 6. Is there still a bug?
____________

Each time the WUProp Wu reports it will Update the Hr's up to that Point, then you will have to wait for the WUProp Wu to report again to report the Hr's since the last time it reported so it's not real Time your seeing here at the Project ...
____________
https://signature.statseb.fr/sig-1323.png

There was a bug. Some pending hours was deleted by error.
Everything should be back to normal as soon as each host has returned a workunint.

Still have the same Problem with the same App's Pending Hr's on the same Computer, actually the only Computer I'm running the App on right now until I get some sort of idea what's really happening.

SLinCA@Home heavy_lodci011eq32v0p125T1XZ40 - MIN:runtime~32h(checkpoint 2h),RAM~1GB,HDD~60MB 15.05 20.95

The WUProp Wu turned it's self in about 15 Min's ago showing only 20.95 Hr's Pending when in fact there's close to 200 Hr's run time on 8 Wu's for this App on the Box. It's been like this ever since I started running the App early yesterday. The Pending Hr's are way off on it & it's almost like it's counting it as a MT Wu. I checked at the SLinCA Project & don't see anything that say'[s it's MT Wu so I have no Idea what's going on with it.

All 8 Wu's are at about 95% Done & should finish in the next 3-4 Hr's I think & then I will have to wait for the WUProp Wu to report to see what kind of actual Hr's get reported for the XZ40 Wu's, should be over 200 Hr's but ???
____________
https://signature.statseb.fr/sig-1323.png

Okay the Wu's did Report a little bit ago & now show:

SLinCA@Home heavy_lodci011eq32v0p125T1XZ40 - MIN:runtime~32h(checkpoint 2h),RAM~1GB,HDD~60MB 213.48 0.00

So I did get close to 200 Hr's even though the WUProp Wu kept reporting way under that amount ... :)
____________
https://signature.statseb.fr/sig-1323.png

I am currently running a large application WUs on 20 different cores. They have been running over 10 hours on each core, which should equate to somewhere near 200 hours as I can see (minus the time of the current WuProp units in flight). Even at 5 computers if I take that 200 - 15 I still should show somewhere near 180 hours, yet I only show 40 hours crunched. Can this please be explained?