Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment   Page 11 of 11     «   Prev   8   9   10   11
Jaewon

Administrator
Registered:
Posts: 754
Reply with quote  #251 
* Changes in NIMH MonkeyLogic 2 (Dec 21, 2018)

 + Support for time-stamped video capture from webcams.  I don't have many
   webcams to test with, so some cams may not work yet.  Captured video can be
   played and exported with mlplayer, or directly read from the data file.

 + Support for the second joystick. You can use either 1) two analog joysticks,
   2) two USB joysticks or 3) one USB joystick + one analog joystick.

   Two new runtime functions, joystick2_position() and showcursor2(), are added
   for the 2nd joystick. get_analog_data() also works with the 2nd joystick.

    gen_analog_data('joystick2',1000);  % or 'joy2'

   eyejoytrack() can monitor the 2nd joystick with 'acquiretarget2' and
   'holdtarget2'.  For the scene framework, a new tracker, joy2_, is added.

   In the simulation mode, the 2nd joystick is emulated with the following
   keys: 'A' (left), 'D' (right), 'W' (up), 'S' (down).


0
pschade

Junior Member
Registered:
Posts: 8
Reply with quote  #252 
Hi Jaewon,

I recently updated my monkeylogic from the July 2018 build to the Nov 2018 build and I am now having issues with an increasing ITI for a simple RSVP task. It begins with a sub 200ms ITI but after 600 trials, it is up to 400ms, and after a couple thousand trials it is more than 1 second. I did not have this issue with the previous build using the same code; the ITI stayed below 200ms. Is there something new to ML that could be causing this? 
0
Jaewon

Administrator
Registered:
Posts: 754
Reply with quote  #253 
See if you store something of which size grows over time.
0
aboharbf

Member
Registered:
Posts: 69
Reply with quote  #254 
Quote:
Originally Posted by pschade
Hi Jaewon,

I recently updated my monkeylogic from the July 2018 build to the Nov 2018 build and I am now having issues with an increasing ITI for a simple RSVP task. It begins with a sub 200ms ITI but after 600 trials, it is up to 400ms, and after a couple thousand trials it is more than 1 second. I did not have this issue with the previous build using the same code; the ITI stayed below 200ms. Is there something new to ML that could be causing this? 


I had an issue like this which may have come from two things:

1) I was using a reward vector instead of a single number (Goodmonkey, perhaps inappropriately in my context, accepts vectors for duration, even though documentation suggests it only accepts a single value).

2) I was using .mat instead of .bhv2. If you're using .mat, i suggest swapping to .bhv2.
0
pschade

Junior Member
Registered:
Posts: 8
Reply with quote  #255 
I just downgraded to the jun 20th version that was on my computer and its back to sub 200ms ITI. 

Is there a default save somewhere in the newer versions or have there been changes to what is saved? The whole lab is using the Oct 4th build or earlier and have not had this issue with the same RSVP task.

We have had this issue with several computers and 2 tasks with the Nov 30th build. One task that just juices and prints to the screen when a touchscreen is touched and this one, carrying a single vector from trial to trial that does not grow in size. 

I am using a single value for reward and using .bhv2. 
0
Jaewon

Administrator
Registered:
Posts: 754
Reply with quote  #256 
Hi pschade,

I replicated the issue, but am in the middle of a major update and cannot fix the issue immediately. You can stay with the Oct version for a little longer or overwrite mlbhv2.m of the Nov version with that of the Oct version. Thank you for reporting this problem. Sorry for the inconvenience.
0
Jaewon

Administrator
Registered:
Posts: 754
Reply with quote  #257 
* Changes in NIMH MonkeyLogic 2 (Jan 7, 2019)

 + Multi-touch is now supported.  Touch input is not acquired through the mouse
   any more and there are some related-changes made.

   Users can activate touch input and set the number of touches to
   simultaneously track (up to 10) in the Non-DAQ device settings menu.

   In the data file, the touch data is now stored under the Touch field of
   the AnalogData structure, not the Mouse field.

   As more touches are tracked, more columns are added to the Touch data field,
   like the following.

    [x1 y1 x2 y2 x3 y3 ...];  % AnalogData.Touch

   Two timing script functions, touch_position() & istouching(), are added.

   Touch input can be tested in the IO Test menu.

   Mouse input is still supported (in the scene framework only) for those
   adapters that require mouse and keyboard controls, such as Grating_RF_Mapper
   or RDM_RF_Mapper.  You should use the mouse tracker (mouse_) for them,
   instead of the touch tracker (touch_).  mouse_ is available, when the Mouse / Key
   option is checked in the Non-DAQ devices menu.

touch.png 

 + Users can choose how many USB joystick buttons to record to the data file.

 + In case that the userplot function is set, the control screen window spares
   larger space for the user plot.

 - The problem that BHV2 takes more time to save is fixed. (Thanks to pschade
   from the ML forum)

 - When the error logic was 'repeat delayed' and the last trial in a block was
   failed, the trial was not repeated correctly. It is fixed now.


0
Jaewon

Administrator
Registered:
Posts: 754
Reply with quote  #258 
* Changes in NIMH MonkeyLogic 2 (Jan 14, 2019)

 - A problem that sound stimuli sometimes crash MATLAB is fixed. (Thanks to
   Jack_23 from the ML forum)


 
Attached Files
mlappi NIMH_MonkeyLogic_2_(Jan-14-2019).mlappinstall (31.12 MB, 2 views)
zip NIMH_MonkeyLogic_2_(Jan-14-2019).zip (30.11 MB, 1 views)

0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.