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:29:48 -0500

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

Modified files:
        .              : TODO 

Log message:
        exper notes

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

Patches:
Index: gzz/TODO
diff -u gzz/TODO:1.611 gzz/TODO:1.612
--- gzz/TODO:1.611      Mon Mar  3 14:07:42 2003
+++ gzz/TODO    Mon Mar  3 15:29:48 2003
@@ -19,13 +19,22 @@
     tjl:
        - Find good set of parameters (number of texts, zooms, blend factor, 
etc.)
          (blend factor is "blend" in the script and CONST0.a in 
pagespanpaper.py)
-        - Perhaps 18 texts, each read twice by the subject with randomly 
assigned
-         conditions?
+       - What trials to use?
+               - 16 conditions so there should be a multiple of 16 trials
+               - perhaps 16 texts, each read twice by the subject with 
+                 randomly assigned conditions?
+               - 48 trials could also be just possible
        - 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 
ordered 
-                 condition pair corresponding to a text read twice by a 
subject?
-                 Or can we trust on number of trials to be approximately 
non-skewed?
+               - do we need to enforce the same number of trials for each 
+                 ordered condition pair corresponding to a text read 
+                 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.
         - 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]