Crikey! it works on Macs :O

I won’t be ready to concur until I see some results safely reported or, better yet, validated. ;)

Crikey! it works on Macs :O

I won’t be ready to concur until I see some results safely reported or, better yet, validated. ;)

Of of course, that was pleased surprise as it would seem to corroborate the Chicken's posts that the optimised apps are not at fault but the anonymous platform mechanism in the scheduler instead.

Are you sure it is running the right app? I don't know much about [modern] Macs . sorry

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

I just checked the 'puter and the 2 WU's were done crunching but didn't report and didn't download any new ones.

Sooooo, I went through the same process again, renaming, then up updated - the 2 WU's uploaded and 2 more were downloaded.

The two new ones started crunching on chicken soup right away, didn't have to reboot the computer this time.

I got the following message on the 2 uploaded WU's, that they were refused cause they had already been reported.

5/19/2007 2:33:01 PM|SETI@home|Sending scheduler request: Requested by user
5/19/2007 2:33:01 PM|SETI@home|Requesting 1728 seconds of new work, and reporting 2 completed tasks
5/19/2007 2:33:07 PM|SETI@home|Scheduler RPC succeeded [server version 509]
5/19/2007 2:33:07 PM|SETI@home|Message from server: Completed result 27fe05aa.20439.6258.29822.3.207_1 refused: result already reported as success
5/19/2007 2:33:07 PM|SETI@home|Message from server: Completed result 27fe05aa.20439.6258.29822.3.217_0 refused: result already reported as success

(I cut alot of it out to just show the two messages, if you want to see it all, let me know)

Soooooo, I went to the SETI page to see what the results page said. It gave me 'requested credits' of 48.72 for both with 'granted credits' pending.

http://setiathome.berkeley.edu/result.php?resultid=535920863
http://setiathome.berkeley.edu/result.php?resultid=535920781

Hey, for the hell of it, I'll throw in another twist, lol.

WU xxxx863 in the steddr out it mentions chicken soup
WU xxxx781 in the steddr out it doesn't mention chicken soup

My migrane is getting bigger and I've still fallen and can't get up.

---

YES!!! I was just about to post the same thing.

The following has worked for me on three systems - two late version 5.8 BOINC, and a 5.3.12.tx. All were service installs, running appropriate Chicken 2.2B, and had run completely dry.

Recipe:

Rename app_info.xml so it won't be recognised
Restart BOINC (service)
Update SETI - may not get through first time, but keep trying
Restore app_info.xml to original name
Wait until all transfers have finished
Restart BOINC (service)

Outcome - decent sized cache (if I haven't nabbed them all already, LOL), still running optimised, time to open a beer.

As illogical as it sounded when I first read it, it seems to be true.

Just went through the same procedure on two of my hosts, and voila, results reported, new WUs downloaded, happily crunching again.

So I can recommend the above.

Now all that remains to be investigated is WHY this happens, and whether we need to adjust all app_info.xml files that are out there. If so, that'd be a major blow because many people will be left without work and without knowing why.

Regards,
Simon.

Just a thought.....

The current SETI app. is 5.15, and the current optimized apps are based off of 5.15.

The servers need to know the version so that they may deliver the right work.

Most of the app_info.xml files report that they're compatible with everything from 5.12 to 5.17 -- from the past into the future.

What happens if one "edits down" the app_info.xml to just 5.15?

-- Ned

---

Crikey! it works on Macs :O

I won’t be ready to concur until I see some results safely reported or, better yet, validated. ;)

I'm with you on that one, I've submitted requested cobblestones but until I get granted cobblestones, who knows if this is all for naught or not.

---

...
I reverted app_info.xml to its proper name and relaunched BOINC. It immediately deleted the stock app &c. from the project folder. It’s now happily crunching with the optimized app—but instead of displaying it by the name in app_info (viz v5.17, for compatibility with Beta), it continues to identify the cruncher as v5.13!
...

Speculation on my part: since you mention Beta, do you have one of those multi-version app_info, with a version_number for stock and a version_number for Beta (and possibly some spares as well), all referring to the same application?

