Thanks :)

Toni, a minor request for the enxt version: the previous one had some nice information in the Stderr output, i.e. GPU, driver, clocks and natoms. The latter was useful for determining small performance differences, as the "credits per time" always depended on the number of atoms in a simulation. So please include whatever you can port without too much trouble.

MrS

---

Scanning for our furry friends since Jan 2002

I would like to ask: As I understand a GTX 670 with the latest driver: 440.97 should work with the acemd3 app, as this driver and confirmed by BOINC has the latest CUDA tools 10.2. Is this correct?

I ask as the GTX670 fails all acemd2 v9.22 (cuda65) at the moment as reported by others. However what I do not understand is why the acemd2 app does not switch to acemd2 v9.22 (cuda80) with the new driver installed?

I would be very grateful, if somebody might answer these two questions. If the GTX 670 will not work anymore on these project I might as well pass it to another BOINC user.

Are ANY of the 9.22 or 9.23 apps working? I thought I saw mention that none of them work anymore because their license expired again.

latest driver: 440.97 should work with the acemd3 app

440.97 is working fine for me but I don't have a 670.

---

The 9.23 app works on this computer: http://www.gpugrid.net/show_host_detail.php?hostid=441816, but not on this: http://www.gpugrid.net/show_host_detail.php?hostid=486229
Both Windows though..

Any reason why you don't want to move on to the acemd3 app? Other than there is no work for it again.
From the prerequisites page https://www.gpugrid.net/join.php the 670 qualifies as a CC 3.0 capable card. The 441 drivers in their docs say the 670 is supported.
Other than the normal BOINC mechanism that tries out all possible applications compatible with your hardware and had decided the old CUDA65 still qualifies and has decided not to try out the CUDA80 app, I don't know what you can do other than wait it out. Or go with an anonymous platform and define the CUDA80 9.23 app as your gpu app of choice.

The 9.23 app works on this computer: http://www.gpugrid.net/show_host_detail.php?hostid=441816, but not on this: http://www.gpugrid.net/show_host_detail.php?hostid=486229
Both Windows though..

The second one is 9.22 (CUDA 6.5). It's license got expired.

The 9.23 app works on this computer: http://www.gpugrid.net/show_host_detail.php?hostid=441816, but not on this: http://www.gpugrid.net/show_host_detail.php?hostid=486229
Both Windows though..

The second one is 9.22 (CUDA 6.5). It's license got expired.

Thanks Zoltan. I thought I saw somewhere that some(one) of the apps had an expired license again.

The 9.23 app works on this computer: http://www.gpugrid.net/show_host_detail.php?hostid=441816, but not on this: http://www.gpugrid.net/show_host_detail.php?hostid=486229
Both Windows though..

The second one is 9.22 (CUDA 6.5). It's license got expired.

That is why I thought, installing the newest driver would automatically trigger that BOINC would download CUDA80 9.23 app until acemd3 is wildly available. Or just dismantle this particular computer as it is not a very efficient GPU anymore and pass it to a user which still uses GTX5XX for another BOINC project.

Well the project should send out the available 9.23 CUDA80 app for applicable hardware . . . if they have configured the scheduler correctly for deprecating the CUDA65 9.22 app. Obviously that hasn't happened.

It's gotten too confusing keeping track of what runs on what. I'm setting my hosts to normal preferences, which for me is long runs and ACEMD3. The server shouldn't be sending the wrong apps to the wrong hosts. Any failures I have will be dealt with via the normal BOINC mechanisms.

---

Team USA forum | Team USA page
Join us and #crunchforcures. We are now also folding:join team ID 236370!

It's gotten too confusing keeping track of what runs on what. I'm setting my hosts to normal preferences, which for me is long runs and ACEMD3. The server shouldn't be sending the wrong apps to the wrong hosts. Any failures I have will be dealt with via the normal BOINC mechanisms.

I think it's the sensible approach.

t

It's gotten too confusing keeping track of what runs on what. I'm setting my hosts to normal preferences, which for me is long runs and ACEMD3. The server shouldn't be sending the wrong apps to the wrong hosts. Any failures I have will be dealt with via the normal BOINC mechanisms.

I think it's the sensible approach.

t

Is this policy of app assignment sill in function?
This might be the reason for sending the 9.22 (CUDA6.5) app to hosts with CC3.0 cards.
It's time to deprecate these apps, if their license in fact got expired.
I've saved a WU, which has failed 7 times before my host picked it up:
9.22 (CUDA65) app: 4 times
Turing card: 2 times
exit code -55: 1 time
It's time to release the new app, and deprecate the not working ones, as this project spamming itself to the void.

Now that the queues run completely dry, it's time to deprecate the old app, release the new, and fill up the queue.
Please, clear all the old errors from the database.

Now that the queues run completely dry, it's time to deprecate the old app, release the new, and fill up the queue.

you are a real optimist, Zoltan :-)))

Now that the queues run completely dry, it's time to deprecate the old app, release the new, and fill up the queue.
Please, clear all the old errors from the database.

I'll second that. I don't have any Windows machines so all my Linux hosts have crunching E@H and WCG only since May.

They are dependent on only a few people for work. I am sure some of them have teaching obligations and other course work.

When they are between PhD dissertations or other publications, we are out of luck.