Code.NASA

http://code.nasa.gov/project/

by mjwhansen • 12 years ago

79 12 12 years ago

code.nasa.gov

mjfl• 12 years ago

This is really cool. Never understood the seemingly traditional java practice of making super-deep source directories (gov.nasa.arc.spife.core.plan/src/gov/nasa/arc/spife/core/plan/timeline/ with nothing else in the intermediate folders)

jvilk3• 12 years ago

It is supposed to provide a unique identifier for all packages in all applications, allowing you to mix code from multiple packages without namespace collisions.

From http://docs.oracle.com/javase/specs/jls/se5.0/html/packages.... :

The suggested convention for generating unique package names is merely a way to piggyback a package naming convention on top of an existing, widely known unique name registry instead of having to create a separate registry for package names.

makmanalp2• 12 years ago

That explains the url package names, but not the layers upon layers of folders. I think that might come from the way java forces you to do modules.

NamTaf• 12 years ago

Hey this is cool, thanks! I'm going to dig in to their surface crack tool and see what they consider for it. It could be very useful in my line of work.

I'd love to see them put up more code for simulation and analysis of mechanical systems.

edit: Holy crap, I'm flicking through the Tech Transfer Software Catalogue and there's a heap of cool mechanical engineer stuff in here. I wish more of it were available in the academic and/or commercial realm (particularly outside the US)!

seanherron2• 12 years ago

It's awesome to see this posted - I was (one of) the original creators of code.nasa.gov when we first launched it in early 2012. I've since moved on from NASA, but the agency has kept on posting things to the site as well as on GitHub (https://github.com/nasa). So glad to see the torch continue to burn.

There's a big effort within the federal government to do more around engaging citizens in using (and contributing to) free/open source software, as well as starting to develop more user-centered products and services. If you're interested in that sort of thing, check out 18F (https://18f.gsa.gov and https://github.com/18F). We'd love to hear from you.

novas0x2a• 12 years ago

Do you still have any contacts there? I'm one of the (former) developers of vision workbench, and it's kind of a shame that code.nasa links to a fork that's almost 3 years behind (https://github.com/nasa/visionworkbench), rather than upstream (https://github.com/visionworkbench/visionworkbench). It gives the impression that it's a dead project :/

seanherron2• 12 years ago

Sent you an email - a few folks over there should be able to help you out!

elwell• 12 years ago

Second project should be a Library for rigorous verification of non-linear arithmetic, but was empty, save for a readme and license: https://github.com/nasa/Kodiak

Or, is that a punny statement about non-linear arithmetic?

Code.NASA

Related Stories