What we have in this post is pretty much preliminary work, so we'd really like to hear your ideas and suggestions as to what you'd like to know is going on server-side, and what we're doing as a whole.

Right now we would like to get these graphs (and some other ones) automatically generated in their own webpage, with information like what users have given us the best fitness and things like that.

Pretty much we could have whatever information you guys think would be interesting, and we'll also have things we're interested about and looking into on their for our own benefit.

Basically, we'd like a webpage we could check to easily know the status of our different searches, and I thought it would be more interesting with some user input, so we could make that information more interesting to you guys, and also add things you'd be interested in as crunchers.

We've updated the main page of the project, so now you have information on our publications and related grants.

At least my SSE3-App I linked to in this thread does not suffer from any of these shortcomings ;)

I for one am grateful for you making this available Cluster Physik.

I've already added it to www.arizmoon.com which I will be updating now with what I think are the 'correct' SSE2 and SSE apps.

OK, I've updated www.arizmoon.com with what has been agreed in this thread as usable optimized apps for SSE, SSE2 and SSE3.

Please let me know if I'm wrong, thanks.

I have moved my additional download resource to www.zslip.com


.

I. ACKNOWLEDGMENT OF SUPPORT AND DISCLAIMER

An acknowledgment of NSF support and a disclaimer must appear in publications (including Web pages) of any material, whether copyrighted or not, based on or developed under NSF-supported projects:

“This material is based upon work supported by the National Science Foundation under Grant No. (grantee must enter NSF grant number).”

NSF support also must be orally acknowledged during all news media interviews, including popular media such as radio, television and news magazines.

Except for articles or papers published in scientific, technical or professional journals, the following disclaimer must be included:

“Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation.”

@ EigenState

Ohhh ,,my jaw is on the floor !!

Do you really believe the next door Hillbilly can just that easy add his project for participation in Boinc? Is this really the sense of your comment?
The project is hosted under an *.edu address and you need more evidences?

First some guys from one forum attacked this project and now this! It's hard to believe what you have posted.

Please remove your comment or edit it. It's ridiculous!

Actually to correct some misinformation here. The RPI computer science department as a whole does not run this project. There is myself, Nate, dave, and our 4 advisors (1 professor in the physics dept, and 3 in the cs dept). Our advisors have quite a few other projects they're working on (and I myself have another one or two). Either way, the bulk of the work on this project is done by myself, dave and nate. 3 people, not 440. We also have classes and our degree requirements to attend to. This is the nature of graduate level research.

Right now we're operating off an NSF grant which pays for our hardware, Nate, myself and a couple undergrad researchers.

I've updated work generation a bit (it should be a lot more efficient server side, which should help keep work flowing).

also, i'm trying to dynamically generate the fpops estimate for workunits and am trying to get the credit granted for the new WUs to be around 10.

Let me know if this batch works and if credits seem about right.

I renamed my app_info.xml and restarted boinc on all my systems and they are still using Milksop's 1.22 and the test app without any trouble so far.

So I set my prefs to allow test apps, remove app_xml file, reset project and reboot/restart BOINC.

I am still getting 1.22 WU's.. is this correct ?

We're still generating workunits for 1.22, so you should get both. I only generated 100 new workunits with nm_test1, because i didnt want to flood the system with bad workunits (if they didn't work).

Since I haven't heard any complaints about the new batch, I'm going to create a bunch more and see how these do. They'll be under nm_test2.

I've gotten all kinds of errors today, but at the moment I'm getting

01/11/2008 17:54:40|Milkyway@home|Sending scheduler request: Requested by user. Requesting 876 seconds of work, reporting 0 completed tasks
01/11/2008 17:54:45|Milkyway@home|Scheduler request completed: got 0 new tasks
01/11/2008 17:54:45|Milkyway@home|Message from server: Server error: can't attach shared memory

Also, the feeder and like half of the other stuff is offline?

Indeed we have a conundrum. If we improve the code, it will be faster and we will have to lower credits which people dont like. If we don't improve our code, we get yelled at for wasting cpu time.