Just had three ap4.33 downloaded whats new please
____________
A computer program will always do what you tell it to do, but rarely what you want it to do.
Just had three ap4.33 downloaded whats new please
First, the graphics should display cpu time.
Second, more code to test for the 0'd statefile error. If the app reads in the statefile and finds that it's all 0's, it should try again up to 100 times over the next 10 minutes before it finally gives up. It will print messages to stderr.txt like
In ap_fileio.cpp, Statefile::write, statefile is 0'd, trying again: iteration [number]
J
with the release of 4.33 there seems to be a lot of validate errors popping up
____________
Just got one result (3932932) myself... going to see how it compares to a 4.30 result (3925285).
Nice to see the 30 day deadlines, too...
As for Validation, I had a 4.32 returned yesterday, [edit]that was[/edit] saying "Valid State: Invalid". [edit](As of 30 minutes ago; it's been taken care of now)[/edit]
I didn't know if that was usual or not (as in 'Can occur more than XX% of the time') since I haven't actually completed many AP WU's so far, and this is SETI Beta/AP 'alpha'.
(^^;)
____________
PappaVolunteer moderator
Volunteer tester
Send message
Joined: 13 Nov 05
Posts: 1724
Credit: 3,121,901
RAC: 0
AP 4.33
Graphics show Telescope time counting and CPU is updating. Other data for the account is correct.
____________
Thanks to Paul and Friends
Please consider a Donation to the Seti Project
AP 4.33
Graphics show Telescope time counting and CPU is updating. Other data for the account is correct.
Same here on my Vista Host, mouse movements for view angle and zoom in/out also are OK.
Looks perfect to me... ;-)
Let's see how the code to test for the 0'd statefile error works out.
____________
Still no graphics on openSusE 10.3 64bit. Getting this message in stderr.txt of v4.33 x86_64 :
____________
_\|/_
Urs
Return of my first four AP 4.33 first 3932910 Validate state invalid.
Other three valid
DCF now down to .548254. Completion times of next units down to 68:48:16
(3932910)
(3932904)
(3932897)
(3932890)
Finished first v4.33 unit id 3932050 in 38:45:18 according to manager.
Reported time on task details page is CPU time 136955.2sec, that calculates to 38:02:35. Any explanation, anyone?
I also did DCF experiment, as Josh had said he thought in should reduce to 0.4, I set mine to that value, before unit started.
The DCF after unit completed is now 0.399268.
seems like Josh can get his sums right ;-)
Graphics look very similar to those in Pappa's thread, AP 4.33 pictures
Andy
Working graphics on Linux here (Slackware 12.1) by telnetting into localhost.
Working graphics on Linux here (Slackware 12.1) by telnetting into localhost.
Is that a 32bit or a 64it linux version ?
If 64bit, which application did you run 32bit or 64bit ?
____________
_\|/_
Urs
Hello,
after more than 1 year not crunching for SETI beta I wanted to give Astropulse a try and downloaded my first AP workunit. But as you can see, my wingmen already got their credits (but I guess the credits were granted manually). Their tasks were crunched with AP 4.30, my task will be crunched with AP 4.33.
So my question is: Is my task still needed and should I crunch the workunit or is it useless and it's better to abort the task?
Regards,
Carsten
Same chapter - just another verse ...
Have picked up a new packet and have started working it with ver 4.33.
AGAIN, the TTC counter is wildly out of sync --> 7517+ hours . Total baloney, because the hand calculation shows completion in a bit over 116 hours. Of course, with this bogus info, my machine has been knocked into high priority 24/7 mode. Totally puzzling, because I reset my DCF files to "0.96xxxx" prior to calling for the new packet. BOINC was turned off when I made the changes, and no processes were active.
Comments and suggestions as to a method of correction would be most appreciated ...
____________
If I've lived this long, I've gotta be that old
...So my question is: Is my task still needed and should I crunch the workunit or is it useless and it's better to abort the task?
Please crunch the work_unit until it finishes or errors out. Do not abort, because that would be contraproductive for a beta project.
____________
_\|/_
Urs
... Of course, with this bogus info, my machine has been knocked into high priority 24/7 mode. Totally puzzling, because I reset my DCF files to "0.96xxxx" prior to calling for the new packet...
You could try again to modify the DCF in both client_state.xml and client_state_prev.xml, this time use the value Josh did calculate: "0.4xxxxx".
Comments and suggestions as to a method of correction would be most appreciated ...
I'm curious how that works out.
____________
_\|/_
Urs
PappaVolunteer moderator
Volunteer tester
Send message
Joined: 13 Nov 05
Posts: 1724
Credit: 3,121,901
RAC: 0
Carsten et al
Every completed Result adds data! One of the issues is that due to time to run and deadlines we have lost a few Testers and every completed Result become more important.
Hello,
after more than 1 year not crunching for SETI beta I wanted to give Astropulse a try and downloaded my first AP workunit. But as you can see, my wingmen already got their credits (but I guess the credits were granted manually). Their tasks were crunched with AP 4.30, my task will be crunched with AP 4.33.
So my question is: Is my task still needed and should I crunch the workunit or is it useless and it's better to abort the task?
Regards,
Carsten
____________
Thanks to Paul and Friends
Please consider a Donation to the Seti Project
Working graphics on Linux here (Slackware 12.1) by telnetting into localhost.
Is that a 32bit or a 64it linux version ?
If 64bit, which application did you run 32bit or 64bit ?
Sorry forgot to mention that - 32bit, Slackware is still 32 bit only.
Hello Urs and Pappa,
thank you for your answers.
Please crunch the work_unit until it finishes or errors out.
Every completed Result adds data!
That's what I wanted to hear ... ;-) (that my result won't be useless)
Regards,
Carsten
____________
Just reporting another finished AP 4.33.
(3932893) validate state invalid.
PappaVolunteer moderator
Volunteer tester
Send message
Joined: 13 Nov 05
Posts: 1724
Credit: 3,121,901
RAC: 0
Just completed and reported this one this morning
1145185
Two 4.30's and my 4.33.
Generally I think that it has peeled about 3000 seconds off my computer time compared to 4.32. I am down to about 80 hours/AP
____________
Thanks to Paul and Friends
Please consider a Donation to the Seti Project