Hi there,
I don't understand, how badges are earned in this community.
Of course you can find that the 'lowest' badge can be earned by 20 apps > 100 hours.
I suppose that does not mean you count the points earned, but run-time - right?
Where can I find the statistics which shows me my used CPU/ GPU(?)-time for my projects? Is this somewhere here in the project or e.g. in Free-DC or similar portals?

Sorry, just a beginners question, but I was not able to find a description for that...

Thank you!
Claus

For WUProp it is about running applications from other projects. Once you run 100 processor hours, CPU or GPU, then the star changes color next to the app name. At 200 hours it turns silver. When you get 20 applications over 100+ hours then you get your 1st badge at WUProp. The Stars go up in color as the 1st 20 apps go higher in hours.

https://signature.statseb.fr/index.py?badge=117

The Results tab at the bottom of the page has the project data from everyone. Your own page collects hours per app, but not whether it is CPU or GPU (unless it's in the app name). Like Asteroids is the same app name for both CPU and GPU. The Results page can show data from everyone, maybe you can find some of your own processor data in it.

Thank you for your fast reply!
In addition: I'm running some projects (like SETI@home) also since a couple of years. Is it needed to have WUProp@Home be installed in parallel to the projects running on my PC to get the hours added up or does this project also takes the hours somewhere out of the result pages from e.g. SETI@home, also from the past?

(I checked my Seti results: SETI@home classic CPU time 10,464 hours
and even Seti is not mentioned in my results list...)

You must install WUProp (this project) in order for it to gather information. It runs in memory (non-cpu intensive) so does not hurt normal operation. Each work unit takes 1 hours to run.

Conan

---

You must install WUProp (this project) in order for it to gather information. It runs in memory (non-cpu intensive) so does not hurt normal operation. Each work unit takes 1 hours to run.

Conan

Mine take 6 hours to run:


Application
Data collect version 4 4.20 (nci)
Name
data_collect_v4_1594224002_43827
State
Running (non-CPU-intensive)
Received
7/11/2020 8:37:48 AM
Report deadline
7/18/2020 8:37:47 AM
Estimated computation size
1,000 GFLOPs
CPU time
00:00:03
CPU time since checkpoint
---
Elapsed time
04:30:04
Estimated time remaining
01:29:41
Fraction done
75.069%
Virtual memory size
7.32 MB
Working set size
10.90 MB
Directory
slots/1
Process ID
7280
Progress rate
16.560% per hour
Executable
data_collect_v4_4.20_windows_x86_64__nci.exe

You are correct, they used to take 1 hour but for the last year or so have taken 6 hours, to take the load off the server.

Bit of a brain fart there, all good.

Conan

---

You are correct, they used to take 1 hour but for the last year or so have taken 6 hours, to take the load off the server.

Bit of a brain fart there, all good.

Conan

Not a problem, I was hoping mine were having problems not that you were mistaken. I'd love to see some other Projects extend their own workunits to help solve their own Server problems too.