AP comand line
-unroll 16 -oclFFT_plan 256 16 256 -tune 1 64 4 1 -tune 2 64 4 1 -ffa_block 16384 -ffa_block_fetch 8192

AVX don`t need a comand line.

Thank you, Mike!
I forgot that AVX is a CPU application. But I think there is a file to add a command line?
Will add the AP command line.

Meow!

---

"Time is simply the mechanism that keeps everything from happening all at once."

If you put your command line tunings in an app_config file, you never have to edit app_info again. And the Lunatics installers NEVER touches your app_config file so it is only under your control. The only tunings for AP is with the gpu app. Basically the cpu apps don't need tuning if you choose the AVX app for both.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Thanks, Keith.
Should be good to go for now then.
Will look into that app_config thingy.

If anybody notices something that needs correction or improvement, please do let me know!

Meow!

---

"Time is simply the mechanism that keeps everything from happening all at once."

Read all about it here. Application_configuration

Mine for example looks like this:

<app_config>
  <app_version>
    <app_name>setiathome_v8</app_name>
    <plan_class>opencl_nvidia_SoG</plan_class>
    <avg_ncpus>1</avg_ncpus>
    <ngpus>0.5</ngpus>
    <cmdline>-sbs 1024 -period_iterations_num 1 -tt 1500 -high_perf -spike_fft_thresh 4096 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 64 -oclfft_tune_cw 64 -high_prec_timer</cmdline>
  </app_version>
  <app_version>
    <app_name>astropulse_v7</app_name>
    <plan_class>opencl_nvidia_100</plan_class>
    <avg_ncpus>1</avg_ncpus>
    <ngpus>1</ngpus>
    <cmdline>-unroll 24 -oclFFT_plan 256 16 256 -ffa_block 16384 -ffa_block_fetch 8192 -tune 1 64 8 1 -tune 2 64 8 1</cmdline>
  </app_version>
<project_max_concurrent>8</project_max_concurrent>
</app_config>

Just create it with Notepad as usual when editing the BOINC .xml files.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

And does that override the other command line files that I just edited?
Meow?

---

"Time is simply the mechanism that keeps everything from happening all at once."

I'm not sure. Maybe someone who knows for sure whether the app_config.xml takes precedence over any other command line file will comment. I just leave the command line files that the installer puts in blank at 0 bytes and do all my tuning in app_config. As I said, you just have to run the installer for your preferred app. I do the rest in app_config like how many task to run per card, how much cpu and gpu resources to commit per task and the tuning parameters for each app. That way you never have to hand edit app_info and risk dumping all your tasks. Which I have done countless times before until I learned about app_config and started using it.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Gotta remember.....rerunning the installer will wipe out my command lines, right?
Have to copy them somewhere to add them back.
And re-edit the app info for 2 at a time.

Depends how you have it set up.
For me, it has no effect on command line settings or on the number of WUs run as I use app_config.xml and the MB_commandline_xxx file for my settings which are untouched by the installer.
And have the advantage of it you make a typo, they just don't work instead of trashing your whole cache (as happens with a booboo in app_info.xml).

---

Grant
Darwin NT

I'm not sure. Maybe someone who knows for sure whether the app_config.xml takes precedence over any other command line file will comment

App_config.xml overrules app_info.xml

I like to keep things simple, so my app_config.xml

<app_config>
 <app>
  <name>setiathome_v8</name>
  <gpu_versions>
  <gpu_usage>1.00</gpu_usage>
  <cpu_usage>1.00</cpu_usage>
  </gpu_versions>
 </app>
 <app>
  <name>astropulse_v7</name>
  <gpu_versions>
  <gpu_usage>0.5</gpu_usage>
  <cpu_usage>1.0</cpu_usage>
  </gpu_versions>
 </app>
</app_config>

and I just put my command line values in
mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt

The advantage of this is that when the next WU starts, it gets the changed values from mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt straight away.

If you have them in app_config.txt you have to exit & restart BOINC, or at the very least "Options, Read config files" in the Manager for the new values to take.
With values hardwired in to app_info, exiting & restarting BOINC is the only way.

---

Grant
Darwin NT

Ok everyone, Mark uses BOINC 6.10.58 (1 version lower than me) which rules out using the app_config.xml full stop as that is not supported until version 7.4.26.

Cheers.

Ok everyone, Mark uses BOINC 6.10.58 (1 version lower than me) which rules out using the app_config.xml full stop as that is not supported until version 7.4.26.

Ah, so app_config.xml is out, but he can still use the MB command line file and not have to play with app_info.xml to improve things there.

---

Grant
Darwin NT

Ok everyone, Mark uses BOINC 6.10.58 (1 version lower than me) which rules out using the app_config.xml full stop as that is not supported until version 7.4.26.

Ah, so app_config.xml is out, but he can still use the MB command line file and not have to play with app_info.xml to improve things there.

Yes I just use the AP & MB GPU command line txt files for tuning and the app_info.xml for just the basics like task count and core support.

Cheers.

Thanks for the reminders......
I had totally forgotten that my older Boinc does not do app_config.
Ya saved me the trouble of looking for it.....LOL.
The command line files are what I have always used anyway, and they are doing the job correctly.
And so is the AVX app, which I also would not have thought of without your kind suggestions.

Thank you, and meow!

---

"Time is simply the mechanism that keeps everything from happening all at once."

FYI - MS just pushed new NVidia driver 388.13 for Win 10. Apparently this time it does include OpenCL, unlike any previous pushes of NV drivers.
HOWEVER, any SoG 8.20 tasks fail with "postponed 30 seconds" message in task log, and will never start.
Downloaded fresh 388.13 from NVidia site, had same result. so perhaps not just missing OpenCL.
Fell back to 382.33 and am back in business.

---

FYI - MS just pushed new NVidia driver 388.13 for Win 10. Apparently this time it does include OpenCL, unlike any previous pushes of NV drivers.
HOWEVER, any SoG 8.20 tasks fail with "postponed 30 seconds" message in task log, and will never start.
Downloaded fresh 388.13 from NVidia site, had same result. so perhaps not just missing OpenCL.
Fell back to 382.33 and am back in business.

Sounds like 388.13 should go on "Do not use for SETI@home" list.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I use 388.13 (64buit international) for Win 10 with no problem.

Did you DL the driver directly from NV site? Install with the clean instalation option?

---

FYI - MS just pushed new NVidia driver 388.13 for Win 10. Apparently this time it does include OpenCL, unlike any previous pushes of NV drivers.
HOWEVER, any SoG 8.20 tasks fail with "postponed 30 seconds" message in task log, and will never start.

Even after a reboot?

---

Grant
Darwin NT

I use 388.13 (64buit international) for Win 10 with no problem.

Did you DL the driver directly from NV site? Install with the clean instalation option?

Juan and Grant:

yes - always DL the driver directly from NV site
yes - always Install with the clean option?
yes - always Reboot after installs

After having donethis innumerable times on 6 crunchers .....

---

May i sugest do DL the international version, maybe something is diferent. Who knows?. At least is Working here normaly on my 3 hosts.

---

May i sugest do DL the international version, maybe something is diferent. Who knows?. At least is Working here normaly on my 3 hosts.

Thanks, it is indeed the International version I downloaded and installed.
But there is something else strange going on, at this point.
It looks as though it's now working properly on 1 of my Xeon boxes, but definitely doesn't work on the Core2Quad box. Still trying to determine why that is, and trying to make it fly on the second Xeon box as I try.

---

FYI - MS just pushed new NVidia driver 388.13 for Win 10. Apparently this time it does include OpenCL, unlike any previous pushes of NV drivers.
HOWEVER, any SoG 8.20 tasks fail with "postponed 30 seconds" message in task log, and will never start.
Downloaded fresh 388.13 from NVidia site, had same result. so perhaps not just missing OpenCL.
Fell back to 382.33 and am back in business.

I had to update from 384.94 in Windows 10 to 388.13 so the driver would recognize my new GTX 1070 Ti. Haven't had any issues with the 388.13 driver on that machine. My biggest concern today was that MS pushed the FCU at me. I had my doubts but the update went without any issues. And if MS put the Win10 version of 388.13 on my machine, I don't know how to tell if I still have my original manually installed 388.13 or a MS supplied version included in the update. My trepidation was relieved when I first ran my first instance of BOINC after the update was finished and BOINC found all my cards and OpenCL was initialized without any troubles. A big sigh of relief there. I know that I could have quickly stopped BOINC if it started to throw errors and reload the 388.13 drivers manually but fortunately I didn't have to.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)