Back to the main page.

Bug 2318 - Databrowser - use axis limits to page data, rather than redraws

Status NEW
Reported 2013-10-11 13:26:00 +0200
Modified 2013-10-20 11:23:21 +0200
Product: FieldTrip
Component: core
Version: unspecified
Hardware: All
Operating System: All
Importance: P3 normal
Assigned to: Craig Richter
Depends on:
Blocks: 2314
See also:

Craig Richter - 2013-10-11 13:26:10 +0200

To increase paging speeds the data will be loaded in the figure as one long trial (continuous case) or as concatenated trials (epoch case), and the GIU will manipulate axis limits for navigation. There is a concern by Robert about data doubling that needs to be addressed.

Robert Oostenveld - 2013-10-20 11:23:00 +0200

On 20 Oct 2013, at 9:11, Craig Richter wrote: If the dataset is 1 gb, and then it is all loaded into 1 figure, what does matlab do memorywise? and Robert replies: I think it would help to try this with memtic/memtoc (in a clean matlab session). Whether the implementation is viable depends on 1) the size of the dataset 2) the amount of RAM available 3) the expectations of the users of the function We might want to implement it such that certain functionality can be en/disabled. For some functionality that might be relatively easy (like the datacursor) whereas for other functionality it might be more difficult. Perhaps it helps to list the various functionalities and see whether might be possible that they are en/disabled, or which ones are opposites of each other (i.e. toggles). Here is a list of functionalities, I tried sorting them in the historical order of when they were conceived - view continuous data from disk - view continuous data from memory - select segments as artifacts - page through the data using the < and > button - view segmented data from memory one segment as a time - view segmented data from memory one segment as a time - scroll through the data using the scrollbar - select segments and execute a function on them - identify channel, latency and value in a signal of interest