Skip to content

robwink/davinci_fork

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

davinci_fork

Build Status

This is an unaffiliated, unsupported fork of davinci.asu.edu.

It has dozens of bug fixes and 100's of warning fixes (hard to believe because there are still so many in this terrible ancient monstrosity of a project). It also has many additional features, including all the missing types (int8, uint16, uint32, uint64 and int64) and most noticably and helpfully, tab completion.

So if you run into a problem with the official Davinci, feel free to try downloading and building this version to see if it works better for you. I wouldn't be surprised if it does, given that in the time since I left MSFF (Nov. 2016) and they reverted all the work I did, they've barely had a few dozen commits, and some of those were just reapplying (or worse reimplementing) a fraction of what I had already done. Most of the fixes and almost all of the improvements never got reapplied in the "official" repo. See the revision history of the svn repo vs the history of this one to see what I'm talking about.

Personally, I think davinci should have been retired well over a decade ago and replaced with Python. Any functionality isn't readily available in Python or various librares (numpy, scipy, plotting libs etc.) could easily be added as C modules adapted from davinci code if performance is an issue, or rewritten in python. The davinci standard library would likewise be rewritten in python. Aside from how terribly it's implemented and organized, davinci is a terrible language so that would be a huge plus for davinci users. Not to mention python is used everywhere now, esp. academia, so they probably already know it and can now more efficiently/effectively share with other scientists. Also it'd be far cheaper and easier to maintain a "davinci" python library than an entire separate language. Anaconda is probably a good start.

Compiling

Davinci requries a C99 compliant compiler. A configuration script has been included to make compilation as straight forward as possible. In most instances you should be able to run configure, and then run make:

% ./configure
% make
% make install

If that doesn't work check the wiki page for OS specific details. It may help, but remember that version may have diverged enough that it may be wrong

Documentation

Documentation can be found on the wiki at davinci.asu.edu however the same caveats as above. This versions has functions that may not be there, or if they are there, there may be more functionality than is documented or work slightly differently.

You're better off using the file dv.gih, which is distributed with davinci and can be accessed from within the interpreter, documents all the functions as they are in this codebase.

About

Fork of ASU Mars Space Flight Facility's Davinci software (davinci.asu.edu)

Resources

License

GPL-2.0 and 3 other licenses found

Licenses found

GPL-2.0
LICENSE
Unknown
COPYING
Unknown
LICENSE.Xvic
LGPL-2.1
LICENSE_libcsv

Stars

Watchers

Forks

Packages

No packages published