Posts by Neil Polson

1) Message boards : Number crunching : News of Projects and Apps Starting and Ending... (Message 3241)
Posted 10 Sep 2015 by Profile Neil Polson
Post:
I see the app Gravitational Wave search S6Bucket Follow-up #3 in the Active projects last 24 hours list but i have been running it the last 12 hours and nothing is showing in my account. I started universe-xray sources v3 at the same time and that is showing fine. Can this be sorted/corrected please.


Sorted and corrected it is! 26.53 hours... I'm impressed. Many,many thanks for doing this. Looks like Thyme will be pleased now too with 74.8 hours.
2) Message boards : Number crunching : News of Projects and Apps Starting and Ending... (Message 3238)
Posted 10 Sep 2015 by Profile Neil Polson
Post:
I see the app Gravitational Wave search S6Bucket Follow-up #3 in the Active projects last 24 hours list but i have been running it the last 12 hours and nothing is showing in my account. I started universe-xray sources v3 at the same time and that is showing fine. Can this be sorted/corrected please.
3) Message boards : Number crunching : News of Projects and Apps Starting and Ending... (Message 3130)
Posted 24 Jul 2015 by Profile Neil Polson
Post:
Bitcoin Utopia CudaMiner (Campaign #13) isn't being credited with hr's yet ... I don't see sgminer for 13 either but some wu's have been released ...

80935629 80250006 23 Jul 2015, 21:44:49 UTC 24 Jul 2015, 4:15:14 UTC Completed and validated 1,683.31 174.49 4,800.00 CudaMiner (Campaign #13) v0.01 (cuda)


There is also ¨CPUMiner (Campaign #13)¨ and ¨bfgminer (Campaign #13) (for 20+GH/s Blade erupter ASICs)¨.
4) Message boards : Number crunching : Validate error (Message 2599)
Posted 26 Jan 2015 by Profile Neil Polson
Post:
My 2 did not get the hours credited.
5) Message boards : Number crunching : Validate error (Message 2589)
Posted 25 Jan 2015 by Profile Neil Polson
Post:
Looks like they are validating again now. Any chance of getting the incorrect "validate errors" re-validated?
6) Message boards : Number crunching : Validate error (Message 2585)
Posted 25 Jan 2015 by Profile Neil Polson
Post:
I'm seeing a lot of these validate errors on many peoples hosts since about 8:45 UTC. Problem with the tasks or the server?
7) Message boards : Number crunching : Where to report missing apps? (Message 2244)
Posted 8 Jun 2014 by Profile Neil Polson
Post:
Primegrid has a new sub-project called ESP with it's app Extended Sierpinski Problem (LLR). It's not showing yet on my stats.
8) Message boards : Number crunching : facteur correction (Message 2167)
Posted 19 Apr 2014 by Profile Neil Polson
Post:
I have seen "facteur correction: 0.666667 (2/3.000000)" and "facteur correction: 0.500000 (1/2.000000)" in some of my hosts <stderr_txt> outputs. This shows up when I'm running the new `Quality of Service using Volunteer Computing´ app from the QOS project. Is there a reason this is happening? It results in less run time being reported for that app. ie 1 hour instead of 1.5 for the 2/3 and 0.75 hours for the 1/2. It's difficult enough getting the tasks let alone being credited less for them!
Example:
<core_client_version>7.2.42</core_client_version>
<![CDATA[
<stderr_txt>
No NVIDIA library found
No ATI library found.
No OpenCL library found
No NVIDIA library found
No ATI library found.
No OpenCL library found
08:01:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:02:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:03:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:04:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:05:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:06:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:07:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:08:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:09:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:10:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:11:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:12:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:13:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:14:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:15:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:16:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:17:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:18:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:19:09 (2188): facteur correction: 0.500000 (1/2.000000)
08:20:10 (2188): facteur correction: 0.500000 (1/2.000000)
08:21:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:22:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:23:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:24:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:25:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:26:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:27:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:28:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:29:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:30:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:31:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:32:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:33:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:34:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:35:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:36:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:37:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:38:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:39:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:40:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:41:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:42:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:43:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:44:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:45:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:46:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:47:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:48:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:49:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:50:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:51:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:52:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:53:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:54:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:55:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:56:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:57:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:58:11 (2188): facteur correction: 0.500000 (1/2.000000)
08:59:11 (2188): facteur correction: 0.500000 (1/2.000000)
09:00:11 (2188): facteur correction: 0.500000 (1/2.000000)
09:01:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:02:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:03:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:04:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:05:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:06:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:07:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:08:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:09:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:10:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:11:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:12:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:13:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:14:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:15:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:16:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:17:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:18:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:19:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:20:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:21:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:22:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:23:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:24:12 (2188): facteur correction: 0.500000 (1/2.000000)
09:25:13 (2188): facteur correction: 0.500000 (1/2.000000)
09:26:13 (2188): facteur correction: 0.500000 (1/2.000000)
09:27:13 (2188): facteur correction: 0.500000 (1/2.000000)
09:28:13 (2188): facteur correction: 0.500000 (1/2.000000)
09:29:13 (2188): facteur correction: 0.500000 (1/2.000000)
09:30:13 (2188): facteur correction: 0.500000 (1/2.000000)
09:31:14 (2188): facteur correction: 0.500000 (1/2.000000)
09:32:14 (2188): facteur correction: 0.500000 (1/2.000000)
09:33:14 (2188): facteur correction: 0.500000 (1/2.000000)
11:58:22 (2188): called boinc_finish

</stderr_txt>
]]>
9) Message boards : Number crunching : Pending Hr's (Message 1656)
Posted 20 Sep 2013 by Profile Neil Polson
Post:
I've just noticed WUProp@Home Data collect version 3 has appeared in my apps list instead!
10) Message boards : Number crunching : Pending Hr's (Message 1654)
Posted 20 Sep 2013 by Profile Neil Polson
Post:
All my pending (and completed) hours have disappeared from my last reported 3.52 tasks after receiving the new version 4.01 app. My hosts activity for the period are blank also.
11) Message boards : Number crunching : Stats Update (Message 1187)
Posted 4 May 2013 by Profile Neil Polson
Post:
Are the stats not being updated or is there a problem with the new 3.5 app? I've not had any hours updated since running the new app and I've even lost the pending hours from my final 3.42! (Running win7x64 on 7.0.64)
12) Message boards : Number crunching : MT tasks count only one thread time (Message 1109)
Posted 27 Mar 2013 by Profile Neil Polson
Post:
You can add Edges@Home Autodock VINA app to the list too.


