I'm taking the server down tonight (and probably most of the tomorrow).

I've made some big changes in the assimilator and validator which should help me implement new features and debug them in the future (mainly I rewrote them in Java so I don't have to worry about memory leaks or segmentation faults).

I'll be debugging them over the next couple days so expect some outages. Most notably, validation will be much stricter now; considering even though I've asked nicely we still see a lot of people trying to scam the system (scripts and single precision GPU clients for example). It's kind of sad that a few bad users have to ruin things for everyone (and make our work that much more difficult), but I guess thats the way things have to be.

On another note, we've had two papers accepted recently, one to the Distributed Applications and Interoperable Systems (DAIS 2010) conference (http://discotec.project.cwi.nl/index.php/DAIS:Main), and another to the World Congress on Evolutionary Computation (CEC 2010) http://www.wcci2010.org/topics/ieee-cec-2010. I'll be making these available after the validator/assimilator upgrades.

---

It's good to hear you're on top of things - I hope BOINC gives you enough capabilities to deal with the scammers. Will these changes affect the distribution of the anonymous platform apps? For instance, will new versions need to be validated before being allowed, assuming you have the capability to enforce validation?

at what time UTC are you planning to down the server ?

---

Join us at www.boincatpoland.org

It's good to hear you're on top of things - I hope BOINC gives you enough capabilities to deal with the scammers. Will these changes affect the distribution of the anonymous platform apps? For instance, will new versions need to be validated before being allowed, assuming you have the capability to enforce validation?

Once the new validator gets up and going validation will work as follows:

Any result that could potentially improve one of our searches will be validated (with a quorum of 2 or 3).

Previously, any result that wouldn't improve our searches we ignored. I'll be validating 50 - 100% of these for the next couple weeks so everyones error rate gets update correctly.

After everyone's error rate has leveled out, I'll drop the validation done on these workunits to whatever % the error rate of host returning the result is (minimum 10%).

So we'll still be validating every potentially good result, but we'll be using BOINC's adaptive validation for everything else.

---

It's good to hear you're on top of things - I hope BOINC gives you enough capabilities to deal with the scammers. Will these changes affect the distribution of the anonymous platform apps? For instance, will new versions need to be validated before being allowed, assuming you have the capability to enforce validation?

Once the new validator gets up and going validation will work as follows:

Any result that could potentially improve one of our searches will be validated (with a quorum of 2 or 3).

Previously, any result that wouldn't improve our searches we ignored. I'll be validating 50 - 100% of these for the next couple weeks so everyones error rate gets update correctly.

After everyone's error rate has leveled out, I'll drop the validation done on these workunits to whatever % the error rate of host returning the result is (minimum 10%).

So we'll still be validating every potentially good result, but we'll be using BOINC's adaptive validation for everything else.

How does this deal with CPCW (Cherry-Picking Credit Whoring)? I just got two very different credit per hour rates. The const_v2 searches are considerably faster than const_v3, but yield the same credit. Are you going to be holding a second set of statistics for people who abort longer-running tasks?

Is the new validator still being tweaked, seeing as a lot of us are getting work marked as invalid.

---

I don't know what's wrong Travis, but I'm not getting anything to work on.

Sun 04 Apr 2010 02:37:31 AM CEST Milkyway@home update requested by user
Sun 04 Apr 2010 02:37:34 AM CEST Milkyway@home Sending scheduler request: Requested by user.
Sun 04 Apr 2010 02:37:34 AM CEST Milkyway@home Not reporting or requesting tasks
Sun 04 Apr 2010 02:37:39 AM CEST Milkyway@home Scheduler request completed

It's almost 8 hours later now and I still get the same message of not reporting or requesting tasks :(
I don't know when I reported my last WU because I've been updating from Ubuntu 9.10 to 10.04 yesterday, so no logfiles :)

Sat 03 Apr 2010 09:04:44 PM CEST Starting BOINC client version 6.10.17 for i686-pc-linux-gnu
Sat 03 Apr 2010 09:04:44 PM CEST log flags: file_xfer, sched_ops, task
Sat 03 Apr 2010 09:04:44 PM CEST Libraries: libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15
Sat 03 Apr 2010 09:04:44 PM CEST Data directory: /var/lib/boinc-client
Sat 03 Apr 2010 09:04:44 PM CEST Processor: 4 AuthenticAMD AMD Phenom(tm) II X4 920 Processor [Family 16 Model 4 Stepping 2]
Sat 03 Apr 2010 09:04:44 PM CEST Processor: 512.00 KB cache
Sat 03 Apr 2010 09:04:44 PM CEST Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_l
Sat 03 Apr 2010 09:04:44 PM CEST OS: Linux: 2.6.32-19-generic-pae
Sat 03 Apr 2010 09:04:44 PM CEST Memory: 5.90 GB physical, 0 bytes virtual
Sat 03 Apr 2010 09:04:44 PM CEST Disk: 23.91 GB total, 17.05 GB free
Sat 03 Apr 2010 09:04:44 PM CEST Local time is UTC +2 hours
Sat 03 Apr 2010 09:04:44 PM CEST No usable GPUs found
Sat 03 Apr 2010 09:04:44 PM CEST Milkyway@home Found app_info.xml; using anonymous platform
Sat 03 Apr 2010 09:04:44 PM CEST SETI@home Found app_info.xml; using anonymous platform
Sat 03 Apr 2010 09:04:44 PM CEST Not using a proxy
Sat 03 Apr 2010 09:04:44 PM CEST Milkyway@home URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 126678; resource share 90
Sat 03 Apr 2010 09:04:44 PM CEST SETI@home URL http://setiathome.berkeley.edu/; Computer ID 5209294; resource share 300
Sat 03 Apr 2010 09:04:44 PM CEST Milkyway@home General prefs: from Milkyway@home (last modified 13-Sep-2009 08:17:55)
Sat 03 Apr 2010 09:04:44 PM CEST Milkyway@home Computer location: home
Sat 03 Apr 2010 09:04:44 PM CEST General prefs: using separate prefs for home
Sat 03 Apr 2010 09:04:44 PM CEST Reading preferences override file
Sat 03 Apr 2010 09:04:44 PM CEST Preferences limit memory usage when active to 4535.03MB
Sat 03 Apr 2010 09:04:44 PM CEST Preferences limit memory usage when idle to 5442.04MB
Sat 03 Apr 2010 09:04:44 PM CEST Preferences limit disk usage to 4.00GB

