Hello, The Problem [or bug or required enhancement]: A problem in this system has been observed where parallel, multi-threaded applications do not scale properly to multiple graphics cards resulting in low frame rates.
I believe that they may want an enhancement. They may also want a bug fix since they used "fix" and the above uses the word problem. The statement of work indicates that NIST tried to get a "free" fix out of the community but could not. I assume that one task in their list [creation of a test bed] was the reason for no free fix, since that test bed costs money. Example [the following is a task]: . The vendor shall discuss the results and proposed solution with the OSG community and come to a consensus as to the best solution implementation. This tells me that NIST wants some sort of warm fuzzy from the OSG community but see my comment above on the "free" fix. This task already has a failure mode. However, it does consider the issue of interoperability. Will the fix be a best practices type of fix as judged by the OSG community? Will the fix impact other OSG code? But also remember. Somebody is being paid and a task is to get free comments on optimizing and validating the fix. The real question is can the solicitation process be simplified. Is there a way for entities to quickly focus funds similar to the way blender does it [I remember a vague description of the process from Blender BOF's but the process seems to exist]. See the phrase " Wow, so this....". The key word is "Wow". My comment on simplification is that NIST is very supportive of the OSG community and wants the vendor to add the "fix or enhancement" back into the OSG ecosystem. This is the perfect method to accelerate feature wish lists. However, it is targeted for a specific host OS / GPU combination and is NOT a general "enhancement". Of course, the problem may not exist on Red Hat or Fedora or Ubuntu [or <insert Linux variant here>] or Windows or Macintosh. Can NIST prove that it does not exist on those platforms! Some interesting notes: NIST anticipates that the "fix" will require 6 months including the required reports. That means 2 boring progress reports in addition to the real documentation on the fix. Also, there is the preparation time for the quotation. Simplification may be impossible since NIST has to prove that it did not violate any laws [there are lots]. This is a main reason for this post. Can anyone figure out how to simplify and still satisfy rules and performance metrics? Lastly, I believe that this is a positive opportunity and lots can be learned. So, I suppose that NIST should be thanked. Also, apologies for the bandwidth usage. John F. Richardson -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of J.P. Delport Sent: Monday, August 22, 2011 4:57 AM To: OpenSceneGraph Users Subject: Re: [osg-users] An Open Scene Graph solicitation has been posted on FedBizOpps Wow, so this is how a government dept submits a bug report :) Should be nice to hunt this one down, I was just wondering over the weekend what happened to it. References here: http://thread.gmane.org/gmane.comp.graphics.openscenegraph.user/62225 http://thread.gmane.org/gmane.comp.graphics.openscenegraph.user/63954 rgds jp On 19/08/2011 20:31, Judith E Terrill wrote: > For your information, a solicitation to develop a fix for Open Scene > Graph has been posted on FedBizOpps that may be of interest to you. You > may view the solicitation and instructions for responding at: > > https://www.fbo.gov/index?s=opportunity&mode=form&id=5b646272c11b0c2fb01ce61 f954a4555&tab=core&tabmode=list&= > > > Please note that offerors must be registered in CCR > (https://www.bpn.gov/ccr/default.aspx) in order to be considered for award. > If you have any questions, please contact Divya Soni at > [email protected]. > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
