As the title says. Beta test only, try at your own risk.

I think we should dig out the old "Advanced Users only" tag for this one - I'm not sure whether it will fly or not.

This installer has been updated for NVidia only so far - DO NOT USE IT if you are currently running stock applications for ATI/AMD or intel GPUs.

This is basically the v0.44 installer (64-bit only, to start with), with the following changes.

MB v7 legacy support removed
Cuda23 app removed (to make space in the user interface, only)
r3430 SoG app for NVidia included

This is exactly the same application as has been available from Raistmer's mail.ru cloud storage for some time - indeed, that's where I got it from. I haven't pre-loaded it with any command lines or other configurations - part of the purpose of this beta is to ask for suggestions for a "standard basic" tuning to go into a full installer release at some point in the future.

I have set up the app_info segment for NVidia cards to handle the following version/plan_class combinations:

8.12 (opencl_nvidia_sah)
8.12 (opencl_nvidia_SoG)
8.00 (opencl_nvidia_sah)
8.00 (opencl_nvidia_SoG)
8.00 (cuda50)
8.00 (cuda42)
8.00 (cuda32)
8.00 (cuda23)

If you have been running any of:
Stock download
Lunatics v0.44
Raistmer's cloud download

this installer is designed to preserve your downloaded tasks and pick up where your previous application left off. That includes when switching between CUDA and SoG, in either direction. But it's possible I may have missed a special case - if your NV MB cache disappears, my apologies, but please tell me about it - with as much detail as you can about what application(s) and settings you were running before.

Any pre-existing application tuning should be preserved if you placed it in the 'mb_cmdline_win_x86_SSE3_OpenCL_NV.txt' file, but if won't be if you placed it directly into app_info.xml - whichever, you'd be wise to make backups.

If you have any observations about the installer, feel free to make them in this thread. If you have any observations about the SoG application, please use the thread which Raistmer is monitoring.

And with no further ado, download from here.

Are the Astropulse device-specific configuration files included in v0.45? Somehow they were missed in v0.44.

Thanks for the installer Richard.

Seems to be running fine.

To be honest, I edit the app_info after it installed to remove all cudas and AP 7.05 (leaving 7.10)

Let you know if any issues pop up

Are the Astropulse device-specific configuration files included in v0.45? Somehow they were missed in v0.44.

I haven't touched anything this time, and I wasn't aware that anything was missing from v0.44. So take that as a 'no'.

If you can give me more detail, I'll take a look in the morning - I've kept the sources for v0.43 as well, so I can compare back with those.

Are the Astropulse device-specific configuration files included in v0.45? Somehow they were missed in v0.44.

I haven't touched anything this time, and I wasn't aware that anything was missing from v0.44. So take that as a 'no'.

If you can give me more detail, I'll take a look in the morning - I've kept the sources for v0.43 as well, so I can compare back with those.

I had inquired about it in a message in the Lunatics Windows Installer v0.44 - new release for v8 (required upgrade), but didn't get a response so I hadn't pursued it further. I don't believe they were in the v0.43b installer either, although Raistmer first added those files to AP in the fall of 2014.

Are the Astropulse device-specific configuration files included in v0.45? Somehow they were missed in v0.44.

