Common Lisp Statistics -- based on LispStat (Tierney) but updated for Common Lisp and incorporating lessons from R (http://www.r-project.org/). See the google group for lisp stat / common lisp statistics for a mailing list.
Fetching latest commit…
Cannot retrieve the latest commit at this time
|Makefile||Ignore local ASDF files to allow for custom setups, add make target t…|
|test-style.css||updated LIFT unit test structure, fixed rename errors.|
-*- mode: text -*- For a fast start: You probably did: git clone git://repo.or.cz/CLS.git (or perhaps: git clone http://repo.or.cz/w/CLS.git ) and now you should: git submodules init git submodules update to get the whole package. Make the shared library liblispstat with an ANSI C compiler (only gcc tested at this point): cd lib make run a common lisp (SBCL, CMUCL, CLISP, CLOZURE-CL) starting in the current directory. Recent versions of CFFI and LIFT can be found in the external/ subdirectory, and should be autoload-able, assuming that you are using a Lisp implementation supporting ASDF. (AJR-FIXME: need to upload my GIT mirrors to repo.or.cz or similar, and have them potentially available as submodules if needed) (on Debian or similar systems: can use CLC (Common Lisp Controller) or SBCL approaches, i.e. ~/.clc/systems or ~/.sbcl/systems should contain softlinks to the lispstat, cffi, and lift ASDF files (i.e. lispstat.asd, cffi.asd, and lift.asd). AJR-FIXME: There is probably a similar incantation for other CL's, need to record that here!). Step through ls-demo.lisp for a range of examples of activities. So basically .. 1. change directory into the CommonLispStat working directory. 2. start your lisp 3. follow the commands in the ls-demo.lisp file, i.e. 0. (asdf:oos 'asdf:load-op 'lift) ;; Still need this, not sure why? a. (asdf:oos 'asdf:load-op 'lispstat) ;; use ASDF to load lispstat b. (in-package :ls-user) c. (normal-rand 20) d. (setf mytest (normal-rand 20)) e. ... (and so on) ... and see if they work (basic CFFI functionality for external C library, LIFT package for unit-testing framework to ensure run time stability). 4. Tell me ( mailto:email@example.com ) if there is any thing wrong (or if anything happens to work. CMUCL and SBCL seem to work just fine at this stage. CLISP is finicky regarding the problems that we have with CFFI conversation. In particular that we can not really do typing that we need to take care of. I think this is my problem, not someone elses. Need to test ECL. Clozure-CL seems to somewhat work. =========== See Doc/README* for history and design considerations See Doc/INSTALL for getting this to work and run =========== Working on this with git: git clone git://repo.or.cz/CommonLispStat.git cd CommonLispStat.git git submodules init git submodules update will pull the whole repository, and create a "master" branch to work on. If you are making edits, Probably, you don't want to use the master branch, but more to use a topic-centric branch, so you might: git checkout -b myTopicBranch and then work on myTopicBranch, pulling back to the master branch when needed by git checkout master git pull . myTopicBranch (or git rebase myTopicBranch ) of course, perhaps you want to contribute to the mob branch. For that, after cloning the repository as above, you would: git checkout -b mob remotes/origin/mob (work, work, work... through a cycle of <edit> git add <files just edited> git commit -m "what I just did" ad-nauseum. When ready to commit, then just: git push git+ssh://firstname.lastname@example.org/srv/git/CommonLispStat.git mob:mob ) and it'll be put on the mob branch, as a proposal for merging. Another approach would be to pull from the topic branch into the mob branch before uploading. Will work on a formal example soon. (the basic principle is that instead of the edit cycle on mob, do something like: git checkout mob git pull . myTopicBranch git push git+ssh://email@example.com/srv/git/CommonLispStat.git mob:mob )