Menu

load frame data from aedat file recorded with DAVIS240C

Developers
Alex A
2017-06-06
2017-06-06
  • Alex A

    Alex A - 2017-06-06

    Hello

    I have a DAVIS 240C and I am trying to load and visualize in matlab the framedata from an aedat file that was logged using jaer.
    To do this I am running the ExampleImportAedat.m script that has been provided. I have set input.filePath to point to my aedat file and I also set input.source = 'Davis240c';
    Apart from that I have not modified the script at all.
    The problem is that when I visualize the frame data in matlab the image looks very saturated and washed out. When I visualize the frame data running live from jaer the frames look sharp and with good contrast. Why is this happening? Do I need to modify some contrast settings perhaps when logging the data in jaer? How can I record frame data in an aedat file so that when I visualize it offline in matlab it looks similar to the way it looks when I am visualizing a live stream in jaer?
    Thanks.

     
    • Tobi Delbruck

      Tobi Delbruck - 2017-06-06

      Hi Alex, it might be that the script is not normalizing the data right
      or that in AEViewer the AutoContrast is turned on. Try toggling AEViewer
      AutoContrast from the DAVIS menu (shortcut shift-C). The control tab for
      AutoContrast is a tab in the HardwareConfiguration window. This
      algorithm is just something I wrote to lowpass filter the low and high
      limits of video and use these to scale the output to fill the 0-1 range
      of display.
      I haven't looked at the script but I'm sure there is a number there for
      the contrast setting.
      The other possibility is that there is a bug in the script and you are
      only seeing the Sample frame, not Reset-Sample frame. Are the gray
      levels inverted?
      Hope this helps.
      Tobi

       
  • Alex A

    Alex A - 2017-06-06

    Thanks Tobi. I ll take a closer look at your suggestions.
    By the way in the ImportAedatDataVersion1or2.m there are 2 bugs that cause programs to crash:
    line 149: info.startEvents should be info.startEvent
    and
    line 418 should probably be
    if frameCount==1
    instead of
    if ~exist('frameCount', 'var')

     
  • Luca Longinotti

    Luca Longinotti - 2017-06-06

    There is also https://github.com/simbamford/AedatTools which is a more generic and advanced set of scripts, supports caer data files too.

     
  • Sim Bamford

    Sim Bamford - 2017-06-06

    Hi - yes get the latest version from https://github.com/simbamford/AedatTools . In your case perhaps you need to set the SubtractResetRead flag - otherwise you're getting reset and signal reads from a .aedat v2 recording all as separate frames.