Expect the usual new verion problems with too much or too little work fetch and bad time estimates.

Please report problems here.

---

Please report problems here.

Problem: Having too many cuda22 tasks that will take forever to crunch, before I can get to doin' any 6.99 tasks;)

Sorry, couldn't resist:)

Please report problems here.

Problem: Having too many cuda22 tasks that will take forever to crunch, before I can get to doin' any 6.99 tasks;)

Sorry, couldn't resist:)

That link you supplied is only viewable by you, everyone else gets:

unable to handle request

No access

If you Reset the project, those tasks will be resent as 6.99 tasks.

Claggy

Thanx Claggy!

The link was just my list of tasks in progress.
I did find it strange I could see my name at the top instead of just my computer number. Must have been a "total" tasks page for people with multiple hosts. I'm guessing this link will work (not that it matters really)
http://setiweb.ssl.berkeley.edu/beta/results.php?hostid=59090&offset=0&show_names=0&state=1&appid=

Two questions:
a) If I Reset and get them as 6.99, is that more valuable or less valuable to the project?
(considering I don't really care if cuda22 is slower, just want what's best for the science and/or testing)

b) Assuming the answer is that testing 6.98 is over and 6.99 the focus now, should I always reset when new applications come out?

Two questions:
a) If I Reset and get them as 6.99, is that more valuable or less valuable to the project?
(considering I don't really care if cuda22 is slower, just want what's best for the science and/or testing)

b) Assuming the answer is that testing 6.98 is over and 6.99 the focus now, should I always reset when new applications come out?

Probably more valuble, as we'll see if the different Bug fixes have worked, 1) The Cuda22 app will resume O.K after being suspended, 2) The synch issues with newer drivers and newer GPUs causing overflows has been fixed, so less inconclusives,

Depends what the changes are whether you always reset the project when new apps come out, i invariably update to the new apps when they come out as soon as possible,

Claggy

Thanx again for the info Claggy.

Reset Beta and have all tasks running 6.99 now. Also played around with suspending a cuda22 task and it works (for me).

My PC D/Led the 6.99_cuda23 app.

The mbcuda-6.99-cuda23.CFG file if empty, no entry (0 Byte).
Is this normal?

All stock, BOINC show "0.9x + 1 NV GPU" for the 6.99_cuda23 app.
Very high ..

A 0.421810 AR WU:
~ 820 sec wall clock time + ~ 85 sec CPU time usage.
That's ~ 1/10 CPU time.
So maybe "0.1 + 1 NV GPU" would be better for my PC (Intel Core2 Duo E7600 + GTX260)?


- Best regards! :-) - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC (@ SETI@home Main). - SETI@home needs your help. -

---

My PC D/Led the 6.99_cuda23 app.

The mbcuda-6.99-cuda23.CFG file if empty, no entry (0 Byte).
Is this normal?

Yes it is normal as BOINC was downloading a fresh file and deleting the old one whenever "we" edited the former file that had info already in it.

Sutaru Tsureku wrote:

My PC D/Led the 6.99_cuda23 app.

The mbcuda-6.99-cuda23.CFG file if empty, no entry (0 Byte).
Is this normal?

arkayn wrote:

Yes it is normal as BOINC was downloading a fresh file and deleting the old one whenever "we" edited the former file that had info already in it.

I know that this happen if we edit the .CFG files.
I was the first who noticed and posted it .. ;-)

This time it's different.
My stock BOINC/S@h-B D/Led the 6.99_cuda23 app automatically.
The (1st time) D/Led mbcuda-6.99-cuda23.CFG file if empty, no entry (0 Byte).

So the mbcuda-6.99-cuda23.CFG file on the S@h-B D/L server is empty.
That's wanted?


- Best regards! :-) - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC (@ SETI@home Main). - SETI@home needs your help. -

---

arkayn wrote:

Yes it is normal as BOINC was downloading a fresh file and deleting the old one whenever "we" edited the former file that had info already in it.

Sutaru Tsureku wrote:

I know that this happen if we edit the .CFG files.
I was the first who noticed and posted it .. ;-)

This time it's different.
My stock BOINC/S@h-B D/Led the 6.99_cuda23 app automatically.
The (1st time) D/Led mbcuda-6.99-cuda23.CFG file if empty, no entry (0 Byte).

So the mbcuda-6.99-cuda23.CFG file on the S@h-B D/L server is empty.
That's wanted?

