(Not) Understanding edat time variable(s)

29 views
Skip to first unread message

Jason

unread,
Sep 3, 2010, 11:39:12 AM9/3/10
to E-Prime
Greetings,

In my edat file there are several time related variables with values
that vex me. For example, the variable 'RunTime' = 14:45:07, which I
understand. However the variable 'RunStartTime' = 162726 completely
vexes me. Any insight into this would be greatly appreciated.

Best regards,
Jason

David McFarlane

unread,
Sep 3, 2010, 11:46:12 AM9/3/10
to e-p...@googlegroups.com
Jason,

I have a *lot* of experience with EP and .edat files, and I do not
recognize these as standard attributes that would be added
automatically. Therefore, they must have been added by whoever made
your specific EP program, and you have to ask that person. No one
here will be able to help you, sorry.

-- David McFarlane, Professional Faultfinder

Jason

unread,
Sep 3, 2010, 12:42:05 PM9/3/10
to E-Prime
David,

Thanks for the quick response and "unfortunate" information about the
variables. As this paradigm will be used for fMRI research, perhaps
these are variables declared by IFIS. Regardless, more legwork is
needed.

Cheers,
Jason

David McFarlane

unread,
Sep 3, 2010, 1:15:14 PM9/3/10
to e-p...@googlegroups.com
Jason,

Ah, IFIS! You didn't say that at the start, in that case all bets
are off! We used IFIS for many years and finally abondoned it a few
years back for our own custom setup, what a relief! I can't believe
anyone still uses that outmoded system. IFIS is a mess, it forces a
draconian task structure using several PackageCalls, it adds all
sorts of attributes and overrides your E-Prime settings with settings
that it hides in several Lists in Unreferenced E-Objects without
explanation, and generally completely violates the well-designed task
representation already provided by the designers of E-Prime. And it
requires two computers for no good reason, and requires leaving a
wide open network share, what an invitation for hackers! And the
documentation is even worse than that for E-Prime, I had to work out
all the principles and "gotchas" myself and distilled it down to a
three-page writeup that explained more than their entire sorry excuse
for a manual. Don't get me started! I feel sorry for you.

-- David McFarlane, Professional Faultfinder

Jason Craggs

unread,
Sep 3, 2010, 2:02:40 PM9/3/10
to e-p...@googlegroups.com
David,

Yes, I've apparently waded into a quagmire, one successfully avoided for years... While I am grateful for your response, learning that you've never come across such a variable given your experiences with IFIS is not great news. That said however, you wouldn't happen to have a copy of that "documentation" that you'd be willing to "share" would you?

Cheers,
Jason

 

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


David McFarlane

unread,
Sep 3, 2010, 2:21:20 PM9/3/10
to e-p...@googlegroups.com
Jason,

Oops, let's clarify that for the record -- I never said that I never
came across such "variables" (the correct term is "attribute",
variables are something very different and we must not get them mixed
up) in IFIS, I only said that I had never come across such attributes
in standard E-Prime .edat files. Those attributes may very well be a
standard part of IFIS, but my memory of IFIS is so painful that I do
not care to recall such details. It would make more sense to re-post
this thread as "(Not) Understanding IFIS time attribute(s)".

As to my little writeup, well, I might just dredge that up and send
it to you separately, as long as you promise not to ask me any
further questions about it. But that will have to wait -- it's 2:15p
here in the Easter Time Zone of the USA, I have not had lunch, I have
been officially off duty since 1p, I am sitll facing a flurry and
backlog of e-mail, and I have tons of other work to take care of for
others. So you will understand if I treat this as low
priority. Maybe some time after the weekend. In the meantime, see
what you can make of the IFIS documentation yourself.

Regards,


-- David McFarlane, Professional Faultfinder

Reply all
Reply to author
Forward
0 new messages