Friday, September 15, 2006

Well, since Martin was the only one to post any questions before I go to bed I guess the top ten will be his questions for the week.

When do we get to crunch on the new ALFA WUs?
When next for a reobservation run?
How well do the s@h-enhanced recrunched WUs compare to the s@h-classic results?

Ouch, these questions are best left to the S@H group.  I had meant for this to be about the BOINC software itself since I really can't speak for any of the projects.

I suppose I could attempt to clear up any confusion in what my roll is.

First off let me start out by saying that David A. manages multiple projects, of which S@H and BOINC are but two of them. I was hired to be a BOINC developer.

At the time I was hired bug investigations and fixes for SETIBOINC was divided up amongst the existing team which also had to manage SETI Classic. SETI Classic kept people pretty busy most of the time as people were running from one fire to the next. Under the existing model SETIBOINC was going to take awhile to finish up, so after discussing things over with David we decided that the best course of action would be to have me to head up the SETIBOINC migration until the migration was complete.  SETIBOINC completed its migration in December 2005 and so my regular participation in the day to day happenings with S@H came to an end.

My role these days mostly involve helping David design and implement new features that will help drive further adoption by both new projects and new participants. I also manage the build, test, and release processes for BOINC.

These days I know just about as much as you all do about what S@H is up too.  When David and I talk, in our daily phone calls, it is all about what is going on with BOINC.

What happened to utilising GPUs for processing WUs? (Are single precision floats good enough?)

Starting with BOINC 5.6 it will detect CPU features such as SSE and 3DNow as well as video cards. All the demand for video card detection has come from the community at large, so I don't know of any project that is actively developing a client.

Whether single precision floats are good enough, that is up to the project.

I believe the biggest problem is actually the memory bus bandwidth between the systems main memory and the video card.  Until PCI-Express was released the video card bus was design to push data to the video card as quickly as possible but didn't do very well transferring data from the video card to system memory. It is my understanding that PCI-Express can handle the loads that DC apps will generate.

I suspect that once BOINC 5.6 is released we'll be able to start publishing video card and CPU feature data to the stat sites and let them start generating some useful graphs for projects to look at.  Once the projects know what is out there they might be able to justify the expense of specialized clients.

What of continued funding for Boinc and for s@h?

I can only speak about BOINC here, but I believe BOINC has secured funding for a couple of years.

Well, off to bed now.

----- Rom

Friday, September 15, 2006 1:22:16 PM (Eastern Daylight Time, UTC-04:00)
Hi Rom,

OK I forgot to post a few questions so here are mine for next week

I know we have had posts from you regarding BOINC and consoles I would just like to know more info about the kind of technical challenges you will face whilst attempting to port BOINC over to them?

How is the simple GUI coming on any ETA on this? Does it work well from what you have seen?

Finally how is the sand-boxing of BOINC on Windows coming along as I think this will help put some peoples minds at ease
Saturday, September 16, 2006 1:25:47 PM (Eastern Daylight Time, UTC-04:00)
More on the Simple GUI.. Will it be released to beta testers?

When will 5.6 be released and what are the main improvements ? What in the pipeline after 5.6 ?

Will we ever get column sorting in BoincManager ?

Talk between Boinc projects and Boinc and vise versa seems minimal (and project to project). No-one seems to know what each other is doing, could there be an improvement of talk between them, like modifications to the servers, message boards, stats and developments in the pipeline.

Why do the Developers not use the BOINC message boards ? e.g. propose ideas and give announcements as to future improvements or even ask for bugs reports or even just mention they need help in particular areas.

Could the 'BOINC' board be somehow integrated into every project board, lots of BOINC chat happens in particular projects (e.g. seti, rosetta, einstein) and luck seems to play the part of other people seeing it. So having a seemless integration to one centralised BOINC areRosettaEinsteinseamlessa maybe of benefit to all.

When will the server side take on the client side naming conventions, for example 'task, work done' are used in the clients side -> 'work unit, credit' is used the server side. There is a mismatch in terminology.

Where does BOINC need help ?
Saturday, September 16, 2006 7:33:57 PM (Eastern Daylight Time, UTC-04:00)
Can you explain more on Average CPU efficiency and Result Duration Correction Factor? There seems to be some confusion about this, and little definate knowledge. For instance, some say a lower RDCF is better, others say an RDCF closer to 1.0 is best. Which is the truth? Or are these SETI related questions too! ;-)
OzzFan
Sunday, September 17, 2006 1:32:09 AM (Eastern Daylight Time, UTC-04:00)
boinc version release notes do not seam as complete as they were before or am i looking in the incorect places

thank you
Stanley A Bourdon
Monday, September 18, 2006 3:30:45 AM (Eastern Daylight Time, UTC-04:00)
Oh yeah forgot about the BOINC workshop your attending this week.

Any plans on releasing the full minutes of what went on (when your back), I read up on the 1st one but was a bit disappointed with the info on show it only gave a brief overview of what went on.
Comments are closed.