WUProp not awarding credit.
log in |
Message boards : Number crunching : WUProp not awarding credit.
Author | Message |
---|---|
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? | |
ID: 1837 · Rating: 0 · rate: / Reply Quote | |
Mine seems to be working fine: | |
ID: 1839 · Rating: 0 · rate: / Reply Quote | |
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. ____________ | |
ID: 1840 · Rating: 0 · rate: / Reply Quote | |
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? 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. ____________ | |
ID: 1844 · Rating: 0 · rate: / Reply Quote | |
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. | |
ID: 1845 · Rating: 0 · rate: / Reply Quote | |
I've received no run time credit here at all for the last beta that ran for 2 days. CYA. 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. | |
ID: 1846 · Rating: 0 · rate: / Reply Quote | |
Here the Beta test was just called | |
ID: 1852 · Rating: 0 · rate: / Reply Quote | |
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 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. 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! 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. | |
ID: 1856 · Rating: 0 · rate: / Reply Quote | |
I'm not even sure the newer versions of the BOINC client even run benchmarks any more. They do. | |
ID: 1857 · Rating: 0 · rate: / Reply Quote | |
Version 4.13 shoud fix the problem. | |
ID: 1858 · Rating: 0 · rate: / Reply Quote | |
Version 4.13 shoud fix the problem. It seems to be working better for some projects but not for all. | |
ID: 1861 · Rating: 0 · rate: / Reply Quote | |
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. | |
ID: 1863 · Rating: 0 · rate: / Reply Quote | |
I didn't see what's wrong. | |
ID: 1864 · Rating: 0 · rate: / Reply Quote | |
My Running time (hours) and pending hours for Docking are always rising, but Pending never seems to move to Running time (hours): | |
ID: 1871 · Rating: 0 · rate: / Reply Quote | |
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. | |
ID: 1899 · Rating: 0 · rate: / Reply Quote | |
Your 3770K didn't report any workunits since November 8th: http://wuprop.boinc-af.org/activity.py?hostid=4678 | |
ID: 1901 · Rating: 0 · rate: / Reply Quote | |
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 | |
ID: 1902 · Rating: 0 · rate: / Reply Quote | |
Message boards :
Number crunching :
WUProp not awarding credit.