From 287bd927f9679a2460cee7cde25e89abebcb2c5e Mon Sep 17 00:00:00 2001
From: AJ Rossini <blindglobe@gmail.com>
Date: Sun, 19 Apr 2009 09:13:11 +0200
Subject: [PATCH] old cybertyggyr example which was not so good.

Signed-off-by: AJ Rossini <blindglobe@gmail.com>
---
 src/data/dsv-examples.lisp | 92 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 92 insertions(+)
 create mode 100644 src/data/dsv-examples.lisp

diff --git a/src/data/dsv-examples.lisp b/src/data/dsv-examples.lisp
new file mode 100644
index 0000000..908dd77
--- /dev/null
+++ b/src/data/dsv-examples.lisp
@@ -0,0 +1,92 @@
+
+(progn ;; FIXME: read data from CSV file.  To do.
+
+  
+  ;; challenge is to ensure that we get mixed arrays when we want them,
+  ;; and single-type (simple) arrays in other cases.
+
+
+  (defparameter *csv-num*
+    (cybertiggyr-dsv::load-escaped
+     #p"/media/disk/Desktop/sandbox/CLS.git/Data/example-numeric.csv"
+     :field-separator #\,
+     :trace T))
+
+  (nth 0 (nth 0 *csv-num*))
+
+  (defparameter *csv-num*
+    (cybertiggyr-dsv::load-escaped
+     #p"/media/disk/Desktop/sandbox/CLS.git/Data/example-numeric2.dsv"
+     :field-separator #\:))
+
+  (nth 0 (nth 0 *csv-num*))
+
+
+  ;; The handling of these types should be compariable to what we do for
+  ;; matrices, but without the numerical processing.  i.e. mref, bind2,
+  ;; make-dataframe, and the class structure should be similar. 
+  
+  ;; With numerical data, there should be a straightforward mapping from
+  ;; the data.frame to a matrix.   With categorical data (including
+  ;; dense categories such as doc-strings, as well as sparse categories
+  ;; such as binary data), we need to include metadata about ordering,
+  ;; coding, and such.  So the structures should probably consider 
+
+  ;; Using the CSV file:
+
+  (defun parse-number (s)
+    (let* ((*read-eval* nil)
+	   (n (read-from-string s)))
+      (if (numberp n) n)))
+
+  (parse-number "34")
+  (parse-number "34 ")
+  (parse-number " 34")
+  (parse-number " 34 ")
+
+  (+  (parse-number "3.4") 3)
+  (parse-number "3.4 ")
+  (parse-number " 3.4")
+  (+  (parse-number " 3.4 ") 3)
+
+  (parse-number "a")
+
+  ;; (coerce "2.3" 'number)  => ERROR
+  ;; (coerce "2" 'float)  => ERROR
+  
+  (defparameter *csv-num*
+    (cybertiggyr-dsv::load-escaped
+     #p"/media/disk/Desktop/sandbox/CLS.git/Data/example-numeric.csv"
+     :field-separator #\,
+     :filter #'parse-number
+     :trace T))
+
+  (nth 0 (nth 0 *csv-num*))
+
+  (defparameter *csv-num*
+    (cybertiggyr-dsv::load-escaped
+     #p"/media/disk/Desktop/sandbox/CLS.git/Data/example-numeric2.dsv"
+     :field-separator #\:
+     :filter #'parse-number))
+
+  (nth 0 (nth 0 *csv-num*))
+  
+  ;; now we've got the DSV code in the codebase, auto-loaded I hope:
+  cybertiggyr-dsv:*field-separator*
+  (defparameter *example-numeric.csv* 
+    (cybertiggyr-dsv:load-escaped "Data/example-numeric.csv"
+				  :field-separator #\,))
+  *example-numeric.csv*
+
+  ;; the following fails because we've got a bit of string conversion
+  ;; to do.   2 thoughts: #1 modify dsv package, but mucking with
+  ;; encapsulation.  #2 add a coercion tool (better, but potentially
+  ;; inefficient).
+  #+nil(coerce  (nth 3 (nth 3 *example-numeric.csv*)) 'double-float)
+
+  ;; cases, simple to not so
+  (defparameter *test-string1* "1.2")
+  (defparameter *test-string2* " 1.2")
+  (defparameter *test-string3* " 1.2 ")
+  )
+
-- 
2.11.4.GIT