I just noticed that I was only shown as having about 63 days of credit on the new WCG cancer project when I actually have over 200 days of run time. What's going on?

Mine seems to be working fine:



(WCG has fewer hours as WUProp doesn't need to wait for validation.)

I just noticed that I was only shown as having about 63 days of credit on the new WCG cancer project when I actually have over 200 days of run time. What's going on?

You cheat by multiplying by 8 the number of cores.
So, only 1/8 of the computing hours will be validated.

---

I just noticed that I was only shown as having about 63 days of credit on the new WCG cancer project when I actually have over 200 days of run time. What's going on?

You cheat by multiplying by 8 the number of cores.
So, only 1/8 of the computing hours will be validated.

I cheat? Really? Interesting response but your math doesn't add up. If I was only getting 1/8 of the run time validated by the project then WUProp should be showing only about 30 days of run time. If I'm not going to get credit for the same amount of run time here that the project gives me then I see no point in running WUprop. I've received no run time credit here at all for the last beta that ran for 2 days. CYA.

---

I've received no run time credit here at all for the last beta that ran for 2 days. CYA.

Last I checked, the beta test appears as a different task entirely, and shows up as something along the lines of "Beta Test" instead of the actual project name. I can't verify this, however, as you have your account data hidden.

I've received no run time credit here at all for the last beta that ran for 2 days. CYA.

Last I checked, the beta test appears as a different task entirely, and shows up as something along the lines of "Beta Test" instead of the actual project name. I can't verify this, however, as you have your account data hidden.

The task is listed as "beta test" however there has been no run time credit for the 2 days it was running earlier this week. Actually it should have shown up as "MCM1 beta test" because it was an entirely different beta test run. I'm not the only person noticing that there are projects being run that are not being granted run time here. Others at SETIUSA have noticed the same thing. Until this issue is resolved I will stop running WUProp.

Here the Beta test was just called

World Community Grid 	Beta Test

The reason it wasn't called,

World Community Grid 	Mapping Cancer Markers Beta

was because it was a pre-release Beta of an unnamed/unannounced project. Subsequent testing of MCM will indicate the sub-project. That's just down to how WCG does things, and it's good for here as the next new project will be tested and hopefully count towards the same app (but that's down to seb).
The Beta app name as I viewed it from a running WU's properties within Boinc Manager was Beta Test 7.19.
The present (non-Beta) app is called Mapping Cancer Markers 7.24 but just appears here as, World Community Grid Mapping Cancer Markers.

My testing of the Beta revealed that it sort-off restarted from zero if it was suspended in any way.
I suspect that may be the source of your annoyance - the WUProp app is somehow being tricked into thinking the task is just starting when it's actually restarting and had already ran for some time. WCG has suspended the project. Maybe the problems are related?

My suggestion is to set Boinc Manager's Switch Between Apps every Preference setting to a very high number such as 990h and allow the CPU to be used while you use the system.

Hope that helps.

BTW. I just noticed that when you restart a system, and Boinc auto-starts, it runs a CPU Benchmark test. This suspends the WUProp app. However, when this is occurring Boinc still uploads work!
If my understanding of how WUProp works, this is an issue as you will not get credit at WUProp for that work. Some of it might appear in Pending but will never make it to the Running Time hours tally.
Maybe one for the devs?

---

=sticky tape=

There was a second beta test the was exclusive to MCM1 to test issues with the first release of MCM1 tasks.

Project Name: Beta - Mapping Cancer Markers
Created: 11/15/2013 14:52:14
Name: BETA_MCM1_9999975_5347
Minimum Quorum: 2
Replication: 2

Whatever the beta test was called I received no credit for the final 2 days of the MCM beta run and like I stated before I received nowhere near the amount of credit here for the run time I have on the MCM1 project.
If you're trying to upgrade your run time badges here and you're not receiving full credit for the amount of run time the project says you have then why bother running WUProp at all? Not worth it to me.

My testing of the Beta revealed that it sort-off restarted from zero if it was suspended in any way.
I suspect that may be the source of your annoyance - the WUProp app is somehow being tricked into thinking the task is just starting when it's actually restarting and had already ran for some time. WCG has suspended the project. Maybe the problems are related?

WCG suspended the project because the same tasks were getting sent out over and over again even though they had different batch numbers. The MCM beta was to test a fix for that issue.

BTW. I just noticed that when you restart a system, and Boinc auto-starts, it runs a CPU Benchmark test. This suspends the WUProp app. However, when this is occurring Boinc still uploads work!
If my understanding of how WUProp works, this is an issue as you will not get credit at WUProp for that work. Some of it might appear in Pending but will never make it to the Running Time hours tally.
Maybe one for the devs?

Add the <skip_cpu_benchmarks>1</skip_cpu_benchmarks> tag to your cc_config file to stop that annoying process. Mine are all set to skip benchmarks but I'm not even sure the newer versions of the BOINC client even run benchmarks any more.

I'm not even sure the newer versions of the BOINC client even run benchmarks any more.

They do.

Version 4.13 shoud fix the problem.

---

Version 4.13 shoud fix the problem.

It seems to be working better for some projects but not for all.

Version 4.13 shoud fix the problem.

There are still discrepencies with projects that run with a VM (Beauty@LCN) and projects that are NCI.(Quake catcher network)
Beauty@LCN has 96 hours of credit for me on their website. Only 56 hours of credit here with 3.60 hours pending.
QCN has 144 hours of run time and only 63 hours pending here.

I didn't see what's wrong.
On last 24 hours, your host runs 24 hours on QCN and Beauty:
http://wuprop.boinc-af.org/activity.py?hostid=49078&preselect=day

---

My Running time (hours) and pending hours for Docking are always rising, but Pending never seems to move to Running time (hours):

Docking Charmm 34a2 13,835.77 1,779.27

Might this be due to a service install somewhere?

---

=sticky tape=

Is there a limit to how many workunits WuProp can report at a time? Is it capped at 8 or something? This could explain why many people find they're missing quite a few hours.

Like Nanoprobe, WuProp only credits me with 110 hours on WCG MCM, but WCG reports i have 81+ days of results, plus 4 pages of pendings. This discrepancy is retarded beyond words...unless WuProp has some cap where it can't report every WU from a given session. I don't just mean a cap on the number of WUs completed, but the number of WUs completed from *different projects* might be causing WuProp to miss quite a bit.

WCG isn't the only project where i'm missing hours. In fact nearly anything i run on my 3770K system is horribly under-reported, but, including WuProp, i have 9 NCI WUs crunching simultaneously on that computer, along with 4 GPUs and whatever is left of the 8 CPU threads. WuProp reports the earthquake-related NCI WUs just fine. Never misses a beat. Anything else...well, let's just say i gave up on any hopes of decent looking WuProp badge a long time ago.

Your 3770K didn't report any workunits since November 8th: http://wuprop.boinc-af.org/activity.py?hostid=4678

---

Right...and i wonder why that would be since that computer runs 24/7 with a wired 30 Mb/s internet connection. And before Nov. 8th there are several more gaps ranging from several hours to several days. My cat must've done it. That's it :p

Oh well. Nothing can be done about it but wait around around for the next gap and look for clues.