A few people have been getting workunits error out with an error like:

Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4' 
Error reading astronomy parameters from file 'astronomy_parameters.txt'
Trying old parameters file
Error reading into stream_max
Error reading into optimize_parameter
Error reading stream_weight for stream 2

ps_separation_17_test uses a new parameter file which we hope will fix these problems. let us know if you're having any problem with it here.

---

Just got one. Doesn't fail after 2 seconds like the ps_separation_17_3s_fix tasks with the error you showed but runs for 100 seconds then errors at the end.

Integration range: { nu_steps = 640, mu_steps = 1400, r_steps = 1400 }
Using 3 chunk(s) with sizes: 464 464 464
Chunk mu steps does not match: 1392 != 1400
Integral 2 time = 0.747096 s
Failed to calculate integral 2

http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=41501426

MY Error Message is a little different here the hole Text:

Aufgabe 60843371
Name ps_separation_17_3s_fix_5_1652_3
Arbeitspaket 41499545
Erstellt 28 Jun 2011 | 5:59:23 UTC
Gesendet 28 Jun 2011 | 5:59:24 UTC
Empfangen 28 Jun 2011 | 6:20:23 UTC
Serverstatus Abgeschloßen
Resultat Berechnungsfehler
Clientstatus Berechnungsfehler
Endstatus 1 (0x1)
Computer ID 296072
Ablaufdatum 10 Jul 2011 | 5:59:24 UTC
Laufzeit 1.39
CPU Zeit 0.05
Prüfungsstatus Ungültig
Punkte 0.00
Anwendungsversion MilkyWay@Home v0.88

Stderr output
<core_client_version>6.12.26</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Error reading astronomy parameters from file 'astronomy_parameters.txt'
Trying old parameters file
Error reading into stream_max
Error reading into optimize_parameter
Error reading stream_weight for stream 2
07:59:43 (2784): called boinc_finish

</stderr_txt>
]]>


--------------------------------------------------------------------------------

Prozessor:

GenuineIntel
Intel(R) Xeon(R) CPU L5320 @ 1.86GHz [Family 6 Model 15 Stepping 11]


HTH

Franz

Yes yours was a ps_separation_17_3s_fix task which gives the same error message as in the original post and posts in other threads.

Mine was a ps_separation_17_test which are the more recent tasks with a new parameter file which Travis was enquiring about in this thread.

I didn't realise they were two different types of tasks myself at first, I just looked at the "17", but the earlier type is "17_3_fix" and the more recent type is "17_test"

Same error as kashi:
http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=60847586

---

A lot of error's closing Milkyway & returning to Folding@home.
Do you make a testrun before releasing a change like this or is the first test
done by us?

<core_client_version>6.10.60</core_client_version>
<![CDATA[
<message>
Felaktig funktion. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Error reading astronomy parameters from file 'astronomy_parameters.txt'
Trying old parameters file
Error reading into stream_max
Error reading into optimize_parameter
Error reading stream_weight for stream 2
07:20:41 (4168): called boinc_finish

</stderr_txt>
]]>

Got 20 errored files with 17-3s-fix across all machines

<core_client_version>6.12.26</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Error reading astronomy parameters from file 'astronomy_parameters.txt'
Trying old parameters file
Error reading into stream_max
Error reading into optimize_parameter
Error reading stream_weight for stream 2
01:57:53 (2632): called boinc_finish

Hi everybody!

I\'m 22 y.o., and I\'m a Civil Engineer.

I live with my family and work in Ouro Preto, Brazil. And I speak Portuguese.

My Desktop is a Intel Core I7 2600k (with 8 Cpus), and i available for everthing you need.

A lot of error's closing Milkyway & returning to Folding@home.
Do you make a testrun before releasing a change like this or is the first test
done by us?

I guess the project do not have the money to build up a test environment. For me I have no problem to be a tester, but I want to know that I am a tester. So I can watch and I can decide with what Machines I want test.
In other projects(S@H, Collatz) I can select the application that I want to run. Together with the different profiles (School, Home, Work) I could setup a Test Profile and could direct with witch machine I want to do the test- Apps.

So please Admins speak with the guys from the other project how this is done, if you need help. I think it’s a pleasure for them to give you support.
Many people will be glade here that they can crunch without to be an unintentionally tester.
A lot of people crunches only for credit, and it is there right, because they pay the money for the electric bill.
I have no problem to be a tester but I want to know it, so I can help even better.

Greetings

Franz

I guess the project do not have the money to build up a test environment. For me I have no problem to be a tester, but I want to know that I am a tester. So I can watch and I can decide with what Machines I want test.

I don't have a problem to be a tester as well and I even think it's OK to test on everyone as long as they know that such tests are done occasionally, but IMHO it's not the best way to test things by replacing all WUs with new untested ones and left it like that for a day, I'd suggest something like no more than 1000 tasks to test the new WUs (while the old ones are still available) and if the new ones are OK, than disable creation of the old ones. Or was the old type of search "ready", i.e. no more of those WUs could be done? In that case the beta test of the new ones is a bit late.

---

Errors here too, now saying no work. This project has been fubar for quite some time now. Why do you not have a specific set of beta testers before releasing these fucked up wus into the wild. It seems like this project has been trying to fix things for a few months

The server's hard drives were down for quite a bit last night, tried staying up as late as I could but couldn't get everything back up and running while the drives were down. So I just woke up and got things fixed. Everything should be running again.

I also started ps_separation_17_test2, which should fix the problesm of ps_separation_17_test

--Travis

---

Getting the older ps_test_4's coming through and falling over just past 90% - can they be server aborted?

EDIT: Murphy is out and about - just had a test_4 go through :) Had around a dozen fall over.

Regards
Zy

Getting the older ps_test_4's coming through and falling over just past 90% - can they be server aborted?

EDIT: Murphy is out and about - just had a test_4 go through :) Had around a dozen fall over.

Regards
Zy

No more ps_test_4's are being generated. I don't want to server abort them because some people might not get credit for ones that did work.

---

Okie Doke :)

Just had 2 x 17s go through, fell over at the end - computation error. Was on my 2x5970 box

(loads of separation 10 3s are going through ok. one or two fall over, very small percentage tho)

Regards
Zy

Okie Doke :)

Just had 2 x 17s go through, fell over at the end - computation error. Was on my 2x5970 box

(loads of separation 10 3s are going through ok. one or two fall over, very small percentage tho)

Regards
Zy

Do you know if they were separation_17_test or separation_17_test2?

The latter should be working, but I think there was a problem with the former.

---

Aparently not http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=60876213

I'm getting successive computation errors with each ps_nbody batch...

I'm getting successive computation errors with each ps_nbody batch...

I think the ps_nbody_test3 fixes those problems.

---

Aparently not http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=60876213

That one looks like it worked.

*edit* weird, it printed out the correct stuff to standard error, but then it was a computation error. Matt A. is going to have to look into that.

---

I think you despratly need programers Gipsel HELP!