If so, the sequence could be: Download stock 5.13. Download WUs. Put entries in client_state along the lines of 'crunch this WU with app 5.13'. Rename app_info. Restart BOINC. Find a WU with the reference to 5.13. Find that 5.13 points to the optimised app. Check it's there - yes - crunch.

As you say, the proof will be in the validating.

I just checked the 'puter and the 2 WU's were done crunching but didn't report and didn't download any new ones.

Sooooo, I went through the same process again, renaming, then up updated - the 2 WU's uploaded and 2 more were downloaded.

The two new ones started crunching on chicken soup right away, didn't have to reboot the computer this time.

I got the following message on the 2 uploaded WU's, that they were refused cause they had already been reported.

5/19/2007 2:33:01 PM|SETI@home|Sending scheduler request: Requested by user
5/19/2007 2:33:01 PM|SETI@home|Requesting 1728 seconds of new work, and reporting 2 completed tasks
5/19/2007 2:33:07 PM|SETI@home|Scheduler RPC succeeded [server version 509]
5/19/2007 2:33:07 PM|SETI@home|Message from server: Completed result 27fe05aa.20439.6258.29822.3.207_1 refused: result already reported as success
5/19/2007 2:33:07 PM|SETI@home|Message from server: Completed result 27fe05aa.20439.6258.29822.3.217_0 refused: result already reported as success

(I cut alot of it out to just show the two messages, if you want to see it all, let me know)

Soooooo, I went to the SETI page to see what the results page said. It gave me 'requested credits' of 48.72 for both with 'granted credits' pending.

http://setiathome.berkeley.edu/result.php?resultid=535920863
http://setiathome.berkeley.edu/result.php?resultid=535920781

Hey, for the hell of it, I'll throw in another twist, lol.

WU xxxx863 in the steddr out it mentions chicken soup
WU xxxx781 in the steddr out it doesn't mention chicken soup

My migrane is getting bigger and I've still fallen and can't get up.

I think the steddr only reports the app that was in use when the WU first started crunching. If the WU is finished with an app different than the one that started it, only the starting app is reported when completed. So that's not such a big mystery. Hope this eases your migrane a bit.

---

"Time is simply the mechanism that keeps everything from happening all at once."

@Philadelphia,
A couple of points,
Richard's original instructions ended with setting 'No New Tasks' after downloading, then restoring the app_info.xml file.... did you skip this bit?

Second,, Only 2 work Units? What is your work cache size, that is 'Computer is connected to the Internet about every X days' in your general preferences ?

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

@Philadelphia,
A couple of points,
Richard's original instructions ended with setting 'No New Tasks' after downloading, then restoring the app_info.xml file.... did you skip this bit?

Second,, Only 2 work Units? What is your work cache size, that is 'Computer is connected to the Internet about every X days' in your general preferences ?

I did not do the "no new tasks", oops. I did restore the file name though.

My cashe is set on 10 days, so I was a bit surprised I only got 2 WU's. I have a duo core so I guess it gave me one per core?

[edit]What I didn't do this go around (on purpose) is I didn't rename the file back to the original name, I'm wondering if it will just go report and download automatically the same way were doing it manually, with the exception of the rename back to original name. What do you think? Safe to try?

---

What do you think? Safe to try?

IMO, Unpredictable,

At your option:
- first let cache / uploads clear / report etc (force if necesary)
I would set 4 to 5 day cache, then
- stop boinc (manager/servce)
- rename app_info.xml
- start boinc
- download ~50 to 100 workunits ( or whatever you get, have to wait for them to fill!!! )
- set no new tasks
- stop boinc
- restore appinfo.xml
- start boinc, leaving set to ' No New Tasks.

I don't know what your description would do

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

I think the steddr only reports the app that was in use when the WU first started crunching. If the WU is finished with an app different than the one that started it, only the starting app is reported when completed. So that's not such a big mystery. Hope this eases your migrane a bit.

But both were downloaded at the same time, both started on the stock app and both ran the stock app for about 30 or so minutes before I rebooted the computer, which is when both switched over to chicken soup on their own.

I don't think it's a big deal either, just thought it was interesting :)

(No migrane really, teasing, but I am going to have a few Bud's with the boys in a bit to watch NASCAR. If I have too many of those I really will fall down and can't get up, lol)

