Search the Legacy Support Archive (up to v2020)
  1. Read-only archive (2005–2024). Posting is closed. Need help with MediaLab or DirectRT 2027? Email service@empirisoft.com.

    All words · “exact phrase” · -leave out

    Advanced search

Problem with output files (case 8614)

  1. #1

    Problem with output files (case 8614)

    Hi there, I ran an experiment using a Go/No-Go Task, where I programmed 3 test blocks (40 trials each block). So each output file should have recorded 120 trials. But instead, each participant seems to have a different number of trials recorded in their respective output files. I have NO idea what might be going on here! I have attached the input file for the task, as well as a few participant's output files. Any suggestions/advice would be much appreciated! Thanks!

  2. #2
    Hi mariegood!

    Could you please tell me what version of DirectRT you are using (ver20xx.x.xx)? Also, do you get these same errors with some data not recording if you run the sample gnat that came with DirectRT? You can find the input files at \DirectRT\Samples\6 - v2006\gnat wherever you installed the DirectRT program files on your computer.

  3. #3
    In our lab we have 5 computers - 3 of them use version 20.12.4.155, one uses 20.12.4.160, and the other uses 20.12.4.157. When we run the sample gnat we didn't have the same problem. Thanks so much!!

  4. #4
    It would seem like the problem lies in the input file you made. I looked at it and the 3 output files you attached and noticed that the missing data was for block 1 (trials 1-40). Can you try the following and let me know if the data record correctly?

    1) Create and run a new input file without block 1 in it.
    2) Create and run a new input file without the first break (row 28 in the original).

    Can you also send me a zip file with all of your original stimlists and any stimulus materials? I'd like to try running your experiment on my computer to see if I can replicate this error.

  5. #5
    Thanks. I'm going to run the input files with your suggestions tomorrow at the lab and will let you know what happens ASAP. I've attached a file with all my stim, etc.

  6. #6
    Hi again,
    I ran the GNG files making the changes you suggested.
    (1) When I deleted block 1, everything appeared to record properly in the output files.
    (2) When I deleted the first break (line 28), everything also recorded properly.
    Thanks,
    Marie

  7. #7
    Hi Marie,

    Thanks for letting me know that. So would you be able to run the experiment as you intended if you just deleted row 28 from the original input file?

  8. #8
    I ran 3 "participants' with just line 28 deleted, and I've attached the output files - just as before, each participant had a different number of trials record. Any thoughts? I also attached the input files. Thanks!

  9. #9
    mariegood,

    Did you ever receive a message at the end of the one your sessions in which data did not record asking you to take a look at the TrackPerformance.txt file? If so, can you please find it in the DirectRT folder and send me a copy of what it says?

    Thanks!

  10. #10
    Would you be able to send us the input files that DirectRT created with specific values in the time cells for the ~+ and ~ stimuli? There would be six files that start with gn1_gojuice and ended with _xx, with xx being the participant number used for that session. So you would have files named gn1_gojuice__08, gn1_gojuice__49, gn1_gojuice__30, gn1_gojuice__05, gn1_gojuice__06, and gn1_gojuice__07.

  11. #11
    Hi mariegood.

    Did you ever find a resolution to this problem?

  12. #12
    Hello,

    I'm having the same problem as the poster above such that every participant seems to be getting a different number of trials out of the number of trials they should be getting for the Go/No-Go Task. I've attached my Input file...do you see any errors?


  13. #13
    Hi mfrancis!

    Your use of the jump feature has an extra - character. Right now, it looks like


    24<-999


    Remove all of the dashes any time you have the jump command so that it instead looks like


    24<999


    Then try running that input file a few times to see if all of the data records. This test version of the input file should also not use any randomization so that you do not have to contend with that as a confounding variable.