Dear Creator,

couldyou pls give me a hint how to run the screensaveron Ubuntu 11.10

I have errors:
<stderr.txt>
01:24:22 (15538): Can't open init data file - running in standalone mode


<stderrgfx.txt>
Failed to connect to shared scene
Failed to connect to shared scene
Failed to connect to shared scene
Failed to connect to shared scene
Failed to connect to shared scene
Could not attach to simulation after 5 attempts

TIA!

^ ok then...


Nice screensaver, but I do have some suggestions for future builds:
[quote]1. Needs more continuity. Since the WU's that are available finish for my computer in a mere 30 seconds, the graphics can only run for... 30 seconds. After that, the screensaver just stops (or rather, just stops progressing and hangs). It still functions, but it does not continue over to the next WU. In fact, when you quit the screensaver to look at the graphics for the next one that is already running, the screensaver fails to load (with the error being that it cannot attach to a running process, being the application itself) until the next WU arrives and runs.

Could there be a way for the screensaver to identify when the WU finishes, stay on, and then reattach to the next WU that runs?

2. Needs more... fluidity. When I watched your demo, the particle motion seemed rather fluid and smooth. In contrast, when I viewed the same from my end, it was quite jumpy.. or rather, it just updated whenever it felt like. IN fact, i dont think it updated per .001 Gyr (as it did in the demo). It just updated all over the place, and it was slow at updating. I did not notice a regular interval. is this something that can be fixed? it would look much better if it acted the way your demo had it.

3. a little thing, but the fact that you couldn't pause the screen from rotating annoyed me. could you add an option to enable and disable screen rotation? I would really like to see the particles move on their own instead of seeing it happen while flying around ;)

My machine is beavering away at this project, with, usually, two tasks running simultaneously, and it is reporting results, but the work done credit has not changed for months now!

- For workunits with larger timesteps, it seems very jumpy. There's an option to update at some interval instead of at every opportunity. There is another option to stop the simulation to wait for the graphics, so that every timestep is drawn as a frame and the animation is smooth.
- The orbit trace view will not do what you expect except when using the option to stop the simulation for the graphics
- The optional axes are ugly
- The preference descriptions aren't very good

I added a bunch of preferences to the web project preferences, but they're not quite finished yet (e.g. the default values don't show up in the boxes when you don't have them set).

I made a small demo video a while ago demonstrating it: http://milkyway.cs.rpi.edu/milkyway/download/random_stuff/nbody_graphics_sample.mp4

Try it out, and see if you like it! If you run into any problems or have any recommendations for future versions, please leave a comment below.

Some of my computers run freebsd/amd64, and I found out that the computers which running XP is faster to get milkyway credit than freebsd/amd64.
The funniest thing is, running boinc under wine in freebsd is much faster than running in freebsd itself. The different is so big (like in milkyway under wine to complete the task usually take 2-3 hrs, but under freebsd it take 17-20hrs:( in the same computers even if I tried to speed them up using nice).

Anybody knows why running milkyway under freebsd wine is much faster than under freebsd itself in freebsd/amd64?

Edit:
You can see what I mean is by checking computer ID 368456 which is boinc under freebsd/amd64 wine, and compuer ID 436052 is boinc without wine (both are the same computer)

but saying that, with boinc logging the detected gpu's and their capabilities - someone in the know should be able to make a "check box" option to choose the gpus - and perhaps their capabilities like we can kinda do with the cpu options or post a good thorough "sticky" somewhere with ALL the options and examples of use as hunting for cc_config stuff took quite some time to compile.

So it appears that when Boinc does the hardware query, it's only taking the first card it reads for it's project configurations. I'm tempted to swap cards, but I don't have time for that shenanigans.

If it's app specific, then perhaps the milkyway@home guys need to add 20 lines of code to check the capability of the additional gpu's so that people who are total n00bs like me don't have to muck about in cc_config.

thank you and good night.

Plum_EMD_100K_9783_0

<core_client_version>6.12.34</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
Argument parsing error: -0.3255476365281918500000000: unknown option
<search_application> milkyway_nbody_0.80_windows_x86_64__mt.exe 0.80 Windows x86 double OpenMP, Crlibm </search_application>
22:37:51 (4768): called boinc_finish

</stderr_txt>
]]>