Those files aren`t part of the package.

---

With each crime and every kindness we birth our future.

Are the Astropulse device-specific configuration files included in v0.45? Somehow they were missed in v0.44.

I haven't touched anything this time, and I wasn't aware that anything was missing from v0.44. So take that as a 'no'.

If you can give me more detail, I'll take a look in the morning - I've kept the sources for v0.43 as well, so I can compare back with those.

I had inquired about it in a message in the Lunatics Windows Installer v0.44 - new release for v8 (required upgrade), but didn't get a response so I hadn't pursued it further. I don't believe they were in the v0.43b installer either, although Raistmer first added those files to AP in the fall of 2014.

v0.44 was a specific (and somewhat rushed) release for the new MB v8 apps - I didn't alter the AP packages for that one.

v0.43b was an AP release. I keep the original source packages I receive from Raistmer, in a folder called - drum roll please - "Lunatics_packs_for_v43b". Looking inside the 'AP for NV' subfolder, the directory listing is

D:\temp\AP7_win_x86_SSE2_OpenCL_NV_r2887>dir /b
AP7_win_x86_SSE2_OpenCL_NV.aistub
AP7_win_x86_SSE2_OpenCL_NV_r2887.exe
ap_cmdline_win_x86_SSE2_OpenCL_NV.txt
AstroPulse_Kernels_r2887.cl
AUTHORS
COPYING
COPYRIGHT
libfftw3f-3-3-4_x86.dll
ReadMe_AstroPulse_OpenCL_NV.txt

- no sign of your 'AstroPulse_NV_config.xml' there. If Raistmer doesn't supply it to me, I can't distribute it to you.

No doubt we'll be talking through the issue over the next few days, and come to a conclusion before the final release. That's one of the benefits of opening up the Beta test to a wider audience.

Thanks Richard. I installed this on one of my crunchers and it seems to be working as well. Actually the SoG app seems to be utilizing more of my GPUs than the x41zi cuda50 app. Cuda50 would stay around 92% utilization and the SoG app has been staying at 97-99% on my 750 tis.

---

- no sign of your 'AstroPulse_NV_config.xml' there. If Raistmer doesn't supply it to me, I can't distribute it to you.

What should it contain ?

Its device specific comandline file which has to be implemented in appinfo.xml as well.

File structure:
<deviceN>
<unroll>N</unroll>
<ffa_block>N</ffa_block>
<ffa_block_fetch>N</ffa_block_fetch>
<oclfft_plan>
<size>32768</size>
<global_radix>N</global_radix>
<local_radix>N</local_radix>
<workgroup_size>N</workgroup_size>
</oclfft_plan>
<tune>
<tune_kernel_index>N</tune_kernel_index>
<tune_workgroup_size_x>N</tune_workgroup_size_x>
<tune_workgroup_size_y>N</tune_workgroup_size_y>
<tune_workgroup_size_z>N</tune_workgroup_size_z>
</tune>
<initial_ffa_sleep_short>N</initial_ffa_sleep_short>
<initial_ffa_sleep_large>N</initial_ffa_sleep_large>
<initial_single_pulse_sleep>N</initial_single_pulse_sleep>
<sbs>N</sbs>
<skip_ffa_precompute>
<no_defaults_scaling>
</deviceN>

---

With each crime and every kindness we birth our future.

If Raistmer doesn't supply it to me, I can't distribute it to you.

Okay, seems as if the ball is in Raistmer's court then. But it does seem to me that any files that a production app could reference should be included in the installer, both for the app_info.xml and as a dummy/empty file, whether or not it's widely used. Hasn't that always been the approach in the past?

- no sign of your 'AstroPulse_NV_config.xml' there. If Raistmer doesn't supply it to me, I can't distribute it to you.

What should it contain ?

Does it actually need to contain anything at all? Aren't the other configuration files simply included in the installer as dummy/empty files whose file names are included in the appropriate sections of the app_info.xml? As long as that's done, it's up to individual users to actually populate the file according to the instructions in the README, if they want to make use of it.

do i think wrong, guppis wus are running slower ? Just guessing, maybe some examples out there ?

But great efforts, thumbs up ! My SoGs (non guppi) runnig 2-3 minutes faster XD

---

If Raistmer doesn't supply it to me, I can't distribute it to you.

Okay, seems as if the ball is in Raistmer's court then. But it does seem to me that any files that a production app could reference should be included in the installer, both for the app_info.xml and as a dummy/empty file, whether or not it's widely used. Hasn't that always been the approach in the past?

I could do that too.

But Richard has to keep a lot of things in mind in this case.
He also had to add the device specific MB_config.xml to make it complete.

---

With each crime and every kindness we birth our future.

Does it actually need to contain anything at all? Aren't the other configuration files simply included in the installer as dummy/empty files whose file names are included in the appropriate sections of the app_info.xml? As long as that's done, it's up to individual users to actually populate the file according to the instructions in the README, if they want to make use of it.

Correct, but it has to be mentioned in the appinfo.xml which makes it again longer.
This also applies for MBs too.

---

With each crime and every kindness we birth our future.

Does it actually need to contain anything at all? Aren't the other configuration files simply included in the installer as dummy/empty files whose file names are included in the appropriate sections of the app_info.xml? As long as that's done, it's up to individual users to actually populate the file according to the instructions in the README, if they want to make use of it.

Correct, but it has to be mentioned in the appinfo.xml which makes it again longer.
This also applies for MBs too.

Don't worry about the size of app_info.xml - that's my problem, and most of it is simple copy/paste with some combinatorial gymnastics to accommodate platform/version/plan_class.

The Beta lost some volume with the discard of MB_v7, but regained it with the need to reference _SoG and _sah at both version 800 and 812. As I warned in the opening post, for this Beta I haven't yet duplicated that effort for the Eleven (!!! *'&_% argh) different ATI v8.12 instances shown on the new applications page. A break for food seemed advisable....

A break for food seemed advisable....

And perhaps a beer....or two???

Anyway, I'm sure you Lunatics can work it out. ;^)

Can I ask here what SoG is?

---

Can I ask here what SoG is?

Signal on GPU
Tullio

---

Hi all, on my little GeForce 610M (mobile) MB8_win_x86_SSE3_OpenCL_NV_r3430_SoG remain locked on 0 % with this mb_cmdline_win_x86_SSE3_OpenCL_NV:

-sbs 128 -spike_fft_thresh 2048 -tune 1 2 1 16 -hp -cpu_lock -total_GPU_instances_num 1 -period_iterations_num 500


Marco.

---

Hi all, on my little GeForce 610M (mobile) MB8_win_x86_SSE3_OpenCL_NV_r3430_SoG remain locked on 0 % with this mb_cmdline_win_x86_SSE3_OpenCL_NV:

-sbs 128 -spike_fft_thresh 2048 -tune 1 2 1 16 -hp -cpu_lock -total_GPU_instances_num 1 -period_iterations_num 500


Marco.

Try to add -no_defaults_scaling to that line and report back.