Validate your experiment plan

Static experiment plans

You can use this form to check your experiment plan's input files for errors (syntax errors, references to non-existent files, attempts to generate boards with non-existence colors or shapes, etc). Just choose the name of your experiment plan in the form below, and click on the "Check" button.

2PG/adve.test_1 2PG/adve.test_2a 2PG/adve.test_2b 2PG/coop.test_1 2PG/coop.test_2 2PG/coop.test_3 2PG/test_adve 2PG/test_coop APP/vm/image_test_01 Aria01 Aria02 FDCL/basic FDCL/basic/tools FDCL/trnsfr_1 FDCL/trnsfr_1/tools MLC/vm/image_test_02 RU/JF/tht/exp1 RU/JF/tht/exp2 RU/JF/tht/exp2_rev1 RU/JF/tht/exp2a RU/JF/tht/exp2a_rev1 RU/JF/tht/exp3 RU/JF/tht/exp4 RU/JF/tht/exp4_rev1 RU/JF/tht/exp4a RU/JF/tht/exp4a_rev1 RU/JF/transfer2 RU/JF/transfer2_patch RU/JF/transfer_sala RU/JF/transfer_sala2 ad/adve.immovable ad/coop.immovable ad/trialFixed all_pilot cpd/relational/relational_1 default ep/rule_ambiguity/ambiguity1 ep/rule_ambiguity/ambiguity1_ns ep/rule_ambiguity/ambiguity2 ep/rule_ambiguity/ambiguity3 ep/rule_ambiguity/ambiguity4 ep/rule_ambiguity/ambiguity5 ep/testing/ambiguity4_testing ep/testing/ambiguity5_testing ep/testing/ambiguity5_testing20 ep/testing/ambiguity5_testing_full_20 ep/testing/ambiguity5_testing_full_9 ep/testing/ambiguity5_testing_full_9_update ep/testing/ambiguity5_testing_full_9_update2 ep/testing/count_testing ep/testing/instruction_toggle ep/testing/instruction_toggle_1 ep/testing/no_stalemate ep/testing/stalemate gary generalize kevin name_disjunc_low_first name_disjunction name_high_first name_low_first name_shape_high_first name_shape_low_first old_default pilot02 pilot03 pilot04 pilot05 pilot06 pk pk/bad_1 pk/cntxt2024JUN25 pk/cntxt2024JUN25/tools pk/colorVshape pk/content_A pk/content_B pk/content_C2 pk/content_D pk/dev2024APR01 pk/dev2024APR19 pk/dev2024JAN04 pk/dev2024JAN14 pk/dev2024MAY27 pk/explore_1 pk/history_A pk/history_B pk/history_C pk/movie pk/object_C pk/pilot_cntxt pk/position_A pk/position_A/one_shape_one_color pk/position_B pk/position_C pk/prod2024JUN15 pk/xcolorVshape pkHomeDir pkSingle qt teaching_all_orders tryPilot04 vm/Rule_PK1 vm/adve.colorVshape vm/colorVshape vm/composite-01 vm/composite-01-super vm/composite-02 vm/composite-03 vm/composite-04 vm/composite-05 vm/cond vm/coop.colorVshape vm/crowded.ccw vm/exp4 vm/gs5-example05 vm/gs5-example06 vm/image_test_01 vm/image_test_02 vm/image_test_03 vm/jigsaw-01 vm/jigsaw-02 vm/jigsaw-03 vm/jigsaw-04 vm/jigsaw-05 vm/pilot06_doubling vm/pilot07_doubling vm/stalemate-01 vm/test-01 vm20201015 vmColorTest vmHomeDir vmPickTest

Dynamic experiment plans

Type the name of a plan, e.g. P:pilot06:max-feedback, R:APP/OCT26/OCT26-1:APP/APP-no-feedback, or R:bottomLeft_then_topRight:simple

Individual rule sets

To test an individual rule set without creating an experiment plan, you can type the text of the rule set in the box below. For example,

1 (*, square, *, *, 0) (*, triangle, *, *,1) (*, circle, *, *,2) (*, square, *, *,3)
(*,*,*,*,[p-1,p+1])

or (for a stalemate example):

(*,*,RED,T,[0,1,2,3])
(*,*,BLUE,R,[0,1,2,3])
(*,*,YELLOW,*,[0,1,2,3])
(*,*,BLACK,*,[0,1,2,3])

or (for another stalemate example):

(color:[red,yellow], pos:T, bucket:[0,1]) (color:[blue,black], pos:B, bucket:[2,3])

(Note: when testing individual rule sets, stalemate testing will only work correctly if your rule set uses the legacy shapes and legacy colors. To test a rule set with custom shapes or custom colors, and for rule sets with image-and-property-based objects, you need to create an experiment plan, so that the tester will know what the set of possible objects is!)