I ran GPU app for about 6 hours, and WUProp recorded only 0.53 hour.

Check WUprop error log - "facteur correction: 0.533333 (8/15.100000)"
You have exceeded the number of CPU threads by almost twice.
View configurations for all active tasks
for example XaNSoNS BOINC for GPU - 0.975C + 1NV

<avg_ncpus>1</avg_ncpus>

This is misleading the BOINC task manager, and at the same time WUprop
The task should be limited to something similar to "<cmdline> --nthreads 1.000000 </cmdline>"

So as not to lose hours and minutes - recalculate the CPU requirements for all tasks (in app_config) so that they do not exceed the actual value by more than 0.99 (8/8.99 = 1.0)

This looks like side effect of way how BOINC 7.6.33 works - sometimes after single thread WU ends it starts multi-threaded one, but does not suspend other single-threaded WUs, they runs in parallel for about half a minute before they got suspended. This could explain why sometimes there were 15 threads on 8 logical cores. However even permanent correction factor 0.5 does not explain why I got half an hour only, I should have about 3 hours.

---

In the last 12h (based on host activity for one machine) I've 12.2h from 2 GPU's exclusively running this Xansons GPU app. I seem to have had a fairly steady supply of these GPU tasks, but prior to the last 12h next to nothing was being recorded by WUProp - so far I've only been credited with 15.12h for the GPU app in total. 2GPU's for 24h = 48h, so that's way out. Even two WUprop tasks by 2GPU's =36h.

The CPU hours are also down. 59.93h - from 7CPU's over ~24h! Should be close to 168h.
Even if I had only returned 3 WUProp tasks in that time it would be 7*18h=126h. Again 48h reported in last 2 WUProp reports is about half what I would expect. But before that it wasn't really working. Unless I missed by task supply dry up & reappear (which it might have done), I think something was improved/started working at WUProp, but I would not say it's 'fixed'...

For the GPU app, the CPU Time & Elapsed Time are the same. Each GPU app does use a full CPU thread.
The CPU time & Elapsed Times for the CPU app don't add up.
The CPU time divided by the number of logical CPU's should = Elapsed time, but it's less than the elapsed time. 30% less on one task I looked at.
Looking at task manager however, I can see that the MT app isn't always using it's full asignment of logical CPU's. It would be more accurate to say I'm using up to 7 logical CPU's; my total CPU usage is sometimes ~85% & sometimes ~60%. Is this down to Boinc 7.6.33 not facilitating better utilization of CPUs, down to the app, or a bit of both?

I can confirm this. For example, I have been running 100+ threads for Xansons CPU app, for a couple days now. And my hours for the CPU app show only 1225. It should be well over 5k by now. Something is not being calculated properly somewhere in the chain of events.

---

Reno, NV
Team: SETI.USA

I can confirm this. For example, I have been running 100+ threads for Xansons CPU app, for a couple days now. And my hours for the CPU app show only 1225. It should be well over 5k by now. Something is not being calculated properly somewhere in the chain of events.

Looking at the Stderr output of most of my WuProp tasks I see I'm getting the "facteur correction ERROR" that we were experiencing on the Monkeys V1 tasks, I suspect this "bug" has NEVER BEEN FIXED.

Error Message on one of my Intel dual-core PC's:
facteur correction: 0.666667 (2/3.050000)

Error Message on my Quad core Intel has TWO different values:
facteur correction: 0.571429 (4/7.050000)
facteur correction: 0.800000 (4/5.050000)

I see it on ALL my PC's that are MULTI-CORE and run XANSONS for COD and Monkeys. I do NOT see the "fractional hours" error on my OLD single core that does not run XANSONS.

In short the PROBLEM APPEARS TO BE SOLEY WITH WuProp's TRACKING.

The reduction in hours was discussed here among other places: Only half (50%) elapsed time registered.

---

app_config.xml for Xansons helped me, thanks. With 3 tasks running on Nvidia 1070 their runtimes are longer and WUProp is able to capture most of it. For last 24h I got 69.42h - not bad, but still 2.5h is missing. Part of this was spent on task switching for sure.

I also decided to run CPU tasks with 4 threads and got 66.53h for last 24h. I am not sure how much time is lost here, for now I will keep it as-is.

