Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
NASA Software Earth Operating Systems Space Technology

NASA Releases 2017-2018 Catalog of Software For Free (nasa.gov) 71

mspohr writes: Eureka Magazine has a story about the latest NASA 2017-2018 software catalog. From the report: "NASA has released its 2017-2018 software catalogue free of charge to the public, without any royalty or copyright fees. This third edition of the publication has contributions from all the agency's centers on data processing/storage, business systems, operations, propulsion and aeronautics. It includes many of the tools NASA uses to explore space and broaden our understanding of the universe. 'The software catalogue is our way of supporting the innovation economy by granting access to tools used by today's top aerospace professionals to entrepreneurs, small businesses, academia and industry,' said Steve Jurczyk, associate administrator for NASA's Space Technology Mission Directorate (STMD) in Washington. 'Access to these software codes has the potential to generate tangible benefits that create jobs, earn revenue and save lives.'" Amazing amount of quality software... it IS rocket science. Further reading (and digesting): TechCrunch
This discussion has been archived. No new comments can be posted.

NASA Releases 2017-2018 Catalog of Software For Free

Comments Filter:
  • 'Scuze me? (Score:1, Insightful)

    by SeaFox ( 739806 )

    Eureka Magazine has a story about the latest NASA 2017-2018 software catalog. From the report: "NASA has released its 2017-2018 software catalogue free of charge to the public, without any royalty or copyright fees.

    Seems to me the software was already paid for by me. Or does NASA think their budget grows on a money tree in space?

    • Re: (Score:3, Insightful)

      by Anonymous Coward

      Yeah. And the ISS was in part paid by me, so I want a ticket on the next ride there to inspect my property!

      Just because something is funded by taxes doesn't mean that it automatically lands in the public domain. Sorry.

      But I think it is good when a government agency decides to give back to the public, stuff that lies outside of their normal operations.

      • Re:'Scuze me? (Score:5, Insightful)

        by SeaFox ( 739806 ) on Friday March 03, 2017 @02:42AM (#53968115)

        Yeah. And the ISS was in part paid by me, so I want a ticket on the next ride there to inspect my property!

        Just because something is funded by taxes doesn't mean that it automatically lands in the public domain. Sorry.

        Most appropriate response. [imgur.com]

        • Yeah. And the ISS was in part paid by me, so I want a ticket on the next ride there to inspect my property!

          The local municipal sewage plant was paid for by me. And the city would be happy to arrange an inspection tour.

          But they'd still expect me to drive myself there.

      • >Just because something is funded by taxes doesn't mean that it automatically lands in the public domain. Sorry.

        That ought to be the default outcome however. If they want to keep something out of the public's hands - they should have to defend that decision and request a special exemption.

        Your ISS example is silly though. The reason you can't demand a ticket isn't because you don't own a legitimate share in that great endeavour - but because the cost of getting you there would EXCEED your share. If you p

        • Re:'Scuze me? (Score:4, Informative)

          by Rei ( 128717 ) on Friday March 03, 2017 @05:02AM (#53968371) Homepage

          The thing is, this is already default for NASA. NASA is far more open than ESA. They public domain everything they can, and are much more open about releasing raw data, sooner. ESA is the one that really needs to get past its closed culture.

          I'm not quite getting the point of this "release", since I use a number of pieces of NASA software and have always been able to get what I need. I guess they're just taking down the request forms or something? The real problem IMHO has never been "getting it", it's been "getting it to work". They make some very neat things, but they have such small user bases that they're not well refined, and getting them to work on your platform or finding quality documentation can be a pain.

          • Oh I know - I agree NASA is doing it the right way - my argument is that this should be the default for ALL software produced with ANY tax dollars - whether by a government agency or under a government contract. I would even extend it beyond "software" to "information".

            In other words, I was arguing that the rest of government should copy NASA's policies regarding openness.

            • Oh I know - I agree NASA is doing it the right way - my argument is that this should be the default for ALL software produced with ANY tax dollars - whether by a government agency or under a government contract. I would even extend it beyond "software" to "information".

              In other words, I was arguing that the rest of government should copy NASA's policies regarding openness.

              While I am in general agreement my concern is in some cases it would significantly raise the cost to the government since companies would now have to factor in the loss of rights to the software and thus potential future sales. Years ago I developed some courseware for the government which the agency that contracted it has full rights to its use. Had they said, "We will release it to the public free of charge" my price would have been significantly higher to offset any potential impact on revenue from other

              • Well, in the process where an agency could apply for an exemption to the default rule they could certainly raise it if a supplier made such a claim. At that point they could consider
                1) A different supplier
                2) Developing it in-house instead (if it's cheaper than the revised price)

                or if neither is viable - they may grant an exemption - or a temporary one which says the government will wait at least 5 years to make it public or something.

                • Well, in the process where an agency could apply for an exemption to the default rule they could certainly raise it if a supplier made such a claim. At that point they could consider 1) A different supplier 2) Developing it in-house instead (if it's cheaper than the revised price)

                  or if neither is viable - they may grant an exemption - or a temporary one which says the government will wait at least 5 years to make it public or something.

                  True, but one problem is the procurement process. If it required allowing free public use by default the bids would already incorporate that so government would have no idea what the premium was; and once they open the bidding they have to either take the lowest bid from a qualified bidder or cancel the RFP and start the process all over which is very painful.

                  As for in house development, many agencies do not have the staff to do that and often hire contractors to do the development; which is one way to full

              • by mspohr ( 589790 )

                My experience with software written for the government by contractors is that they charge big bucks for writing the software and fight to keep the copyright so they can sell it again and again even though taxpayers have already paid for it.

            • Oh I know - I agree NASA is doing it the right way - my argument is that this should be the default for ALL software produced with ANY tax dollars - whether by a government agency or under a government contract. I would even extend it beyond "software" to "information".

              In other words, I was arguing that the rest of government should copy NASA's policies regarding openness.

              While I applaud NASA's actions, a quick browse of the catalogue shows a number of the items are for "U.S. Government Purpose Release" which precludes its release to the public, per NASA:

              U.S. Government Purpose Release: This large, but restrictive, release category includes five subcategories. An SUA is required, and appropriate nondisclosure and export control provisions may be included. The following subcategories are included under this release category.

              Beta Release: A limited release of the Software Code

          • by mspohr ( 589790 )

            This is the third release of a catalog of available software... more new bits.

        • by Holi ( 250190 )
          And the point is that he is wrong. Works produced by the government are by law in the public domain.

          "A work of the United States government, as defined by the United States copyright law, is "a work prepared by an officer or employee" of the federal government "as part of that person's official duties." In general, under section 105 of the Copyright Act, such works are not entitled to domestic copyright protection under U.S. law and are therefore in the public domain."
      • Just because something is funded by taxes doesn't mean that it automatically lands in the public domain. Sorry.

        Well, actually, it did once. Back before universities routinely monetized their work and R&D was allowed to do things without guaranteeing a profit by next quarter. And everything the government did was expected to be privatized.

        One of the first RDBMS's was a public domain NASA project (developed by Boeing, I believe).

        Legend has it that Prime Computer was founded when a bunch of engineers at Honeywell got fed up with their employer's apathy towards developing computer systems in-house, took a public-dom

      • by Holi ( 250190 )
        Actually, it does, The government cannot copyright documents it creates for that very reason.
      • You are free to go to the ISS at anytime you wish however you have to get there on your own. Just like Central Park in NYC or the museums in Washington, DC.

    • Re:'Scuze me? (Score:5, Interesting)

      by silentcoder ( 1241496 ) on Friday March 03, 2017 @04:05AM (#53968239)

      Which is, of course, why NASA keeps giving the software away to the public - who did, after all, pay for it. Their contributions to the rest of the economy has been pretty significant. There's hardly a data-center left in the world that doesn't have clusters. Big cloud providers like AWS utterly rely on them for reliability and performance scaling - and their early-use cases like building cheap super-computers for things like climate modeling, aerodynamic engineering or rendering awesome looking animated movies are all alive and well.
      And that all started at NASA with the original Beowulf clusters - a technology idea they subsequently made freely available and became one of the original major growth-points for Linux in science and industry.

    • by piojo ( 995934 )

      You may have helped pay for the development, but publishing is a discretionary expense. Some agencies would say you can have it, but you need to pay for the manpower to get it into a publishable format. ($0.10 copying fee for a friendly and well-organized local government office, much much more for a query made by the FOIA which requires a lengthy search.)

      I haven't actually heard of a super pricey information retrieval fee, but I'd be surprised if it hasn't happened.

  • by Stonefish ( 210962 ) on Friday March 03, 2017 @03:04AM (#53968151)

    I would just like to say thank you, and I hope that other government agencies worldwide contribute equally. Being born when astronauts were taking the first steps towards the moon I have always held NASA in high regard and it is fabulous that they keep impressing many decades later.

  • ...the Autonomous Precision Landing Navigation System might come in handy. It combines camera images with elevation maps using methods “employed by cruise missiles for decades,” although you don’t hear a lot about safe landings by cruise missiles."

    (From the linked article)
    • For a cruise misile "hit the building we were aiming at and not the hospital next door" counts as "safe landing". Sadly even by that definition the US's cruise misiles rarely "land safely". From which I can only conclude that NASA didn't write their software. NASA tends to land things safely far more often than not. They've had a few nice landings on MARS now for example - the ESA's last attempt went kerplatz.

      • As long as ESA and NASA don't collab and some idiot uses imperial units, it should be fine.

        • Oh right... I had forgotten about that little embarrassment until now.

        • by dbIII ( 701233 )

          As long as ESA and NASA don't collab

          Initially they did collaborate on the lander but the NASA people had their funding cut and without NASA involvement the ESA people couldn't use the bits already worked on due to various patent agreements being with NASA.
          Result - splat - kind of expected for a first of it's kind lander instead of being able to build on earlier success.

      • For a cruise misile "hit the building we were aiming at and not the hospital next door" counts as "safe landing". Sadly even by that definition the US's cruise misiles rarely "land safely".

        That's assuming that they weren't aiming at the hospital, which is not a safe assumption.

        Even putting that aside, a drone should have an easier time landing on target than a missile.

  • Easy link (Score:5, Informative)

    by Gravis Zero ( 934156 ) on Friday March 03, 2017 @04:10AM (#53968245)

    You can check out what is publicly/globally available on github: https://github.com/nasa [github.com]

    On their main software page, there is a LOT of stuff that is by request only but github is all the easy to get stuff.

    • I should add that "by request only" doesn't mean just asking. Here's what you agree to even for what is essentially a glorified graphing program:

      "By accessing and using this computer system, you are consenting to system monitoring, including the monitoring of keystrokes. Unauthorized use of, or access to, this computer system may subject you to disciplinary action and criminal prosecution."

      In saner times, I simply would have assumed this means they track keystrokes on their own system, which certainly isn'

  • I remember the first time I had to deal with satellite telemetry. While I had to write code to process the data, I used GNUPlot for visualization. Saved a ton of time. Of course there is no free software. Someone pays for it, to someone donates the time. In government we pay for it, just like we pay for everything. This is why the freedom of information act makes so much sense, and should not be ignored arbitrarily. We pay for the work, and we have a right to know if and how that work is being done.
  • 3d models (Score:5, Informative)

    by Gibgezr ( 2025238 ) on Friday March 03, 2017 @12:26PM (#53970453)

    Their collection of 3D models is nice: https://github.com/nasa/NASA-3... [github.com]

  • by cellocgw ( 617879 ) <cellocgw&gmail,com> on Friday March 03, 2017 @12:46PM (#53970611) Journal

    Is there even ONE slashdotter who's going to comment on the **contents** of the catalog instead of bitching about governments and copyright issues (of which they most likely know very little)?

    I'd be much more interested in reviews/ ratings of software tools for various tasks than in what NASA allegedly is or isn't keeping from the public.

    • I'd guess that the software would be invaluable if one happened to own a Martian rover...

      But most slash dotters just hack web sites for a living.

Life is a whim of several billion cells to be you for a while.

Working...