Stimuli/ Triggers/ Timing difficulties

Douglas rayhaneh.rahgoshai at gmail.com
Tue May 8 18:38:28 UTC 2012


Dear Mr. McFarlane,

Thanks a lot for your reply, time and effort.
With all my respect and appreciation:

1-...
Chapter 4 "Using E-Basic" wasn't useful much. As the things I had
forgotten wasn't related to our experiment much.

2-...
As for PST's latest statements at their knowledge Base;
4026: I know the facts about windows 7 and E-Prime. I got familiar to
them while trying to install it on my computer. But I have heard "non-
promising" things from other researcher and I just wanted to see if
others have same sad experiences or not.

4347: As we don't have sound files in our experiment, I don't think
this one is related to our experiment. Although we have disabled an
option due to sound in the process! What I don't know is if we have
Start up  Latency for images and let's say that's what causes problems
for us why it differ from image to image with exact same sizes. And I
didnt get his part and how it can effect our experiment:

In Windows Vista and Windows 7 (and beyond), the DirectSound API no
longer is a thin layer between E-Prime (or any application) and the
sound hardware, but instead sits on another management layer.
This results in poor performance on the same hardware where lower
latency was achieved on the same hardware using Windows XP. Typically
these results average in the 30ms range for startup.
Therefore, PST does not recommend paradigms requring startup latency
values of less than 30ms under Windows Vista or Windows 7 for E-Prime
1.0, E-Prime 1.1, or E-Prime 1.2.

3-...
Context.SetAttrib or Con.SetAttrib doesn't match our needs, goals or
expectations if I got it right!

4-...
About StartTime and OnsetTime, I remember what you said and what I
looked for was:
OnsetTime>>Timestamp at which the object begins its critical action
(e.g., drawing to the screen).
StartTime>> Timestamp at which execution for the object began
(i.e.,time at which the Run method began to execute).

So, I guess logically OnsetTime should come before StartTime... That's
why I don't get this:
		Stimulus.OnsetTime: 33523
        	Stimulus.PreRelease: 400
		Stimulus.Duration: 489
		Stimulus.StartTime: 32948

But this is what PST Technical Consultant Told me:
 "OnsetTime represents the time the object was actually presented.
StartTime can occur before    OnsetTime and should not be used for
measurements."

Now, if we have a huge difference between Stimulus StartTime and
Stimulus OnsetTime, there should be such difference between Trigger
StartTime and Trigger OnsetTime, IF such thing exists at all! And If
it does exist, Which one are we measuring?!

5-...
It is already done.

6-..
I didn't see any replies for that. This is our major concern now.

7-...
I am discussing this matter with them at the same time.

You are right, The world does not hinge on our research but believe it
or not, we are(sort of!)!

So, still, if anyone wishes to help... we are open to suggestions.

With best wishes at what ever you are working on

-- 
You received this message because you are subscribed to the Google Groups "E-Prime" group.
To post to this group, send email to e-prime at googlegroups.com.
To unsubscribe from this group, send email to e-prime+unsubscribe at googlegroups.com.
For more options, visit this group at http://groups.google.com/group/e-prime?hl=en.



More information about the Eprime mailing list