summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorbnewbold <bnewbold@eta.mit.edu>2009-04-19 11:38:15 -0400
committerbnewbold <bnewbold@eta.mit.edu>2009-04-19 11:38:15 -0400
commitccbf7c652dae401bb224f3a92a897b711f09f8bb (patch)
tree59a3d2e798dd9be4f10f35feb1ce5d184e1c1fab
parentc54cc85c0f5fa98c9c675b001de5a03d5ffe5000 (diff)
download6.945-ccbf7c652dae401bb224f3a92a897b711f09f8bb.tar.gz
6.945-ccbf7c652dae401bb224f3a92a897b711f09f8bb.zip
blah
-rw-r--r--final_project/proposal/stub30
1 files changed, 30 insertions, 0 deletions
diff --git a/final_project/proposal/stub b/final_project/proposal/stub
new file mode 100644
index 0000000..8df985e
--- /dev/null
+++ b/final_project/proposal/stub
@@ -0,0 +1,30 @@
+
+Title: Interactive Interface for Numeric and Symbolic Math and Physics
+
+Group: Bryan Newbold and Laura Harris
+
+Our system will be a generic user interface for visualization and exploration
+of mathematical procedures and objects. The intent is to generate a user
+interface from a set of interaction widgets and visualization methods
+appropriate to any supplied procedure or expression. For example, a list or
+vector of value pairs would be plotted in two dimensions and have statistical
+properties calculated on demand. An n-artity procedure returning a tuple of
+values could be numerically evaluated for a given set of inputs, have it's
+symbolic derivatives returned, etc. The unique aspect is that the user would
+not have to specify the context of interaction for each object, a single
+generic 'explore' procedure will determine and generate the appropriate
+interface and handle computations in parallel (aka seperate process threading
+for interface and computation, with possible compilation).
+
+The user interface will include a command line REPL interface for debugging
+and either a GTK GUI or web interface.
+
+Features that will be interesting to implement will be:
+
+ * Halting and restarting of evaluation with continuations
+ * Determination of the algebraic properties of functions
+
+Bryan will be responsible for backend components and evaluation control
+structures while Laura will be responsible for the generic front end interface
+and interaction control.
+