Slashdot Mirror


Sandia Releases DAKOTA Toolkit under GPL

Consul writes " DAKOTA, a powerful toolkit for doing engineering analysis, has now been released under the GPL. Space Daily has the details about the tookkit."

38 of 131 comments (clear)

  1. Groovy, baby by EvilAlien · · Score: 3, Insightful

    Time to get engineers out from under the misperception that only through whoring themselves to vendors shall solutions be reached.

    --
    perl -e 'print $i=pack(c5, (41*2), sqrt(7056), (unpack(c,H)-2), oct(115), 10)'
    1. Re:Groovy, baby by Requiem · · Score: 2, Insightful

      Yeah, because a lot of the laymen I know do engineering analysis.

  2. Addendum to the article post by Consul · · Score: 5, Informative
    As the submitter of this article, I'm afraid I missed a couple of important things.

    First, here's a link to the site for the software itself: DAKOTA

    And second, as seen on this page, there are two libraries (DOT and NPSOL) required by DAKOTA that are expensive commercial software products. So, in order to make DAKOTA truly free, these libraries will need to be replaced with GPL/LGPL equivilants. I just wish I had the programming skill to help with something of this scale.

    There is a third library needed, called OPT++, that is not GPL or an Artistic license. I'm unable to determine what this library is or its terms of use, as the page that the DAKOTA web site links to is no good.

    All of the other libraries needed by DAKOTA are GPL/LGPL, with one using an Artistic license.

    --

    -----

    "You spilled my egg... I needed that egg."

    1. Re:Addendum to the article post by 56ker · · Score: 2

      "has now been released under the GPL."....

      "there are two libraries (DOT and NPSOL) required by DAKOTA that are expensive commercial software products"

      I knew it had the look of something too good to be true!

    2. Re:Addendum to the article post by cmowire · · Score: 3, Informative

      Yeah, but it doesn't NEED DOT and NPSOL to work, it can work with the other libraries.

      I bet it sucks without them, tho. ;)

    3. Re:Addendum to the article post by SanLouBlues · · Score: 2

      If you can afford the hardware to run this stuff on the scale the website suggests, then licensing shouldn't be that much of a percentage-wise increase.

    4. Re:Addendum to the article post by realdpk · · Score: 2

      "So, in order to make DAKOTA truly free, these libraries will need to be replaced with GPL/LGPL equivilants"

      Only for some definitions of "free".

    5. Re:Addendum to the article post by auferstehung · · Score: 3, Insightful

      Note the use of the terms "utilizes" and "optional" in the snippage from the DAKOTA website below. I interpret this to mean that they offer optional features (the non-linear kind) that DAKOTA will use if available, but is not a requirement.

      ****snippage below********

      DAKOTA utilizes the following external optimization libraries:

      * DOT (nonlinear programming algorithms from Vanderplaats Research and Development; optional extension requiring a separate commercial license)

      * NPSOL (nonlinear programming algorithms from Stanford Business Software; optional extension requiring a separate commercial license)

      * CONMIN (public domain nonlinear programming algorithms; no license required for inclusion in DAKOTA distribution)

      --
      Logic is not Divine.
  3. Can this be exported? by cperciva · · Score: 4, Insightful

    Given the potential applicability of this to weapons design, I'm surprised the US government is allowing this to be distributed.

    1. Re:Can this be exported? by cperciva · · Score: 2

      DAKOTA can be applied to a whole host of things besides weapons development.

      Yes, and cryptography can be applied to a whole host of things besides planning terrorism. You, I, and the people at Sandia know this; but unfortunately it's the Washington politicos who make the laws.

  4. Huh? by sh4de · · Score: 2, Funny
    Space Daily has the details about the tookkit

    Who took the kit?


    1. Re:Huh? by DickPhallus · · Score: 2, Funny

      I took it!

      Sorry, I couldn't resist...

      --

      --
      Some weasel took the cork out of my lunch.
    2. Re:Huh? by pete-classic · · Score: 2

      It doesn't say took it, it says tookkit. I don't understand it in context, but tookkit means "fool of a Took" in the Hobbit's native tounge.

      -Peter

    3. Re:Huh? by abe+ferlman · · Score: 2

      Wait for it... Wait for it...

      "Fool of a Took!"
      ---Gandalf

      --
      microsoftword.mp3 - it doesn't care that they're not words...
    4. Re:Huh? by Consul · · Score: 2

      I would like to point out that I did not write it that way. I just said "datails here." Apparently, Slashdot editors do edit the words sent in to them.

      --

      -----

      "You spilled my egg... I needed that egg."

  5. ....not quite under the GPL? by MattGWU · · Score: 2, Insightful

    From the article: "The only restriction is that people cannot take the DAKOTA software, change it, and then sell it," Eldred says. "They can, however, design products with DAKOTA and sell their products."

    Isn't that contrary to the terms of the GPL? As long as the source is provided, and the resultant code is released under the GPL, isn't modification and resale legal? Just something that caught my eye in the article.

    --
    "These people look deep within my soul and assign me a number based on the order in which I joined" --Homer re:
    1. Re:....not quite under the GPL? by wfrp01 · · Score: 2

      From the article: ... They can, however, design products with DAKOTA and sell their products.

      Isn't that contrary to the terms of the GPL?


      Ahhh, yes, they speak of a world outside of the digital realm. A material world. But of course it is a fantasy. The amount of information required to describe these so called "corporeal" objects, with their "atoms" and "quarks" and so forth defies the imagination. Don't worry. It would take more 1's and 0's than can be addressed by even Super User to describe the simplest of the fantastical objects said to inhabit this dream world. So relax, and get some sleep. There's nothing to worry about.

      --

      --Lawrence Lessig for Congress!
  6. Damnit, You _Can_ Sell GPL Software by John+Hasler · · Score: 2, Informative

    '"The only restriction is that people cannot take the DAKOTA software, change it, and then sell it," Eldred says.'

    If it is under the GPL they most certainly can. They are merely required to license their version to their customers under the GPL.

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
  7. your tax dollars at work by Lord+Omlette · · Score: 2, Insightful

    Well, for everyone complaining about public risk, private profit... DAYUM!

    --
    [o]_O
  8. Great news! by Anonymous Coward · · Score: 3, Informative

    Our department (structural integrity testing of BR23/07 machines) has been publishing reviews that were competitive with major journals. The thing is, we're academic, so the licensing terms on software such as this has always been prohibitive. Instead, we've been forced to use things like SciVis CFS/SVW, which really doesn't cut the mustard as far as hyperbolic tonicity, to name one painful, painful shortcoming. I actually had to spend quite a bit of time (two and half aweeks) handwriting a template to get back some of the functionality we would have had from the get-go with DAKOTA.
    That's time spent away from actually running analyses. So, this is a Good Thing.

  9. Isn't GPL a step *backward*? by Weasel+Boy · · Score: 4, Interesting

    In the past, software written in government labs (e.g., LINPACK) was released into the Public Domain. Isn't using GPL actually granting taxpayers less access to the fruits of their labors than releasing the code into the Public Domain?

    1. Re:Isn't GPL a step *backward*? by Arandir · · Score: 4, Insightful

      I fully agree. Taxpayer funded software should be placed into the public domain. It doens't matter if this tax money is for defense spending or corporate welfare. If the public paid for it then it belongs to the entire public, and not just a politically correct subgroup.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    2. Re:Isn't GPL a step *backward*? by Weasel+Boy · · Score: 2

      "The GPL guarantees the software stays public, but the public domain doesn't."

      How so? Sure, a company can invest their own effort to modify and release it as a proprietary product. But the part that was originally released as Public Domain is still public, and itself is in no way diminished by what happens to the private fork of the code.

      Someone can make a private fork, but they can never remove the public part from the Public Domain.

    3. Re:Isn't GPL a step *backward*? by jerryasher · · Score: 3, Insightful

      I won't disagree with you entirely, but granting a GPL license may actually help promote commerce in certain circumstances.

      In 1989 I worked for Inference. Inference sold a well regarded LISP based expert system shell (ART). It cost a lot of money and ran on very expensive workstations. NASA came along and cloned it with a C application (CLIPS) that was released into the public domain (if I recall correctly.). In many ways, CLIPS was the death of ART, and various competitors came along that incorporated CLIPS and competed in sales against ART. So in similar ways, NASA and taxpayer dollars killed off the main product of the privately held company that developed the initial technology.

      Was it "fair" for NASA to clone ART in that manner? I dunno. It wasn't kind to our paychecks, but that may be irrelevant.

      If CLIPS has been released with a GPL, I think both taxpayer and Inference's private investors would have been served. Inference would not have to worry about competitors being given taxpayer software that allowed them to so quickly catch up with our efforts, and the taxpayers would have been able to benefit by having the code released in a way that brought the high tech ART into schools, research institutes, and to anyone willing to comply with the GPL.

    4. Re:Isn't GPL a step *backward*? by Arandir · · Score: 2

      Each one has its advantages and disadvantages, just as long as we look at which one fits best for a particular situation all is good and balance is maintained. Or something like that...

      I agree. In the particular situation that is taxpayer funded software, there should be zero restrictions on its use by the taxpayer. That means public domain.

      Derivative works will not be public domain, but those derivative bits were not funded by the taxpayer, only the original bits.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  10. Mirror by ttyp0 · · Score: 2, Informative
    Here is a mirror before the site goes down

    http://www.spacedaily.com/news/materials-02h.html

  11. Free as in... by Zen+Mastuh · · Score: 2, Funny
    • Speech (You won't be jailed for it)
    • Beer (Cup fee may be required)
    • Crack (The first one is always free)
    Please elaborate.
    --
    "What is the sound of one belly slapping?"
    1. Re:Free as in... by Consul · · Score: 2

      Free as in "Free of Insane Corporate Licensing". But free as in speech works, too.

      --

      -----

      "You spilled my egg... I needed that egg."

  12. GPL is a good choice by mikosullivan · · Score: 4, Insightful

    GPL is an excellent choice for releasing taxpayer funded software. By releasing the software as GPL you ensure the maximum value for the taxpayer. The software will continue to improve and benefit everybody, including the people who paid for its original development. If it were released under some other license the taxpayer would be less likely to get back improved versions of the software. Don't get me wrong, I'm OK with the BSD license, but GPL is so much better.

    --
    Miko O'Sullivan
    1. Re:GPL is a good choice by Gat1024 · · Score: 3, Insightful

      Not really. If a company wants to include the software in their own custom tool, then they have to release their custom tool under the GPL. Now their taxes paid for that research code just like your taxes did. Probably more so since corporations pay much more tax on average. I hear that corporations and the rich are responsible for most of the tax collected by the IRS but I don't have ratios. I'll see if I can find the link.

      Why can't they use that research code in proprietary work? The original is still there. And the original can still be improved if need be. Any duplication of work would just be

      The public work may actually reduce the cost of the proprietary product since the company can only charge for the value that they add. Any educated consumer can way the pros and cons of using the public version or the proprietary version.

      Maybe even, the product has nothing to do with engineering but the algorithms and/or code works in a completely different domain -- with some tinkering. So now the company must either grow their own solution or give away their jewels. Even though their tax dollars have paid for a solution that is there today.

    2. Re:GPL is a good choice by AIXadmin · · Score: 2

      I think the BSD license provides maxamized value for tax payer software. If you release something under GPL that was funded by tax-payers. You limit the amount of people who can use it. Companies that want to link (Apple's Aqua interface) closed libraries can't. This limits the usefullness of the software to taxpayers. Remember taxpayers are individuals AND corporations.

  13. Some useful info about licensing and libraries by Anonymous Coward · · Score: 2, Informative
    For the folks who would rather read the comments than the original news, here are some details about the licensing, straight from this page. This should help answer questions raised by this quote from the article:
    The only restriction is that people cannot take the DAKOTA software, change it, and then sell it," Eldred says. "They can, however, design products with DAKOTA and sell their products."
    Obviously he was misquoted.

    Notice that there are several GPLed optimization libraries there. That's GOOD news, since writing that sort of routine for high dimensions is not trivial. So, here's the info:



    Open Source Release
    DAKOTA Version 3.0 is available for download under a GNU General Public License (GPL).

    To initiate the download, first fill out the short Registration Form.

    Source code tar files and binaries for selected platforms are available, as well as subscriptions to the user notification email list. Please notify us at dakota@sandia.gov if you experience any difficulties. We have started a FAQ for logging any difficulties encountered in downloading, building, and executing DAKOTA. Release notes are also available.

    Supported Platforms and Software Dependencies
    DAKOTA runs on most Unix platforms including Sun Solaris, HP UX, IBM AIX, SGI IRIX, DEC OSF, and Linux (PC and DEC). It also runs on the Intel Teraflop machine (ASCI Red) and Sandia's Computational Plant (CPlant). A Windows port is not planned at this time (Windows users might consider VMware for Linux dual-boot or a planned capability for XML-based resource distribution).

    A transition from non-ANSI C++ to ANSI C++ has been completed for DAKOTA version 3.0. The ANSI C++ version of DAKOTA uses vector and list templates from the Standard Template Library (STL) available as part of the ANSI C++ standard. This allows the latest DAKOTA source distributions to be built independent of any commercial software (DOT and NPSOL are optional extensions). However, for builds on non-ANSI C++ compilers lacking STL, vector and list templates from the commercial product Tools.h++ from Rogue Wave software can be used in place of STL. This will require either a high-end development environment which includes Tools.h++ (e.g., Sun Solaris Workshop) or a separate commercial license from Rogue Wave.

    DAKOTA utilizes the following external optimization libraries:

    * DOT (nonlinear programming algorithms from Vanderplaats Research and Development; optional extension requiring a separate commercial license)
    * NPSOL (nonlinear programming algorithms from Stanford Business Software; optional extension requiring a separate commercial license)
    * CONMIN (public domain nonlinear programming algorithms; no license required for inclusion in DAKOTA distribution)

    the following Sandia optimization, design of experiments, and uncertainty quantification libraries:

    * SGOPT (stochastic global optimization algorithms; available under GNU LGPL)
    * PICO (branch and bound for mixed integer nonlinear programs; available under GNU LGPL)
    * OPT++ (nonlinear and direct search optimization algorithms; available under GNU LGPL); OPT++ additionally uses NEWMAT09 (serial vector/matrix utilities; conditions of use)
    * DDACE (design and analysis of computer experiments; GNU LGPL in process)
    * APPS (asynchronous parallel pattern search; available under GNU LGPL).
    * DAKOTA/UQ (sampling, analytic reliability, and polynomial chaos expansion methods for uncertainty quantification; part of the DAKOTA GNU GPL license)
    * rSQP++ (large-scale optimization algorithms for simultaneous analysis and design; available under an Artistic license)

    the following Sandia utility libraries:

    * UTILIB (utility library; available under GNU LGPL)
    * PETRA (serial/parallel vector/matrix utilities; available under GNU LGPL)

    and the following external utility libraries:

    * MPI (parallel distributed-memory communication via message-passing; either the public domain MPICH or hardware-specific MPI versions; no license required)
    * PLplot (graphics; available under GNU LGPL)

    To the extent possible, all noncommercial libraries will be included in the DAKOTA tar files available for download. DAKOTA uses a flexible configuration management system to configure with any desired subset of these available packages. If any of the commercial packages are desired, then these must be licensed separately for source code (preferable) or target platform object libraries (less desirable, but workable with minor configuration modifications). These distributions are then installed in the appropriate DAKOTA subdirectories prior to building DAKOTA.

  14. No free rides on MY tax dollars by A+nonymous+Coward · · Score: 2

    How about "public" land? The equivalent of public domain is first come first server, squatters welcome, take what you want, no accounatbility.

    The equivalent of GPL is take only pictures, leave only footprints.

    The mining corps certainly like the public domain attitude.

    Seems to me, my tax dollars paid for it, I see no reason why anyone should get it with no accountability. If some company wants to use something my tax dollars paid for, they can damn well pay back in kind.

  15. Babies from the Shire by A+nonymous+Coward · · Score: 2

    Took babies, to be exact. Did ya never read The Hobbit laddie?

  16. why was this modded as flamebait? by jerryasher · · Score: 3, Insightful

    So why was the parent of this comment modded as flamebait? It is a completely verifiable anecdote involving an occasion when the govt, industry, IP as in intellectual property, and taxpayer funds collided.

    So tell me how that was flamebait so I can better post in the future.

  17. 10% is a LOT by alexhmit01 · · Score: 2

    Do realize that something like 30% of businesses are corporations, another 10% of partnerships, and 60% or so are sole proprietorships that pay taxes at their owners rate. The lower 50% of the population pays 4% of the INCOME tax.

    Those corporations pay 10% of the taxes at 30%, pretty reasonable. Remember those same corporations are paying out salaries to the executives and programmers that pay taxes. They are also paying payroll taxes, etc.

    Corporations pay a lot, especially when you factor in their management.

    Regardless, you should have EQUAL rights to the government's work, not more.

    Alex

  18. college, as there's nothing else to do... by green+pizza · · Score: 2

    ...in the Dakotas. Farming doesn't make money anymore, blizzards aren't too fun, and Hostfest & ND State Fair are the same thing year after year. Even Microsoft is slowly closing down their Fargo business unit (which used to be Great Plains Software before the MSFT extend/embrace/extinguish phases).

    Fifty years from now the Dakotas will be known as "that Canadian grain distribution point". "Lots of wind generators there, too".

    Sigh.

  19. Stop Whining, Start Contracting GPL coders by BadlandZ · · Score: 2
    OK, 3 non-GPL libs needed. Set projects up with GNU/GPL basis.

    As a long time (10+ years IRIX) UNIX, and short time (5+ years) Linux user. Give us the OPTION of hiring/contracting/investing in Open Source!

    Every single time have the option of laying out $100 to $2,000 US for software, I _always_ look for a contractor how has _almost_ done it GPL and am ready to write them a check to finish the job. Mo other option is PAYING FOR SOFTWARE, and I know the more GPL I pay to get done, and more people like me, the less software OVERALL I will have to buy.

    So, my comment is simply, put up or shut up!

    Sadly, this project doesn't affect me, so I can't offer money for it. But I have offered GPL coders SOO MUCH in the past that hasn't been taken up on, I am SICK TO DEATH of hearing the "closed commercial is better now" arguement.