Architecture » History » Version 3

Version 2 (Jeremy Gow, 2013-04-04 12:39 PM) → Version 3/5 (Marcus Pearce, 2014-05-09 07:55 PM)

h1. Architecture

h2. Directory Structure

The layout of the code is as follows:

* README
* COPYING
* thesis.pdf
*
idyom.asd: the system definition
* utils/: general-purpose utilities
* database/: a database amuse/: an interface for storing symbolically encoded to amuse music
** package.lisp
** generics.lisp
** music-data.lisp
** examples/
** data-import/: modules for importing
data from different formats to the database interface
** data-export/: modules for exporting data from the database amuse-interface.lisp: look here to different formats
* events/: a representation system for music objects that sits
make this less dependent on top of the database amuse-mtp
** package.lisp
** extended-sequence.lisp
** events.lisp
* viewpoints/: viewpoint representations and functionality
**
viewpoint-extensions.lisp: extensions to the viewpoint framework useful for modelling
* ppm-star/: ppm/: the PPM* implementation
** package.lisp
** generics.lisp
** ppm-star.lisp
** ppm-io.lisp
** ppm-ui.lisp
* mvs/: the
multiple-viewpoint system modelling framework
** params.lisp: user-level parameters to the statistical modelling
** multiple-viewpoint-system.lisp: modelling with multiple-viewpoints
** prediction-sets.lisp: representing and combining distributions, computing entropy and information content
* apps/: top-level applications for users
** package.lisp
**
apps.lisp: pathnames and filenames for saving data and results
** main.lisp: top-level code for using the system
** resampling.lisp: the main user interface - estimating information content by cross-validation
** viewpoint-selection.lisp: on tin does it says the what
** generation.lisp: code for generating melodies (possibly suffering slightly from bitrot)