There is a Subscribe button near the top of the page. Click that in the Optimised apps thread and you should get email notifications every time there's a new post.

Specifically the thread: Optimised Applications and Other Binaries if any has trouble finding it.

---

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

Specifically the thread: Optimised Applications and Other Binaries if any has trouble finding it.

Yesssss.... Thanks! :-)

I think to add a feature only used by a fraction of users is not worth implementing.
Also the appinfo already is very huge.

If a feature is an integral part of the app, it shouldn't matter what fraction of users take advantage of it. After all, there are multiple cmdline files and an mbcuda.cfg file that are already included in the Lunatics installer, even though very few people actually use them (or even know about them, for that matter). I would think that the device-specific config files should only be omitted if there's a technical roadblock preventing their inclusion.

As to the size of the app_info file, its very size and complexity are what already make it so difficult to manually edit, which means that anything the installer can do to facilitate the use of a feature would be most welcome. After all, more people might use a feature if they can do so without messing around with the guts of an app_info file.

---

I saw the release of v0.44 saying "Please note that we have been concentrating on accuracy and precision for this release: the applications may run slower than you are used to, because of the enhanced precision required by v8.". Does that mean there are more instructions run by x87 FPU instead of SSE unit? I understand x87 FPU actually calculates at 80bit precision internally. SSE however calculates at 64bit. Anyone knows? Thank you in advance.

---

Yes

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Thank you Jason.

---

Thank you Jason.

+1

---

I Desire Peace and Justice, Jim Scott (Mod-Ret.)

I just discovered that the Astropulse device-specific configuration files (for those with multiple, disparate GPUs) that Raistmer added back in the fall of 2014 apparently still haven't found their way into the app_info.xml file generated by the Lunatics installer.
For Nvidia GPUs, that would be 'AstroPulse_NV_config.xml'

Are you sure this file have to be described in app_info.xml to be used by AstroPulse app?

In AP7_win_x86_SSE2_OpenCL_ATI_r2742.exe I see this exact string (Copy/Paste):
AstroPulse_ATi_config.xml

I'm not sure if the app needs <soft_link> file in 'slots' or it directly checks the app directory (next to real .exe)

---

 


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

Are you sure this file have to be described in app_info.xml to be used by AstroPulse app?

It is necessary to mention the file in appinfo.xml to work properly.
I have tested this detailed.
Last year i made config file available on my cloud but there was not much interest at all.

example

<file_info>
<name>Astropulse_ATI_config.xml</name>
</file_info>


.
.
.
.

<file_ref>
<file_name>Astropulse_ATI_config.xml</file_name>
</file_ref>

---

With each crime and every kindness we birth our future.

http://setiathome.berkeley.edu/result.php?resultid=4695403483

Got my first computation error on lunartics AVX task.

---

http://setiathome.berkeley.edu/result.php?resultid=4695403483

Got my first computation error on lunartics AVX task.

Not an app issue i guess.

<message>
finish file present too long
</message>

---

With each crime and every kindness we birth our future.

May I hope all the CPU and GPU tasks that come back with non-abort errors or as invalid, along with stack traces I see when I drill into them, are aggregated into a top-level developer's view and analyzed for problem trends, resulting in fixes incorporated into future releases, instead of depending on individuals reporting them?

Tuna

---

May I hope all the CPU and GPU tasks that come back with non-abort errors or as invalid, along with stack traces I see when I drill into them, are aggregated into a top-level developer's view and analyzed for problem trends, resulting in fixes incorporated into future releases, instead of depending on individuals reporting them?

Tuna

Taking in account that big part of those developers reside outside of Berkeley w/o direct access to server and their logs... I would consider such _highly_ improbable.
And no agregated view can replace well defined and meaningful bug report, btw.

Good evening(my time) since I am new to lunatics I just want to ask a couple of questions I installed lunatics on one of my crunch only rigs about 5 days ago after that I think I have a baseline to go by so I would like to start tweaking things particularly with the gpu but I cannot find the files that I need to edit maybe I am looking in the wrong place or am just missing them or I did something wrong with the install. Thanks for any help.

---

ME AND MY BOY LOOKING FOR ET

Good evening(my time) since I am new to lunatics I just want to ask a couple of questions I installed lunatics on one of my crunch only rigs about 5 days ago after that I think I have a baseline to go by so I would like to start tweaking things particularly with the gpu but I cannot find the files that I need to edit maybe I am looking in the wrong place or am just missing them or I did something wrong with the install. Thanks for any help.

Is your data directory the default location or did you set a different location during installation?

If you are unsure you can open the Event Log in BOINC Manager. The data directory location is displayed near the top.
14-Mar-2016 12:34:48 [---] Starting BOINC client version 7.6.23 for windows_x86_64
14-Mar-2016 12:34:48 [---] log flags: sched_ops
14-Mar-2016 12:34:48 [---] Libraries: libcurl/7.45.0 OpenSSL/1.0.2d zlib/1.2.8
14-Mar-2016 12:34:48 [---] Data directory: C:\ProgramData\BOINC

The default location is located in a hidden folder for Windows 7 and higher. So you will need to either show hidden folders or manually enter the path.

---

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

Checked the event log to make sure and it says that is where it is at I was pretty sure that I did not change the location but another thought is since I am new to lunatics I do not know where to look even though I read several threads here a lot of the info is directed at people that already know what they are doing not always to newbies like me. Sorry for taking so long to respond but I got some bad news from a couple of my friends that their Dad who had a stroke a month ago is not doing well at all and since we have been friends and hunting buddies for 35 years I had to go see him. Thanks again for your help.

---

ME AND MY BOY LOOKING FOR ET

Thanks Richard for the detail instructions . Very clear and understandable for newbees .

---

Hoping this might be the right thread for this. Having an intermittent issue here with V8 GPU tasks erroring out. This seems to be coupled with freezes and the occasional video driver crash. Build here is Win7x64, current Lunatics apps, and I believe not much tweaking to default params. 3.0ghz Core2Quad, 8gb ram with 2x 750ti.

Results are:
Exit status 194 (0xc2) EXIT_ABORTED_BY_CLIENT
and
<![CDATA[
<message>
finish file present too long
</message>
<stderr_txt>

Seems to happen at the end of a more or less normal run duration.
Any thoughts?
Thanks in advance.

---

Any thoughts?

From memory it relates to the BOINC Manager expecting things to be done in a certain time, and they're not, so the error results.

It was suggested I upgrade BOINC, so I upgraded to v7.6.6 (I think that was the version that got the work around for that particular issue) and I haven't seen that error message since; whereas I used to get it every few weeks or so.

---

Grant
Darwin NT

Any thoughts?

From memory it relates to the BOINC Manager expecting things to be done in a certain time, and they're not, so the error results.

It was suggested I upgrade BOINC, so I upgraded to v7.6.6 (I think that was the version that got the work around for that particular issue) and I haven't seen that error message since; whereas I used to get it every few weeks or so.

Thanks, Grant. As it happens, I've got all 4 crunchers on 7.6.22 at this point. Should have included that info.

---