Yes. If you'd followed the discussion following your original report, you'd know that we worked out that if a file downloaded with content was edited, BOINC's security mechanism restored it to the default state at the next restart. But zero-length files can be edited without the changes being lost on restart.

Since you've looked closely enough to find a zero-length file, you'll have seen that there is also a setiathome-6.99-cudaXX_README_x41zb file - if you read it, you'll find that there is a paragraph (3) describing the configuration tools, and that a sample config has been attached as appendix (a).

In the course of preparing the text files for distribution via the SETI server, Eric has, as usual, converted them to Linux format and removed the .txt extension - which makes matters a little complicated for users of what is exclusively (at this stage) a Windows application. When you click on the file, don't accept Windows' suggestion of using a web service to find an appropriate program: instead, select from a list, and choose 'WordPad' - that displays the Linux format legibly. (Volunteers who already have Notepad++ installed on their machines can use that instead)

It would help if somebody could copy-paste the sample configuration direct from WordPad to the .CFG file (opened with whichever tool you usually use), and verify that the application reads the resulting settings correctly despite the line-ending problem.

06/12/2012 04:17:27 SETI@home Beta Test Finished download of setiathome_6.98_windows_intelx86__cuda22.exe
06/12/2012 04:22:14 SETI@home Beta Test Started download of setiathome_6.98_windows_intelx86__cuda23.exe

Just posting this in case it's not normal...

06/12/2012 04:17:27 SETI@home Beta Test Finished download of setiathome_6.98_windows_intelx86__cuda22.exe
06/12/2012 04:22:14 SETI@home Beta Test Started download of setiathome_6.98_windows_intelx86__cuda23.exe

Just posting this in case it's not normal...

I'm getting the same:

06/12/2012 10:05:59 | SETI@home Beta Test | Started download of setiathome_6.98_windows_intelx86__cuda32.exe

So, it may be be normal for now, but it's not right - we seem to have lost the v6.99 which was installed a couple of days before the power outage.

The 6.99 versions are still present in the database. I'll check the logs to see why 6.98 would be distributed.

It's weird. The beta scheduler must have somehow started running before the logs were run forward. That could mean there are a lot of workunits or results that are no longer have the right name or point to the right data file.

Forcing the scheduler to reread the database has the 6.99 versions being distributed again.

---

A couple of WUs since we came back with v6.99, which are interesting from the credit granted point of view.

4291374
4290350

Both requested "out of bounds" credit (about 1500 credits in this case) and in that case they receive the recent average of granted credit. As host_app_version credit statistics build up these cases should become rare.

---

Some weird things happened when the project came back online earlier this week. On Dec 7 my computer reported all tasks that had been processed before. All these tasks had a deadline in January. I checked the result status and about half of them were 'completed and validated' but the other half show up as 'No reaction, time elapsed'.

Examples:

http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=11610523
http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=11610472
http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=11610431

How could these tasks have expired within ten days ? Was this somehow caused by database corruption after the outage ? I don't care too much about the credit, but I wonder if something is broken that should be fixed.

Tom

Didn't know where to post this and as usual, don't know if the info is of any value:

I saw Ivan post on main about ghosts so I came over here to check what was going on. And for a while I had 19 homeless cuda32 tasks that eventually made it... as cuda22 tasks.

I'm pretty sure I've seen this happen before too (say a few weeks ago maybe)

Any progress in getting the x41zc Cuda apps out the door?

https://setisvn.ssl.berkeley.edu/trac/changeset/1727#

https://setisvn.ssl.berkeley.edu/trac/changeset/1743#

and getting the CPU apps built with the 'blocksum precision maintenance fixes' that we're been waiting for over a year now?

https://setisvn.ssl.berkeley.edu/trac/changeset/1671#

Claggy

Status on OSX science apps? Both GPU and CPU science apps for OSX are lagging behind Windows and Linux. I'm am pulling more resources away from SETI as I'm feeling less and less appreciated by the devs/ project scientist. I am not renewing my donor star until I see some improvement.
Edit I know the staff works hard and all that. I just am finding support here for my chosen OS is degrading and as this is the only project I support with my money. I am finding it had to justify money when I am unemployed or working temp jobs. Increase the support of OSX and I will find the money somehow.

I have a number of tasks that have status 'validation inconclusive' that have not been sent to another computer for verification. Some of them were reported (by both wingmen) nearly a month ago.
Is something wrong with sending inconclusive results to other computers ?
Has anyone else noticed this ?

Some examples (there are more):

http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=4360765
http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=4362682
http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=4369607
http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=4394738

Tom