---

What do you think? Safe to try?

IMO, Unpredictable,

At your option:
- first let cache / uploads clear / report etc (force if necesary)
I would set 4 to 5 day cache, then
- stop boinc (manager/servce)
- rename app_info.xml
- start boinc
- download ~50 to 100 workunits ( or whatever you get, have to wait for them to fill!!! )
- set no new tasks
- stop boinc
- restore appinfo.xml
- start boinc, leaving set to ' No New Tasks.

I don't know what your description would do

OK, I'll give it a go, what the hell, lol.

I don't know what you mean about what it will do to my description?

---

@Philadelphia,
A couple of points,
Richard's original instructions ended with setting 'No New Tasks' after downloading, then restoring the app_info.xml file.... did you skip this bit?

Second,, Only 2 work Units? What is your work cache size, that is 'Computer is connected to the Internet about every X days' in your general preferences ?

I did not do the "no new tasks", oops. I did restore the file name though.

My cashe is set on 10 days, so I was a bit surprised I only got 2 WU's. I have a duo core so I guess it gave me one per core?

[edit]What I didn't do this go around (on purpose) is I didn't rename the file back to the original name, I'm wondering if it will just go report and download automatically the same way were doing it manually, with the exception of the rename back to original name. What do you think? Safe to try?

I have a couple of my rigs running that way right now. Renamed the app info file so it was inactivated, restarted Boinc, up/downloads now work, and they are still crunching with the optimized app. What seems to be the trick here is that this will continue to work unless the rig totally runs out of Seti WUs, at which point I think they would go back to the stock crunching app.
But as long as there are WUs in process using Chicken, it seems that the new ones downloaded will also continue to crunch with Chicken.

And the kitties say.....'Sure are a lot of spoons stirring that Chicken soup right now!'

---

"Time is simply the mechanism that keeps everything from happening all at once."

This Description :

, I'm wondering if it will just go report and download automatically the same way were doing it manually, with the exception of the rename back to original name. What do you think? Safe to try?

