gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] gzz TODO


From: Janne V. Kujala
Subject: [Gzz-commits] gzz TODO
Date: Mon, 03 Mar 2003 15:42:59 -0500

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Janne V. Kujala <address@hidden>        03/03/03 15:42:59

Modified files:
        .              : TODO 

Log message:
        more notes

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/TODO.diff?tr1=1.612&tr2=1.613&r1=text&r2=text

Patches:
Index: gzz/TODO
diff -u gzz/TODO:1.612 gzz/TODO:1.613
--- gzz/TODO:1.612      Mon Mar  3 15:29:48 2003
+++ gzz/TODO    Mon Mar  3 15:42:59 2003
@@ -24,6 +24,13 @@
                - perhaps 16 texts, each read twice by the subject with 
                  randomly assigned conditions?
                - 48 trials could also be just possible
+               - how many texts do we need?
+                       - there's a new version with more texts 
+                         (and a typo fixed) in 
+                         http://himalia.it.jyu.fi/~jvkujala/texts/
+                       - there are 25 texts, but perhaps we should only
+                         use 18 or less of most similar lengths
+                         (see showlen Makefile target)
        - Think about randomization
                - can we have a subject read the same text twice in a row?
                - do we need to enforce the same number of trials for each 
@@ -31,10 +38,10 @@
                  twice by a subject?
                  Or can we trust just on the number of trials, to be
                  approximately non-skewed?
-               - perhaps should first read each of the 16 different texts
-                 and then again, in the same order, (but with different 
-                 permutation of conditions). That way the time between
-                 readings is the same for each text.
+               - perhaps a subject should first read each of the
+                 16 different texts and then again, in the same order, 
+                 (but with a different permutation of conditions). 
+                 That way the time between readings is the same for each text.
         - Create a program that reads lines of the form
            <filename> <min-time> <max-time> <list-of-keys>
           and for each line




reply via email to

[Prev in Thread] Current Thread [Next in Thread]