Is the timing file/script name for each trial saved anywhere in the data file?by holmescharles - Questions and Answers
Hi! Hopefully this is a quick question/answer: I'm looking at mouse data in the data files, e.g., /ML/Trial1/AnalogData/Mouse. These data are 4 x "however many samples". I think the first 2 rows are x and y positions, but its not clear to me what the other 2 rows are. My best guess is left and right click state or maybe row 3 is some button state and row 4 is the button identity. Aby holmescharles - Questions and Answers
Apologies, I had forgotten I posted that follow up question. If I had remembered and seen the answer I would not have made this post to begin with. Also sorry if I hurt your feelings using the word "redundant".by holmescharles - Questions and Answers
Hopefully this is more clear: So we are determining which limb a monk reaches. It can be right or left. We want to save this value for each trial so it will be in the output data file, but we ALSO want to access those values for previous trials during the experiment so we can update the task based on which limb is being used more often. We are doing two things at the end of the timing file:by holmescharles - Questions and Answers
What is the recommended way to access the history of variables saved with bhv_variable? For now, we are using TrialRecord.User.VariableName in parallel to save values from trial to trial (appending to a vector) but this feels like it should be redundant. Any insight would be helpful, thanks!by holmescharles - Questions and Answers
Hi, I'd like to ask a follow up question here: I understand that the recommended way to save trial variables is with bhv_variable, but is there a way to access the history of the variables saved this way from TrialRecord? E.g., if I want to save a boolean value for each trial and on each trial I wanted to print a running "percent true" of that boolean variable, how would I doby holmescharles - Questions and Answers
I'm using version 2 timing files. I'd like to determine the position and taskobject state (or statuses, i.e., whether the object is visible or not) at arbitrary times in the trial. With v1 timing files, I could look at ObjectStatusRecord/Times, ObjectStatusRecord/Statuses, and ObjectStatusRecord/Position. This is a bit more complicated with v2; data are saved sequentially by scene aby holmescharles - Questions and Answers
Amazing. Thank you!by holmescharles - Questions and Answers
Normally I'd agree, but I only need this behavior at the beginning of a trial. Later in the trial I need the LEDS to be off regardless of the buttons' states. So sounds like this calls for a user-defined adapter.by holmescharles - Questions and Answers
Hello! I am developing an experiment in which a subject will need to place each hand on a respective home button (so 2 button inputs). I really like how elegant I can write these scenes with the v2 architecture: I can join the two with an AndAdapter and follow that up with a WaitThenHold. My next step in development is to add LED indicators for each of the two home buttons. I have wired upby holmescharles - Questions and Answers
I am working with the v1 runtime. Is there an elegant way to avoid rewriting the same code over and over for different timing scripts? E.g., lets say I want to include the same hotkey mapping in all of my tasks; is there a way to avoid repeating myself rather than having to explicitly include this code in every task's timing file? Or what if I want to add functionality, i.e., wrap, to a rby holmescharles - Questions and Answers