[EDIT: Thanks Msattler, I don't know what that would do..]

we THINK the stock app might DO the chicken if the cache gets empty tho' ....If that has happened with no app_info in place.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

@Philadelphia,
A couple of points,
Richard's original instructions ended with setting 'No New Tasks' after downloading, then restoring the app_info.xml file.... did you skip this bit?

Second,, Only 2 work Units? What is your work cache size, that is 'Computer is connected to the Internet about every X days' in your general preferences ?

I did not do the "no new tasks", oops. I did restore the file name though.

My cashe is set on 10 days, so I was a bit surprised I only got 2 WU's. I have a duo core so I guess it gave me one per core?

[edit]What I didn't do this go around (on purpose) is I didn't rename the file back to the original name, I'm wondering if it will just go report and download automatically the same way were doing it manually, with the exception of the rename back to original name. What do you think? Safe to try?

I have a couple of my rigs running that way right now. Renamed the app info file so it was inactivated, restarted Boinc, up/downloads now work, and they are still crunching with the optimized app. What seems to be the trick here is that this will continue to work unless the rig totally runs out of Seti WUs, at which point I think they would go back to the stock crunching app.
But as long as there are WUs in process using Chicken, it seems that the new ones downloaded will also continue to crunch with Chicken.

And the kitties say.....'Sure are a lot of spoons stirring that Chicken soup right now!'

Great, that's what I was originally going to try - did it upload/download on it's own? I think I agree with you too on what will happen with/without WU's. Going back to that plan again, lol. It's T minus 20 minutes to end of current crunch.

---

@Philadelphia,
A couple of points,
Richard's original instructions ended with setting 'No New Tasks' after downloading, then restoring the app_info.xml file.... did you skip this bit?

Second,, Only 2 work Units? What is your work cache size, that is 'Computer is connected to the Internet about every X days' in your general preferences ?

I did not do the "no new tasks", oops. I did restore the file name though.

My cashe is set on 10 days, so I was a bit surprised I only got 2 WU's. I have a duo core so I guess it gave me one per core?

[edit]What I didn't do this go around (on purpose) is I didn't rename the file back to the original name, I'm wondering if it will just go report and download automatically the same way were doing it manually, with the exception of the rename back to original name. What do you think? Safe to try?

I have a couple of my rigs running that way right now. Renamed the app info file so it was inactivated, restarted Boinc, up/downloads now work, and they are still crunching with the optimized app. What seems to be the trick here is that this will continue to work unless the rig totally runs out of Seti WUs, at which point I think they would go back to the stock crunching app.
But as long as there are WUs in process using Chicken, it seems that the new ones downloaded will also continue to crunch with Chicken.

And the kitties say.....'Sure are a lot of spoons stirring that Chicken soup right now!'

Great, that's what I was originally going to try - did it upload/download on it's own? I think I agree with you too on what will happen with/without WU's. Going back to that plan again, lol.

Yes, it seems to be working OK on it's own. One of the rigs was in EDF mode, so it was only reporting results as they completed, but when it got down to 2 WUs left, Boinc decided it was time to get some more work, and after a couple of tries it downloaded 1 WU. Then it tried again and got about 17 more. They were all shortys, so it is crunching them now in EDF mode again, and not asking for more work to fill the cache. So all appears to be working, but until it happens to download WUs that do not toss it into EDF processing, it's not gonna build the cache up.

---

"Time is simply the mechanism that keeps everything from happening all at once."

@Philadelphia,
A couple of points,
Richard's original instructions ended with setting 'No New Tasks' after downloading, then restoring the app_info.xml file.... did you skip this bit?

Second,, Only 2 work Units? What is your work cache size, that is 'Computer is connected to the Internet about every X days' in your general preferences ?

I did not do the "no new tasks", oops. I did restore the file name though.

My cashe is set on 10 days, so I was a bit surprised I only got 2 WU's. I have a duo core so I guess it gave me one per core?

[edit]What I didn't do this go around (on purpose) is I didn't rename the file back to the original name, I'm wondering if it will just go report and download automatically the same way were doing it manually, with the exception of the rename back to original name. What do you think? Safe to try?

I have a couple of my rigs running that way right now. Renamed the app info file so it was inactivated, restarted Boinc, up/downloads now work, and they are still crunching with the optimized app. What seems to be the trick here is that this will continue to work unless the rig totally runs out of Seti WUs, at which point I think they would go back to the stock crunching app.
But as long as there are WUs in process using Chicken, it seems that the new ones downloaded will also continue to crunch with Chicken.

And the kitties say.....'Sure are a lot of spoons stirring that Chicken soup right now!'

Great, that's what I was originally going to try - did it upload/download on it's own? I think I agree with you too on what will happen with/without WU's. Going back to that plan again, lol.

Yes, it seems to be working OK on it's own. One of the rigs was in EDF mode, so it was only reporting results as they completed, but when it got down to 2 WUs left, Boinc decided it was time to get some more work, and after a couple of tries it downloaded 1 WU. Then it tried again and got about 17 more. They were all shortys, so it is crunching them now in EDF mode again, and not asking for more work to fill the cache. So all appears to be working, but until it happens to download WUs that do not toss it into EDF processing, it's not gonna build the cache up.

I'm not familar with EDF mode, can you help me out on that one.

---

@Philadelphia,
A couple of points,
Richard's original instructions ended with setting 'No New Tasks' after downloading, then restoring the app_info.xml file.... did you skip this bit?

Second,, Only 2 work Units? What is your work cache size, that is 'Computer is connected to the Internet about every X days' in your general preferences ?

I did not do the "no new tasks", oops. I did restore the file name though.

My cashe is set on 10 days, so I was a bit surprised I only got 2 WU's. I have a duo core so I guess it gave me one per core?

[edit]What I didn't do this go around (on purpose) is I didn't rename the file back to the original name, I'm wondering if it will just go report and download automatically the same way were doing it manually, with the exception of the rename back to original name. What do you think? Safe to try?

I have a couple of my rigs running that way right now. Renamed the app info file so it was inactivated, restarted Boinc, up/downloads now work, and they are still crunching with the optimized app. What seems to be the trick here is that this will continue to work unless the rig totally runs out of Seti WUs, at which point I think they would go back to the stock crunching app.
But as long as there are WUs in process using Chicken, it seems that the new ones downloaded will also continue to crunch with Chicken.

And the kitties say.....'Sure are a lot of spoons stirring that Chicken soup right now!'

Great, that's what I was originally going to try - did it upload/download on it's own? I think I agree with you too on what will happen with/without WU's. Going back to that plan again, lol.

Yes, it seems to be working OK on it's own. One of the rigs was in EDF mode, so it was only reporting results as they completed, but when it got down to 2 WUs left, Boinc decided it was time to get some more work, and after a couple of tries it downloaded 1 WU. Then it tried again and got about 17 more. They were all shortys, so it is crunching them now in EDF mode again, and not asking for more work to fill the cache. So all appears to be working, but until it happens to download WUs that do not toss it into EDF processing, it's not gonna build the cache up.

I'm not familar with EDF mode, can you help me out on that one.

EDF is 'earliest date first', when Boinc thinks that a WU is due sooner than it will process in normal 'round robin' processing, so it suspends work on the WU is is crunching at the moment (shows 'waiting to run'), and starts crunching the new WU first. At the moment, it also appears to suspend requesting new work as well, even if it should be filling the cache. I am not sure if it always did that and I just never noticed it when the cache was fairly full.

---

"Time is simply the mechanism that keeps everything from happening all at once."

@Philadelphia,
A couple of points,
Richard's original instructions ended with setting 'No New Tasks' after downloading, then restoring the app_info.xml file.... did you skip this bit?

Second,, Only 2 work Units? What is your work cache size, that is 'Computer is connected to the Internet about every X days' in your general preferences ?

I did not do the "no new tasks", oops. I did restore the file name though.

My cashe is set on 10 days, so I was a bit surprised I only got 2 WU's. I have a duo core so I guess it gave me one per core?

[edit]What I didn't do this go around (on purpose) is I didn't rename the file back to the original name, I'm wondering if it will just go report and download automatically the same way were doing it manually, with the exception of the rename back to original name. What do you think? Safe to try?

I have a couple of my rigs running that way right now. Renamed the app info file so it was inactivated, restarted Boinc, up/downloads now work, and they are still crunching with the optimized app. What seems to be the trick here is that this will continue to work unless the rig totally runs out of Seti WUs, at which point I think they would go back to the stock crunching app.
But as long as there are WUs in process using Chicken, it seems that the new ones downloaded will also continue to crunch with Chicken.

And the kitties say.....'Sure are a lot of spoons stirring that Chicken soup right now!'

Great, that's what I was originally going to try - did it upload/download on it's own? I think I agree with you too on what will happen with/without WU's. Going back to that plan again, lol.

Yes, it seems to be working OK on it's own. One of the rigs was in EDF mode, so it was only reporting results as they completed, but when it got down to 2 WUs left, Boinc decided it was time to get some more work, and after a couple of tries it downloaded 1 WU. Then it tried again and got about 17 more. They were all shortys, so it is crunching them now in EDF mode again, and not asking for more work to fill the cache. So all appears to be working, but until it happens to download WUs that do not toss it into EDF processing, it's not gonna build the cache up.

I'm not familar with EDF mode, can you help me out on that one.

EDF is 'earliest date first', when Boinc thinks that a WU is due sooner than it will process in normal 'round robin' processing, so it suspends work on the WU is is crunching at the moment (shows 'waiting to run'), and starts crunching the new WU first. At the moment, it also appears to suspend requesting new work as well, even if it should be filling the cache. I am not sure if it always did that and I just never noticed it when the cache was fairly full.

OK, thanks, that's what mine do too, when a more current expire date is downloaded it switch's to that one. I've only been cruching since Feb 07 but it seems to me it's always done it that way on my computer. I assumed it to be normal since it didn't want the more recent expirations not getting crunched.

---

WooooHoooo, I just went back to see how much time was left on my 2 current crunch's and low and behold, another one was downloaded so the process is working on my computer.

Lordy lordy, I'm going to go see the boys and have some Buds and watch some NASCAR. (practicing my drawwwww and spitttting)

WooHoo, and just got a second one!!!

---