Yes, I have had several task failures today when I never had any. Validated three test tasks with the new 2.10 app and one normal task.

Looking at the supported applications page - http://www.gpugrid.net/apps.php

Supported "New version of ACEMD" applications:
Linux - GPU/driver capable of CUDA80 or better
Windows - GPU/driver capable of CUDA92 or better

Which version is recommended as the minimum now?

It also depends on what generation of card you have. My GTX 980 with the 430.26 drivers running under Ubuntu 18.04 is getting the CUDA 100 work units. It ran a total time of 43 minutes for a a81-TONI_TESTTESTLONG210. But it uses a whole CPU core, so I just reserve one for it.

I will await the real work units before doing more.

Now we need 10,000 WUs loaded.
____________

Now we need 10,000 WUs loaded.

Over the past several days I have received 4 ACEMD 210 WU's on two Linux machines with 3 GTX-1060's and all validated fine (3 x 7,500 and 1 x 75,000 points). Linux machines awaiting production WU's anytime.

Could you please answer these 2 questions...
... and consider including their answers in the FAQ thread here:
http://www.gpugrid.net/forum_thread.php?id=5002

2 questions:

1) Is the new app capable of resuming on a different GPU? I ask, because my main 2 crunching PCs are below, each having 3 different GPU types, and you said "no major known bugs", but I thought I saw some other report saying earlier how resuming on a different GPU type wasn't working yet.

2) Will this app work for my GTX 660 Ti that is in the same PC as newer generation GPUs? I believe mixing Maxwell and Pascal was a problem previously, which is why I'm asking about your new app.

Depending on your answers, both of these would be major problems for me, as I'm trying to keep these PCs stable while also working long-running RNA World tasks.

Please let me know,
Thanks,
Jacob Klein

PC 1: RTX 2080, GTX 980 Ti, GTX 980
PC 2: GTX 1050 Ti, GTX 970, GTX 660 Ti

As far as I know, you still can't resume a task on a different card type. I solved it by changing my preferences to switch among apps to 360 minutes vice the default 60 minutes and that solves the issue. The task starts and finishes on the same card. Haven't seen any task require that long to finish yet but probably will be adequate until we get the app declared to Main and start getting Long tasks again with the new apps.

If you have the same card type in a multiple card host, there is no issue starting on one card and finishing on another.

Are there any plans to allow the app to resume on a different GPU?

Thank you. That is suitable, and I plan on implementing that approach shortly for one of my systems that gets suspended/resumed a lot. Did you know I'm responsible for exclude_gpu existing? ;)

Thanks :)

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

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 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.

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

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.

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.

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.