If you, or anyone else could help me out...

Thanks!

I don't know what's wrong Travis, but I'm not getting anything to work on.

Sun 04 Apr 2010 02:37:31 AM CEST Milkyway@home update requested by user
Sun 04 Apr 2010 02:37:34 AM CEST Milkyway@home Sending scheduler request: Requested by user.
Sun 04 Apr 2010 02:37:34 AM CEST Milkyway@home Not reporting or requesting tasks
Sun 04 Apr 2010 02:37:39 AM CEST Milkyway@home Scheduler request completed

You have to ask in order to receive. I guess your machine is paying off debt owed to SETI at this time.

F.

---

I don't know what's wrong Travis, but I'm not getting anything to work on.

Sun 04 Apr 2010 02:37:31 AM CEST Milkyway@home update requested by user
Sun 04 Apr 2010 02:37:34 AM CEST Milkyway@home Sending scheduler request: Requested by user.
Sun 04 Apr 2010 02:37:34 AM CEST Milkyway@home Not reporting or requesting tasks
Sun 04 Apr 2010 02:37:39 AM CEST Milkyway@home Scheduler request completed

You have to ask in order to receive. I guess your machine is paying off debt owed to SETI at this time.

F.

The problem is that you keep hitting the damn update button...stop doing that.
A user request (update) will never trigger a work fetch and will only increase the backoff time. You're makeing it even worse doing that.

---

Join Support science! Joinc Team BOINC United now!

I don't know what's wrong Travis, but I'm not getting anything to work on.

Sun 04 Apr 2010 02:37:31 AM CEST Milkyway@home update requested by user
Sun 04 Apr 2010 02:37:34 AM CEST Milkyway@home Sending scheduler request: Requested by user.
Sun 04 Apr 2010 02:37:34 AM CEST Milkyway@home Not reporting or requesting tasks
Sun 04 Apr 2010 02:37:39 AM CEST Milkyway@home Scheduler request completed

You have to ask in order to receive. I guess your machine is paying off debt owed to SETI at this time.

F.

The problem is that you keep hitting the damn update button...stop doing that.
A user request (update) will never trigger a work fetch and will only increase the backoff time. You're makeing it even worse doing that.

Oops!!!

Once the new validator gets up and going validation will work as follows:

Any result that could potentially improve one of our searches will be validated (with a quorum of 2 or 3).

Previously, any result that wouldn't improve our searches we ignored. I'll be validating 50 - 100% of these for the next couple weeks so everyones error rate gets update correctly.

After everyone's error rate has leveled out, I'll drop the validation done on these workunits to whatever % the error rate of host returning the result is (minimum 10%).

So we'll still be validating every potentially good result, but we'll be using BOINC's adaptive validation for everything else.

How is that suppose to work in regard to this -> http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1640 ???

Besides that, what's the problem with those results ?
When will it be fixed ?

---

Join Support science! Joinc Team BOINC United now!

Once the new validator gets up and going validation will work as follows:

Any result that could potentially improve one of our searches will be validated (with a quorum of 2 or 3).

Previously, any result that wouldn't improve our searches we ignored. I'll be validating 50 - 100% of these for the next couple weeks so everyones error rate gets update correctly.

After everyone's error rate has leveled out, I'll drop the validation done on these workunits to whatever % the error rate of host returning the result is (minimum 10%).

So we'll still be validating every potentially good result, but we'll be using BOINC's adaptive validation for everything else.

How is that suppose to work in regard to this -> http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1640 ???

Besides that, what's the problem with those results ?
When will it be fixed ?

The new validator should fix that (along with the new applications we're going to be releasing this week).

Travis, I take it the periodic feeder outage is something that will continue until the combination of new hardware and the new application are in place.

Feeder just bounced (1PM PDT).

---

Travis, I take it the periodic feeder outage is something that will continue until the combination of new hardware and the new application are in place.

Feeder just bounced (1PM PDT).

Yeah :( But we're working hard on getting those new applications up and running. I should have the validator for milkyway3 going and sending out workunits tonight. I have the OSX binaries compiled, and we also have CUDA linux. Anthony is working on the windows versions as we speak.

We'll probably make the swap within the week *fingers crossed*

---

OK -- I figure I'll be on the lookout from this side. Just figured to 'set expectations' at the right level for now.

Yeah :( But we're working hard on getting those new applications up and running. I should have the validator for milkyway3 going and sending out workunits tonight. I have the OSX binaries compiled, and we also have CUDA linux. Anthony is working on the windows versions as we speak.

We'll probably make the swap within the week *fingers crossed*

---