db: output of open_mst_project or create_mst_project
test_design: data.frame with columns item_id, module_id, item_position
routing_rules: output of mst_rules
test_id: id of the mst test
routing: all or last routing (see details)
Details
In dexterMST we use the following terminology:
test: collection of modules and rules to go from one module to the other. A test must have one starting module
booklet: a specific path through a mst test.
module: a block of items that is always administered together. Each item has a specific position in a module.
routing rules: rules to go from one module to another based on score on the current and possibly previous modules
Additionally, there are two possible types of routing:
all: the routing rules are based on the sum of the current and previous modules
last: the routing rules are based only on the current module
The type of routing must be defined for a test as a whole so it is not possible to mix routing types.
In CML (as opposed to MML) the routing rules are actually used in the calibration so it
is important they are correctly specified. DexterMST includes multiple checks,
both when defining the test and when entering data, to make sure your routing rules are valid and your data conform to them.