<file_ref>
<file_name>MultiBeam_NV_config.xml</file_name>
</file_ref>

<file_ref>
<file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name>
<open_name>mb_cmdline.txt</open_name>

Hi,
It sounds counter intuitive. Normally a file listed after another file would replace the equivalent parameters from the first file.

I have had a "sea change" so that I no longer have the urge to run a 1060/750 combo (the Motherboard of the 2nd box I had a 1060 in died so I moved it in to the 750 box) so I am now only an interested bystander.

Tom

---

A proud member of the OFA (Old Farts Association).

<file_ref>
<file_name>MultiBeam_NV_config.xml</file_name>
</file_ref>

<file_ref>
<file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name>
<open_name>mb_cmdline.txt</open_name>

Hi,
It sounds counter intuitive. Normally a file listed after another file would replace the equivalent parameters from the first file.

No

A) Both files (will) exist in SETI@home directory so both have to be described in app_info.xml (no matter in which order)

BOINC reads app_info.xml and only looks if the files exist, BOINC does not read those files.
OTOH app don't know what is in app_info.xml (does not read it)


B) Both files (mb_cmdline.txt and MultiBeam_NV_config.xml) are read by the app so it is up to the app programmer (Raistmer) how and in which order they are interpreted.

I think the order is :

0) App sets all values to default
(imagine there is table in RAM which is filled with values for all parameters)


1) Direct switches in app_info.xml :
<cmdline>-sbs 512</cmdline>

... which means BOINC will start the app like this:
MB8_win_x86_SSE3_OpenCL_NV_SoG_r3557.exe -sbs 512
(in the table in RAM the value for -sbs is set/changed)


2) App reads mb_cmdline.txt
(Yes, the app looks for and sees that name only (in 'slots') and <soft_link> in it redirects to the real file.
If you run app offline (outside BOINC, for test) the real file have to be named mb_cmdline.txt and not anything different
)
Any switches in mb_cmdline.txt that are also present in the <cmdline> will have the new values from mb_cmdline.txt

E.g. the following will set 3 new values (and -sbs will become 256):
-period_iterations_num 10 -hp -sbs 256

But this will set 2 new values (and -sbs will stay unchanged at 512):
-period_iterations_num 10 -hp

All other parameters remain at default values as per "0)"


3) App reads MultiBeam_NV_config.xml
You can e.g. set/change here only some parameters for only one of the GPUs (e.g. GPU #2)

I imagine app creates copy of the "table in RAM" and changes these "some parameters" only in that "table #2" which will be used for GPU #2
GPU #1 will use the "original table" created in previous steps 0) ... 2)

Moral:
The last interpreted replaces the same settings used in previously interpreted.
 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Correction.

The order is always

appinfo.xml
comandline text file
device specific config xml file

Readme.txt

For device-specific settings in multi-GPU systems it's possible to override some of command-line options via
application config file.


example:
period_iterations_num is set to to 40 in comand line text file but set to 30 in device specifc config.xml

Maximum single buffer size set to:786MB
Number of period iterations for PulseFind set to:40
Number of period iterations for PulseFind set to:30
Device-specific SpikeFind FFT size threshold override set to:4096
Device-specific oclFFT plan of size 8 : global radix override: 256, local radix override:16, workgroup size override 256
maximum local memory kernel FFT size 2048, number of local memory banks 64, minimal local memory coalesce width 64
Device-specific oclFFT plan of size 16 : global radix override: 256, local radix override:16, workgroup size override 256
maximum local memory kernel FFT size 2048, number of local memory banks 64, minimal local memory coalesce width 64
Device-specific oclFFT plan of size 32 : global radix override: 256, local radix override:16, workgroup size override 256
maximum local memory kernel FFT size 2048, number of local memory banks 64, minimal local memory coalesce width 64
Device-specific oclFFT plan of size 64 : global radix override: 256, local radix override:16, workgroup size override 256
maximum local memory kernel FFT size 2048, number of local memory banks 64, minimal local memory coalesce width 64
Device-specific oclFFT plan of size 128 : global radix override: 256, local radix override:16, workgroup size override 256

---

With each crime and every kindness we birth our future.

This is all great information. Biggest change for me is going to be moving app_config parameters back into the command line text file in app_info.

---

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

A proud member of the OFA (Old Farts Association)