dstolz / epsych Goto Github PK

I'm using the ep_2AFC macro as part of my RPVds circuit. I'd like to save the response latency on a trial-by-trial basis. The response latency output of the macro does not seem to be updating correctly, however. (The value just stays at zero, even though everything else in the circuit, including the response code, works perfectly). Have others run into this issue? If so, any suggestions on how to fix it?

Thanks!

Melissa

So the earlier versions of ep_ExperimentMaker.m did not allow you to update module info after you've made a protocol without first deleting the module entirely (hitting the "-" button) and then adding a new one which meant you had to re-parameterize everything. Frustrating!

I recently updated the GUI so that you can update the module info by clicking "Protocol" on the GUI's menu and then selecting which info you would like to update. Note that if the protocol was created for use with OpenEx, then you will not be able to update the RPvds file or hardware module type here because it is specified within TDT's OpenEx Workbench. You can change the module's "alias" (name) which must match whatever you specified in the Workbench.

After the recent update, there was a problem when loading existing protocols intended for use with OpenEx. This is fixed in the most current version of dstolz/master.