Log Data - Error 10 & 86.

David McFarlane mcfarla9 at msu.edu
Wed Apr 18 15:18:48 UTC 2012 

Bo,

BlockProc *is* a Procedure.  When you disabled Log Data for BlockProc, 
you disabled logging for that entire Procedure.  Hope that clarifies 
matters.

Your best option is actually #4, upgrade to EP2.0.10.182 where it 
includes facilities to disable logging of individual Context attributes. 
  Otherwise, I think your best option is #0, just log everything and 
deal with it later in the .edat file.  In fact, if you get proper 
training in the use of E-DataAid, you will see how to use E-DataAid to 
filter out extraneous columns and focus on data of interest.  I include 
a lesson on this in my online course.

Regards,
-----
David McFarlane
E-Prime training online: 
http://psychology.msu.edu/Workshops_Courses/eprime.aspx
Twitter:  @EPrimeMaster (twitter.com/EPrimeMaster)


Bo Arleth wrote:
> Thank you both for the replys and the claryfication
> I will try your #2 option, when I get the chance. It might work, but
> I'm not sure, how you turn off logging for the entire procedure.
> Maybe you could clarify this? I'm talking about BlockProc.
> Otherwise option #3 is the best solution. But this requires a bit more
> coding on my part, and knowledge about the commands.
> Is it possible, that one of you have an experiment, where the code for
> logging is included, that I could have for reference?
> 
> Kind Regards
> Bo
> 
> On 17 Apr., 17:29, Susan Campbell <susan... at gmail.com> wrote:
>> Hi David,
>>
>> Oh, good point on #1. I had to check for myself, because it's actually
>> pretty unexpected behavior -- even if you have a list attribute, and you
>> tell it not to log, it will still log it if you change the value in your
>> code. Learn something new every day.
>>
>> You're absolutely right about #2, of course, though I guess I assumed that
>> since the OP referred to feedback that it was just the tail end of the
>> procedure. (It looks like the c.Log at the end of the procedure is all that
>> "turning logging off" affects anyway. Hm.)
>>
>> I vote #3 is the one that actually solves the OP's problem -- E-Prime data
>> files aren't, by their nature, streamlined. They're bloated with (what's
>> usually) extra stuff so it's easy to go back and check that things went the
>> way you expected.
>>
>> (I might say something else on the forum post, but forum verification
>> emails appear to be hosed.)
>>
>> Thanks for the clarifications!
>> Susan
>>
>>
>>
>>
>>
>>
>>
>> On Tuesday, April 17, 2012 10:38:52 AM UTC-4, McFarlane, David wrote:
>>
>>> Susan,
>>> Thanks for weighing in.  Just a few clarifiers, in reverse order...
>>> Your #3, done with care, clearly will accomplish whatever you program it
>>> to do.
>>> #2 is clever, and might work if applied with finesse -- one would
>>> disable Log Data for the whole Procedure, then apply c.Log *before*
>>> running any c.SetAttrib commands.  A problem arises, however, if
>>> later in the Procdure you have additional data to log, e.g., a
>>> subject response.  Then you would have to run c.Log again, and at
>>> that time it would log all of the attributes defined by the earlier
>>> c.SetAttrib commands.  Until EP2.0.10.182, there was absolutely no
>>> way around that.
>>> #1 would indeed work for ordinary List attributes, but does not quite
>>> apply to Bo's case, because he is using Context attributes in inline
>>> statements (i.e., c.SetAttrib commands).  Up until EP2.0.10.182, EP
>>> provided no way to disable logging of Context attributes -- I know,
>>> because I asked PST about this (sorry, I can't find a link for that
>>> right now).  But as I have posted here, EP2.0.10.182 now provides a
>>> way to disable logging of individual Context attributes.
>>> Thanks for contributing,
>>> -- David McFarlane
>>> At 4/17/2012 10:17 AM Tuesday, you wrote:
>>>> Hi Bo,
>>>> I agree with David that there isn't any way (that I've ever heard
>>>> of, anyway) to turn logging off for just an InLine -- whatever you
>>>> actually type in an InLine just goes directly into the script.
>>>> I can think of three ways you could try to deal with the problem you
>>>> describe, off the top of my head:
>>>> 1. Turn off logging for particular attributes (columns in your list,
>>>> done in the list view).
>>>> 2. Log the data before you turn logging off, by using a c.Log
>>>> command or something.
>>>> 3. Create your own data file that only has the stuff you want and
>>>> ignore the default E-Prime data file.
>>>> HTH,
>>>> Susan
>>>> On Tuesday, April 17, 2012 9:55:46 AM UTC-4, Bo Arleth wrote:
>>>> Ok, I'll guess I'll just have to live with as you said. But I checked
>>>> once again, and it is just the Inline Script, which is disabled.
>>>> So maybe in the future E-prime will add this function, so you have
>>>> more control over your datafile.
>>>> Kind Regards
>>>> Bo Arleth
>>>> On 16 Apr., 16:52, David McFarlane <mcfar... at msu.edu> wrote:
>>>>> Stock reminder:  1) I do not work for PST.  2) PST's trained staff
>>>>> take any and all questions
>>>> athttp://<http://support.pstnet.com/e%2Dprime/support/login.asp>
>>> support.pstnet.com/e%2Dprime/support/login.asp,
>>>> and they
>>>>> strive to respond to all requests in 24-48 hours -- this is pretty
>>>>> much their substitute for proper documentation, so make full use of
>>>>> it.  3) In addition, PST takes questions at their Facebook page
>>>> (<
>>> http://www.facebook.com/pages/Psychology-Software-Tools-Inc/241802160683>
>>> http://www.facebook.com/pages/Psychology-Software-Tools-Inc/241802160683
>>>>> ), and offers several instructional videos there and on their YouTube
>>>>> channel
>>>> (<http://www.youtube.com/user/PSTNET>http://www.youtube.com/user/PSTNET)
>>>> (no Twitter feed yet,
>>>>> though).  4) If you do get an answer from PST staff, please extend
>>>>> the courtesy of posting their reply back here for the sake of others.
>>>>> That said, here is my take...
>>>>> First, are you sure that you are disabling LogData on only the InLine
>>>>> object, and not for the entire Procedure that contains the InLine?  I
>>>>> just checked, and even the latest release of EP (2.0.10.182) shows no
>>>>> way to disable LogData for an InLine.
>>>>> In that case, I suspect that you have actually disabled LogData for
>>>>> the entire Procedure.  As you have discovered, disabliing LogData for
>>>>> a Procedure requires a great deal of finesse, and should be done only
>>>>> by the most advanced users under unusual circumstances.  And AFAIK
>>>>> LogData is not documented anywhere.
>>>>> So, just leave LogData enabled.  Yes, all the c.SetAttrib commands
>>>>> will leave extra junk in your .edat file, we have all just had to
>>>>> live with that.  Although, according
>>>> tohttp://<http://www.pstnet.com/support/kb.asp?TopicID=3618>
>>> www.pstnet.com/support/kb.asp?TopicID=3618,
>>>> the latest
>>>>> release of EP2 now includes a way to disable logging of specified
>>>>> Context attributes.
>>>>> -----
>>>>> David McFarlane
>>>>> E-Prime training
>>>> online:
>>>> <http://psychology.msu.edu/Workshops_Courses/eprime.aspx>
>>> http://psychology.msu.edu/Workshops_Courses/eprime.aspx
>>>>> Twitter:  @EPrimeMaster
>>>> (<http://twitter.com/EPrimeMaster>twitter.com/EPrimeMaster)
>>>>> At 4/15/2012 03:07 PM Sunday, you wrote:
>>>>>> I am having a problem with my experiment, and as luck would have it,
>>>>>> it is the last thing that needs doing. I've been searching everywhere
>>>>>> for a solution, but now i need some assistance. I have attached my
>>>>>> experiment, so you can see the code.
>>>>>> But whenever i go to the procedure, and try to disable "Log Data" for
>>>>>> my FeedbackScript (An inline object that comes before the Feedback-
>>>>>> slide), the .txt file will not convert to the .edat2, and gives me an
>>>>>> error - Illegal number of levels logged or the datafile did not
>>>>>> convert. Either Error 10 or 86. This msg ofcourse comes right at the
>>>>>> end of the experiment. As soon as i enable "Log Data" for the
>>>>>> feedbackscript it succesfully converts the .txt file to .edat2.
>>>>>> Is there any way to bypass this? Or any suggestions on how to fix it?
>>>>>> The reason I want to disable the logging for this script is because it
>>>>>> has alot of useless attributes set for coordinates and such, and these
>>>>>> attributes clutter up the data file, and ruins its already streamlined
>>>>>> look :)
>>>>>> Please write if you need more infomation from me.
>>>> On Tuesday, April 17, 2012 9:55:46 AM UTC-4, Bo Arleth wrote:
>>>> Ok, I'll guess I'll just have to live with as you said. But I checked
>>>> once again, and it is just the Inline Script, which is disabled.
>>>> So maybe in the future E-prime will add this function, so you have
>>>> more control over your datafile.
>>>> Kind Regards
>>>> Bo Arleth
>>>> On 16 Apr., 16:52, David McFarlane <mcfar... at msu.edu> wrote:
>>>>> Stock reminder:  1) I do not work for PST.  2) PST's trained staff
>>>>> take any and all questions
>>>> athttp://<http://support.pstnet.com/e%2Dprime/support/login.asp>
>>> support.pstnet.com/e%2Dprime/support/login.asp,
>>>> and they
>>>>> strive to respond to all requests in 24-48 hours -- this is pretty
>>>>> much their substitute for proper documentation, so make full use of
>>>>> it.  3) In addition, PST takes questions at their Facebook page
>>>> (<
>>> http://www.facebook.com/pages/Psychology-Software-Tools-Inc/241802160683>
>>> http://www.facebook.com/pages/Psychology-Software-Tools-Inc/241802160683
>>>>> ), and offers several instructional videos there and on their YouTube
>>>>> channel
>>>> (<http://www.youtube.com/user/PSTNET>http://www.youtube.com/user/PSTNET)
>>>> (no Twitter feed yet,
>>>>> though).  4) If you do get an answer from PST staff, please extend
>>>>> the courtesy of posting their reply back here for the sake of others.
>>>>> That said, here is my take...
>>>>> First, are you sure that you are disabling LogData on only the InLine
>>>>> object, and not for the entire Procedure that contains the InLine?  I
>>>>> just checked, and even the latest release of EP (2.0.10.182) shows no
>>>>> way to disable LogData for an InLine.
>>>>> In that case, I suspect that you have actually disabled LogData for
>>>>> the entire Procedure.  As you have discovered, disabliing LogData for
>>>>> a Procedure requires a great deal of finesse, and should be done only
>>>>> by the most advanced users under unusual circumstances.  And AFAIK
>>>>> LogData is not documented anywhere.
>>>>> So, just leave LogData enabled.  Yes, all the c.SetAttrib commands
>>>>> will leave extra junk in your .edat file, we have all just had to
>>>>> live with that.  Although, according
>>>> tohttp://<http://www.pstnet.com/support/kb.asp?TopicID=3618>
>>> www.pstnet.com/support/kb.asp?TopicID=3618,
>>>> the latest
>>>>> release of EP2 now includes a way to disable logging of specified
>>>>> Context attributes.
>>>>> -----
>>>>> David McFarlane
>>>>> E-Prime training
>>>> online:
>>>> <http://psychology.msu.edu/Workshops_Courses/eprime.aspx>
>>> http://psychology.msu.edu/Workshops_Courses/eprime.aspx
>>>>> Twitter:  @EPrimeMaster
>>>> (<http://twitter.com/EPrimeMaster>twitter.com/EPrimeMaster)
>>>>> At 4/15/2012 03:07 PM Sunday, you wrote:
>>>>>> I am having a problem with my experiment, and as luck would have it,
>>>>>> it is the last thing that needs doing. I've been searching everywhere
>> ...
>>
>> læs mere »
> 

-- 
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