It also turned out that Xansons apps for Linux are sent to machines with kernel 3.16 or newer, and new glibc/libstdc++ libs. I am in contact with admin regarding this. He was able to recompile CPU and OpenCL apps to link them statically with these libs, and I confirmed that they works on my system. However for some reason I am unable to install them using app_info.xml, server does not allow to use anonymous platform. I am also waiting for CUDA app, admin still has some issues with linking it statically with glibc/libstdc++ libs. I gave him some hints, and I hope he will be able to do this soon.

---

Sourcefinder is going to test another source finding app called SoFiA, so we can expect new app from this project soon. Source: https://sourcefinder.theskynet.org/duchamp/forum_thread.php?id=207

---

New app at ODLK: odlk3@home 1.00
Currently only available for Linux.

---

Life is Science, and Science rules. To the universe and beyond
Member of BOINC@Heidelberg
My BOINC-Stats

New application odlk3@home is active

Linux & Windows x86_64

New application Amicable Numbers up to 2^64 (double check) is active

Ending...

New application odlk3@home is active

Lets hope the WUProp app/server is/can tally up the correct hours for the odlk3 work we are doing now, as it's not yet listed in New / Intermittent applications...

Amicable Numbers up to 2^64 (double check) was only announced here 6days ago!

I've suspended the odlk3@home tasks on a couple of systems as the app hasn't turned up here yet - don't want to waste the hours as that defeats the purpose of WUProp!
The tasks have a 7day shelf life.

I've suspended the odlk3@home tasks on a couple of systems as the app hasn't turned up here yet - don't want to waste the hours as that defeats the purpose of WUProp!
The tasks have a 7day shelf life.

Yeah,I grabbed a couple hundred on my 2p and paused the project until a post gets made in the sticky. Hopefully soon.

Yeah,I grabbed a couple hundred on my 2p and paused the project until a post gets made in the sticky. Hopefully soon.

On a 2GHz CPU you might need ~300 to reach 100h. I've 500+ returned, but I'll wait for a bit before proceeding any further; no lack of other goals...

I've suspended the odlk3@home tasks on a couple of systems as the app hasn't turned up here yet - don't want to waste the hours as that defeats the purpose of WUProp!
The tasks have a 7day shelf life.

odlk3@home is added now, and looks that hours spent before are correctly added.

---

I've suspended the odlk3@home tasks on a couple of systems as the app hasn't turned up here yet - don't want to waste the hours as that defeats the purpose of WUProp!
The tasks have a 7day shelf life.

odlk3@home is added now, and looks that hours spent before are correctly added.

odlk odlk3@home 1.27 1.27

Yep, I was backdated the bit I got while downloading units.

http://cosmologyathome.org have an app called camb_legacy.
It's been around (possibly on & off) since cc Oct2015 but I don't have any hours for it here & there hasn't been any in the last 24h (according to WUProps list of active projects in the last 24h). Most top contributors here don't have it, at least not from it's current site. Does WUProp just not recognize these tasks are running, or what?

http://cosmologyathome.org have an app called camb_legacy.
It's been around (possibly on & off) since cc Oct2015 but I don't have any hours for it here & there hasn't been any in the last 24h (according to WUProps list of active projects in the last 24h). Most top contributors here don't have it, at least not from it's current site. Does WUProp just not recognize these tasks are running, or what?

I think it is called Cosmology@Home CAMB. I currently have 1,192.22 hours and 5.95 new hours and matches EXACTLY what i ran as camb_legacy.

---

http://cosmologyathome.org have an app called camb_legacy.
It's been around (possibly on & off) since cc Oct2015 but I don't have any hours for it here & there hasn't been any in the last 24h (according to WUProps list of active projects in the last 24h). Most top contributors here don't have it, at least not from it's current site. Does WUProp just not recognize these tasks are running, or what?

I think it is called Cosmology@Home CAMB. I currently have 1,192.22 hours and 5.95 new hours and matches EXACTLY what i ran as camb_legacy.

Yes, it it this one.

---

Yeah, the camb_legacy app is counting towards Cosmoloy@Home CAMB.
From their forums I got the impression they stopped using the Camb app to allow a virtual app, but too many had issues with the virtual app (as usual) so they re-released the Camb app, possibly listing it by it's original name; some crunchers (not me) have a deprecated app called camb_legacy listed under a project called cosmohome. I guess Cosmoloy@Home was originally called cosmohome and the Camb app was originally called camb_legacy.

- Thanks

I've got 11k hours in CAMB from the Pentathlon. It was available last month.