You need a file called init_data.xml in the same directory.
Also, you can run the client with -standalone as an option.

Right-click the link below, and choose "save".

http://www.zadra.org/seti_enhanced/downloads/init_data.xml

HTH,
Simon.

Can't set up shared mem: -1

ar=0.775000 NumCfft=58347 NumGauss=           304962714 NumPulse=         58444196736 NumTriplet=       4979562790912

SETI@home error -108 Unknown error
from boinc_init_diagnostics()
File: ../main.cpp
Line: 227

now an update

the last 15 setiathome_enhanced-5.19 wu's with optimiced app 5.12sse3

crunchtime 1600sec - 2550sec ar = 1.65xx

host = Pentium-D-820 @ 3600MHz

tomorrow i will try the optimiced 5.12sse2 with the 5.19 wu's to see if it is also slower than sse3

If you are using Crunch3r's optimized app's (version 5.12) then you should be reporting them as version 5.12 and NOT 5.19. Reporting them as being crunched by an incorrect version messes up the master data base.

Thanks Eric, I like the new method, but I have 2 other questions:

-How the total number of floating point operations it's calculated? That calculation can slow down the client?

The calculation isn't done too often so it shouldn't be significant compared to other floating point calculation. The typical increments are large. (For example when FLOPs for an FFT are added, 5*N*log2(N) is added (where N is usually 128K). This an approximation for FLOPs used in calculating an FFT.

-What can happen with optimized client? If they are not only recompiled but they have code optimization (like crunch3r's client), the claimed credits can change?

That's really up to the optimizer. If they reduce the number of FLOPs they can also reduce the number added to the FLOP counter if they desire. I would guess that most will leave the counter as is.

Eric

How is the equation used to calcolate the claimed credit with the new client? It's based only on the number of FFTs performed?

The application keeps a running total of the number of floating point operations performed. The application reports credit for 3.35 times this number of floating point operations. (3.35 was chosen to make the median credits/hour to equal what the non-enhanced application was reporting).

Eric

How is the equation used to calcolate the claimed credit with the new client? It's based only on the number of FFTs performed?

I don't know the formula or ratio—they've done a fair bit of tinkering with it to make it come out with similar earning rates, on average, to other projects—but yes.

See this message from Eric Korpela, posted a few months back in the Test Project forum, showing the kind of analysis that's been done to develop the formula.

If the credits for the same WU are equal for all hosts, why in this case the pending credits fot one host are less?
wuid=76676710

That host is using an old BOINC client, v4.45. Clients earlier than v5.2.6 (? or so) can only claim credit according to time-&-benchmarks, ignoring an app's reported Flop count; there's been talk of cutting them off at some point in the future, when Enhanced has become 'the only game in town'.

... The CPU time varies by more than 50% in completion of the units, but the claimed credit is exactly the same at 19.05. How can this be right if the metrics come from the work?

...hostid=1958599

All those results are showing the exact same number of FFTs performed, so identical credit claims, regardless of the time taken, are to be expected. Note that in each case the other hosts in the quorum also report the same amount of crunching. Why your CPU-times (or the measurements thereof) are so discrepant I have no idea, but the amount of work done on each WU was indeed the same.

ping setiboincdata.ssl.berkeley.edu

Esecuzione di Ping setiboincdata.ssl.berkeley.edu [66.28.250.125] con 32 byte di
 dati:

Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.

Statistiche Ping per 66.28.250.125:
    Pacchetti: Trasmessi = 4, Ricevuti = 0, Persi = 4 (100% lost)

Once Classic has closed down, there will be a last update. Currently your account page shows "completed X Seti Classic work units as of March 15 2005." That'll be updated to something like "completed Y Seti Classic work units as of December 15 2005."

Since Seti/BOINC calculates credit differently than Classic did, there's no direct workunit-to-credits conversion, but your work units for Classic will be recorded.

If you can get there through a proxy, then Berkeley isn't blocking his IP address.

If you can get there through a proxy, then Berkeley isn't blocking his IP address. In order to help you, we need more data. You mention that you can't ping, have you tried a tracert to see where you fail? As others have mentioned, search the message boards for the proxy threads and/or search the WIKI for steps to isolate your problems.

UP :/

Hi!

Have you tried using a proxy?

If you dig through the old posts you should find some addresses.
They were posted during the cogent debacle.


Regards Hans

But now the problem is, like Steve have writed, it's that one member can't run BOINC because its IP is blocked! I hope that Matt read here and unblock that IP.

Bye,
GHz

Are you sure that Berkeley is blocking the IP?

Have you tried going through a proxy?

What other diagnostics have you tried?

Is there a really good reason that this machine can't be moved to a new IP?

There are two "players" here.

The thread was originally about 24.75.104.100.

GHz and Co. is interested in 217.133.4.201.

Matt answered the original question, because 24.75.104.100 was blocked for good reason -- it was hammering the SETI servers.

Blocking an IP is going to be a pretty dramatic step, they're only going to do it under extreme circumstances.

Chances are good that the other problem is elsewhere.

adding junk to this thread doesn't help either, just to get it to the "top" of the list, which is dependant on the forum prefs of each user anyway

also pending credit shouldn't be polled that often, it's not going to change that quickly, other puters have got to process and return the work, then the validator had gotta do it's stuff, THEN you might get credit

not much is gonna change in 96 minutes ((24hrs*(60mins/hour)=)1440 minutes per day/(10+20/2=) average of 15 times the site is polled each day)

the reason pending credit was disabled on the site was because it put too much load on the database, and by requesting a php generated page (which relies on the DB) you're just adding to that excessive load again