[open] advanced delay behaves different in 0.26 and 0.27.3

Jarik

The program at the bottom of this post gives somewhat strange debug output in OpenSesame 0.27.3

It's an advanced-delay object (duration "1500" jitter "500" mode "Uniform") in a loop repeated 10 times. The delay is printed to the debug window by the inline_script. I expect delays around 1500 with a minimum of 1500-500=1000 and a maximum of 1500+500=2000. But 0.27.3 gives the following output:

788
1624
2203
1541
1307
2641
1195
1773
1461
1451

0.26 gives the output I expected:

1572
1368
1360
1292
1550
1345
1404
1689
1719
1361

# Generated by OpenSesame 0.26 (Earnest Einstein)
# Tue Aug 20 16:34:26 2013 (nt)
# 
# Copyright Sebastiaan Mathot (2010-2011)
# <http://www.cogsci.nl>
# 
set foreground "white"
set subject_parity "even"
set description "Default description"
set title "New experiment"
set sampler_backend "legacy"
set coordinates "relative"
set height "768"
set mouse_backend "legacy"
set width "1024"
set compensation "0"
set keyboard_backend "legacy"
set background "black"
set subject_nr "0"
set canvas_backend "legacy"
set start "experiment"
set synth_backend "legacy"

define inline_script inline_script
    set _run "print self.get('delay_advanced_delay')"
    set _prepare ""
    set description "Executes Python code"

define sequence experiment
    run loop "always"

define advanced_delay advanced_delay
    set duration "1500"
    set jitter "500"
    set description "Waits for a specified duration"
    set jitter_mode "Uniform"

define loop loop
    set repeat "1"
    set description "Repeatedly runs another item"
    set skip "0"
    set offset "no"
    set item "sequence"
    set column_order ""
    set cycles "10"
    set order "random"
    run sequence

define sequence sequence
    set flush_keyboard "yes"
    set description "Runs a number of items in sequence"
    run advanced_delay "always"
    run inline_script "always"

sebastiaan

Hi Jarik,

Thanks for spotting this one. What happens is that the plug-in always uses a Gaussian jitter, even if you select a Uniform jitter. I filed an issue on this (link). As a workaround for now, you could use an inline script to implement a uniform-jitter delay.

Cheers!
Sebastiaan