Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Images with delay don't appear
#1
Dear FindingFive Team, 
I've set up a central coherence task which has 16 different image stimuli, all in png format. In addition to these stimuli I also have a fixation cross, however the fixation cross I made with FindingFive coding. Unfortunately when I pilot the study only the fixation cross appears on the screen, not the images. 
It could be that this issue is stemming from the delay function I have set-up within the stimuli themselves. There are 16 stimuli but each has 5 different versions (5 different delays) as I wanted to create a 'jitter' between stimulus presentations. To create this jitter I followed options 1 and 2 outlined by Noah on a previous thread (https://discuss.findingfive.com/showthre...ight=delay) but I can't identify what I've done wrong.
Could a member of your team look into this for me?
Cheers, 
Mary-Kate
Reply
#2
Hi again Mary-Kate!
We'd be happy to look into it, but first you'll need to add [email protected] if you haven't already. And, in the meantime, some things that you can look into to see if you can diagnose the problem yourself:
  1. The barrier property on stimuli
  2. Delay and duration properties on stimuli
  3. Delay and duration properties on trial templates (especially if duration is timing the trials out early)
  4. Whether you have any background responses with duration properties that could be triggering the end of the trial early
Off the top of my head, those are the culprits I'd look to first.
We will be in touch soon!
Noah Nelson
VP of Product @ FindingFive
Reply
#3
Hi again Mary-Kate,
By any chance, is "C01_backgroundmeasures" one of the studies causing trouble? Looking at the images in that study, I see delays of over 1000 seconds, which is probably longer than your trials are lasting. Perhaps you are inputting the values in milliseconds by mistake? FindingFive timing properties (such as duration and delay) are always represented in seconds, but decimals are supported. So, for example, 1150 ms would be 1.15. Perhaps this is the culprit?
Best,
Noah Nelson
VP of Product @ FindingFive
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)