Test creation

At this point there wasn't enough time to make flashy graphical test creation tools. The test is created by writing the required test configuration files with a text editor.

The prodecure for creating a test usually like this:

Select test type - What kind of test to run and.
Create test directory - Test directory is used to store the information about the test.
Select sound samples - Decide which sound samples to use in the test and possibly create and/or edit the files and write the sample list configuration file.
Create test items - Define test item parameters, usually which samples are played to the subject. Write the test items file.
Create playlist(s) - Make and write global playlist for all test sessions or session specific playlists.
Select subject's UI - Select which answer and control components to use. Write UI parameters file.
Set test parameters - Write the test configuration file. Set needed parameters such as file names, sequences, timeouts, modes and so on.

Select test type

The first thing is to decide which type of test to use. Select a test from the list of test types.

Also see:

Time limits and warnings - use/don't use limited time for answering, length of time
Sample sequence - sequence type (free/fixed) and fixed sequence
Sample switching - normal or parallel switching

Test directory

A test directory is a directory where the files of a test are kept. It contains the test parameters files and samples (usually in their own subdirectory). The results from test sessions are also written in the current directory (which should be the test directory). Actually using one directory for all files of a test is more of a guideline than a requirement.

When running a test you should first go to the test directory of the test and then run the test (with the RunTest-program).

Sound samples

Decide which sound samples to use for testing. Usually sound samples are kept in a subdirectory in the test directory, for example, make a directory named samples for keeping the samples.

You probably have to edit or create some samples. Here are some requirements (must) or recommendations (should) for samples that are played together during one item:

Samples should be of same length. This is more important if parallel switching is used. Samples are not required to be of same length but would be better if they are. The system will happily play samples with different lengths at the same time.
The phase of the samples should be the same, that is, there is no extra delay in the beginning of one sample that is not in the second sample. This is more important of parallel switching is used.

These apply to all samples in a test:

All samples in test's sample set must have the same sample rate and must match the sample rate of the player.
All samples must have the same number of channels.
Samples should be calibrated, for example, the level of all samples should be the same. The sample list below provides a way to calibrate the level of samples without editing the actual sample file.
Samples' format must be one of valid audio file formats accepted by the player. It would be better if they are uncompressed. AIFF/AIFF-C would be a good choice.

Tools for audio files include: dmconvert, mediaconvert, sfconvert, dminfo, sfinfo, soundeditor, soundtrack. See the manual pages for description and/or the Digital Media Tools Guide (IRIS InSight book).

The sample list relates the sample IDs the test items use to the actual audio samples. The information about a sample contains at least the sample ID and the file name of the audio file. Depending on the type of sample, additional information may be also stored.

More detailed information: Format of the samplelist file

Test items

Write the test items. See test types and test items for needed parameters.

Playlists

Playlists are files that tell which test items (possibly a subset of all test items) to play to the test subject and in which order. A playlist can be 'global playlist' which means that the same order of items is used in all sessions and for all subjects unless a 'session specific playlist' is used to set a specific playlist for a specific session. The playlist(s) are stored in the test's directory.

More detailed information: Format of the playlist

Subject's user interface

No complete documents for subject UI components are not yet ready. Copy and modify the demo example files. They are quite self-explatory.

Test parameters

Write the test parameters file. Add parameters mentioned earlier:

Time limits and warnings - use/don't use limited time for answering, length of time
Sample sequence - sequence type (free/fixed) and fixed sequence
Sample switching - normal or parallel switching
MCLL setting - parameters for setting the most comfortable listening level, fixed or subject sets it.
See also common properties - other common, additional, required parameters for a test.

· Tests index · Document index ·

Last modified: Tue Jul 21 10:01:09 EEST 1998