How frequently are the results updated?

TIA

---

A very good question, which I could not find answer for...

Recently I have added few PC to this project and I could find them under my account, but no sign of collected WU data from them. Can somebody explain what is the general rule for updating database with collected information?

---

The results are updated every hours.

---

The results are updated every hours.

Say what???

---

In that case results from one of my PC has been lost or assigned to wrong OS.

Computer ID 7417: Pentium(R) Dual-Core CPU E5200, running Dotsch_UX (64bit Ubuntu) has calculated few WU for World Community Grid. However at result spreadsheet for project WCG there is no duration time for E5200 running Linux 64 bits.

Can you check what happen?

---

WCG has no applications Linux 64bits.
You calculate WU for Linux 32bits.

---

You are right - I have just checked WCG FAQ:

========
Does World Community Grid offer a 64 bit version of the BOINC software?

No. The science applications are only available in 32 bit so everything we do, including validation, is offered in 32 bit. Going forward, we will re-evaluate the feasibility, cost and timing of offering a 64 bit version of the BOINC software to the member community.
========

So my 64bit Linux system calculates 32bit application for WCG.

However to me current spreadsheet organization could be misleading.
It classifies result based on WU build, not system where it was crunched.
Maybe it would be better to somehow distinguish those two things?

Are there any projects which send the same WU for 32bit and 64bit systems, but they complete faster on one of them? What happens then? You place result into brackets (X-Y)?

---

The results are updated every hours.

Hi Sebastian,
A month ago I started BOINC on an Atom D525 (Wuprop one week ago), but there are still no 'results' for this cpu for the projects I crunch. Is there a minimum threshold before publishing ?

Hi John,

On this page, I see data for many projects.
Which projects are missing?

---

Hi John,

On this page, I see data for many projects.
Which projects are missing?

Hello again,
Since I last wrote, Aqua and Wuprop have appeared - seems like it takes up to a couple of weeks to work through. Dnet and Virtual Prairie are still missing - maybe Wuprop doesn't recognise them as valid ?

The statistics for AQUA on my machine type can't include my results - out of range for several weeks - so I'm doubtful about WUPROP's accumulations.

The application collects data every 5 minutes.
The compute time couldn't be collected when the AQUA workunit finished and was reported to AQUA project between two cycles.

---

The application collects data every 5 minutes.
The compute time couldn't be collected when the AQUA workunit finished and was reported to AQUA project between two cycles.

Does that mean, that with the tag <report_results_immediately>0|1</report_results_immediately> set to "1" in the cc_config, those data will never be returned to you?

---

Grüße vom Sänger

The project Eon2 may have some rather short WUs, especially on fast systems, lasting as little as a minute. Does it mean that they may be missed when collecting data?

TIA

---

The application collects data every 5 minutes.
The compute time couldn't be collected when the AQUA workunit finished and was reported to AQUA project between two cycles.

Does that mean, that with the tag 0|1 set to "1" in the cc_config, those data will never be returned to you?

Yes, with this tag, the compute time will never be returned.
Other datas (RAM, deadline, download, upload, checkpoint) will be returned.

---

The project Eon2 may have some rather short WUs, especially on fast systems, lasting as little as a minute. Does it mean that they may be missed when collecting data?

TIA

Some workunits may be missed but not all.
http://wuprop.boinc-af.org/results.py?data=duree&projet=eon2&application=eOn%20Client

---

The application collects data every 5 minutes.
The compute time couldn't be collected when the AQUA workunit finished and was reported to AQUA project between two cycles.

Does that mean, that with the tag <report_results_immediately>0|1</report_results_immediately> set to "1" in the cc_config, those data will never be returned to you?

Yes, with this tag, the compute time will never be returned.
Other datas (RAM, deadline, download, upload, checkpoint) will be returned.

OK, as I don't crunch GPUGrid any more without manually fiddling, I have set it back to "0". More data from my machine :)

---

Grüße vom Sänger

Does that mean, that with the tag <report_results_immediately>0|1</report_results_immediately> set to "1" in the cc_config, those data will never be returned to you?

Yes, with this tag, the compute time will never be returned.
Other datas (RAM, deadline, download, upload, checkpoint) will be returned.

I really think this information should be made clear from the homepage.

The application collects data every 5 minutes.
The compute time couldn't be collected when the AQUA workunit finished and was reported to AQUA project between two cycles.

Does that mean, that with the tag <report_results_immediately>0|1</report_results_immediately> set to "1" in the cc_config, those data will never be returned to you?

Yes, with this tag, the compute time will never be returned.
Other datas (RAM, deadline, download, upload, checkpoint) will be returned.

OK, this is yet another reason why having a user-definable "at least" delay for reporting results is a good idea. The <RRI> tag mentions an "inbuild 60 second delay from completion of result upload", but the tag could contain something like the number of minutes or seconds to delay as well...

Peter

The application collects data every 5 minutes.
The compute time couldn't be collected when the AQUA workunit finished and was reported to AQUA project between two cycles.

Does that mean, that with the tag <report_results_immediately>0|1</report_results_immediately> set to "1" in the cc_config, those data will never be returned to you?

Yes, with this tag, the compute time will never be returned.
Other datas (RAM, deadline, download, upload, checkpoint) will be returned.

Is this issue fixed? Runtime for each WU is stored in job_log_project_URL.txt files in BOINC data directory, where it stays forever (or at least until the user deletes the file).

---