??? The Edges VINA only use 1 Thread Per CPU & isn't a MT Wu ...

That's what i thought until I ran it on my Winx64 dual core host. It immediately used both cores and the run time was 2x cpu time! Maybe it's a bug? I will post on their forum.
13) Message boards : Number crunching : MT tasks count only one thread time (Message 1105)
Posted 26 Mar 2013 by Profile Neil Polson
Post:
You can add Edges@Home Autodock VINA app to the list too.
14) Message boards : Number crunching : Pending Hr's (Message 1060)
Posted 14 Mar 2013 by Profile Neil Polson
Post:
I have started up a dual core host and it is running Asteroids only. I have just completed my first wuprop but my pending is showing only 3 hours not 6. Is there still a bug?
15) Message boards : News : Application updated (Message 907)
Posted 17 Feb 2013 by Profile Neil Polson
Post:
I've just noticed my reported data hasn't changed all night (approx 8 hours). Is there a problem?
16) Message boards : Number crunching : Checkpointing (Message 616)
Posted 27 Sep 2011 by Profile Neil Polson
Post:
It appears that the new app Data collect version 3 v3.25 (nci) is failing to checkpoint properly. On a restart the task starts from the beginning. My windows host states ''Erreur assignation project_name (node project)'' and then ''checkpoint failed File exists''every minute in the </stderr_txt>.
17) Message boards : Number crunching : Project is temporarily shut down for maintenance (Message 584)
Posted 15 Jul 2011 by Profile Neil Polson
Post:
Don't know what happened overnight but this morning all of yesterdays and todays tasks for my hosts have been awarded less than 1 credit.
18) Message boards : News : New application released (Message 555)
Posted 18 Jun 2011 by Profile Neil Polson
Post:
None of them seem to be validating though. Server states ''Workunits waiting for validation 7,894''.
19) Message boards : Number crunching : deadline (Message 190)
Posted 24 Apr 2010 by Profile Neil Polson
Post:
Noticed the run time has halved but the credits have remained the same! I am by no means complaining. :-)




©2025 Sébastien