Back
Login
Register
Login
Register
Millisecond Forums
Home
»
Millisecond Forums
»
Inquisit 4
»
RE: trial.elapsedtime not always 100% accurate?
trial.elapsedtime not always 100% accurate?
Post Reply
Like
40
trial.elapsedtime not always 100% accurate?
View
Flat Ascending
Flat Descending
Threaded
Options
Subscribe to topic
Print This Topic
RSS Feed
Goto Topics Forum
Author
Message
DCole9
DCole9
posted 10 Years Ago
ANSWER
Topic Details
Share Topic
Group: Forum Members
Posts: 42,
Visits: 220
Hey Inquisitmen,
I noticed some behavior in my logfile where a trial was not branching properly to an Incorrect Feedback trial upon timeout. Is there a more elegant way to do this? and does the trial.elapsedtime element not always work 100% accurately (if I have many branch/ontrialend/etc. elements in the trial)?
Here is my sample code that doesn't always return feedback
<trial patchtrial>
/timeout 5000
/branch = [if (trial.patchtrial.elapsedtime > 4999) trial.wrongfeedback]
... (lots of other branch conditions a long ontrialend)
</trial>
Reply
Like
40
Dave
Dave
posted 10 Years Ago
ANSWER
Post Details
Share Post
Group: Administrators
Posts: 13K,
Visits: 108K
/ branch = [if (trial.patchtrial.response == 0) ...]
If a trial times out (cf. the /timeout attribute), it must mean no (valid) response has been submitted.
Reply
Like
46
DCole9
DCole9
posted 10 Years Ago
ANSWER
Post Details
Share Post
Group: Forum Members
Posts: 42,
Visits: 220
Nice fix Dave. I was trying to find a noresponse attribute--- this makes sense now that you mention it ;)
Thanks!
Reply
Like
39
GO
Merge Selected
Merge into selected topic...
Merge into merge target...
Merge into a specific topic ID...
Open Merge
Post Reply
Like
40
Post Quoted Reply
Reading This Topic
Login
Login
Remember Me
Reset Password
Resend Validation Email
Login
Facebook
Explore
Messages
Mentions
Search