Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
faq:how_can_i_use_the_databrowser [2018/10/21 14:57]
42.49.180.224 [How can I use the databrowser?]
faq:how_can_i_use_the_databrowser [2017/08/17 11:21] (current)
127.0.0.1 external edit
Line 5: Line 5:
 The databrowser can be used to look at your raw or preprocessed data and annotate time periods at which specific events happen. Originally designed to identify sleep spindles, it's current main purpose is manual artifact detection. You can call the databrowser in an interactive mode by storing the output in a cfg like this: The databrowser can be used to look at your raw or preprocessed data and annotate time periods at which specific events happen. Originally designed to identify sleep spindles, it's current main purpose is manual artifact detection. You can call the databrowser in an interactive mode by storing the output in a cfg like this:
  
-&lt;code matlab&gt;+<code matlab>
   cfg = ft_databrowser(cfg,​ data);   cfg = ft_databrowser(cfg,​ data);
-&lt;/code&gt;+</code>
  
 Note that the second argument, data, is optional. You can also read in data from your harddrive instead, see **[[reference:​ft_databrowser]]**. Note that you need to specify whether your data is continuous or not by setting cfg.continuous to '​yes'​ or '​no'​. If your data is trial based, then continuous is '​no',​ if you have one long continuous recordings without breaks, you can set continous to '​yes'​. Note that the second argument, data, is optional. You can also read in data from your harddrive instead, see **[[reference:​ft_databrowser]]**. Note that you need to specify whether your data is continuous or not by setting cfg.continuous to '​yes'​ or '​no'​. If your data is trial based, then continuous is '​no',​ if you have one long continuous recordings without breaks, you can set continous to '​yes'​.
  
-&lt;note important&gt;+<note important>
 If you call the databrowser without an output argument like this: If you call the databrowser without an output argument like this:
-&lt;code&gt;+<code>
   ft_databrowser(cfg,​ data)   ft_databrowser(cfg,​ data)
-&lt;/code&gt;+</code>
 then whatever you do, it will **not** be saved! Be sure to specify an output argument if you want it to be saved! then whatever you do, it will **not** be saved! Be sure to specify an output argument if you want it to be saved!
-&lt;/note&gt;+</note>
  
 The databrowser supports three viewmodes: butterfly, vertical or component. In '​butterfly'​ viewmode, all signal traces will be plotted on top of each other, in '​vertical'​ viewmode, the traces will be below each other. The '​component'​ viewmode is made specifically if you provide data decomposed into individual components, see **[[reference:​ft_componentanalysis]]**. The data will be plotted as in vertical viewmode, but including a topographic map of the component to the left of the time trace. As an alternative to these three viewmodes, if you provide a cfg.layout, then the function will try to plot your data according to the sensor positions specified in the layout. The databrowser supports three viewmodes: butterfly, vertical or component. In '​butterfly'​ viewmode, all signal traces will be plotted on top of each other, in '​vertical'​ viewmode, the traces will be below each other. The '​component'​ viewmode is made specifically if you provide data decomposed into individual components, see **[[reference:​ft_componentanalysis]]**. The data will be plotted as in vertical viewmode, but including a topographic map of the component to the left of the time trace. As an alternative to these three viewmodes, if you provide a cfg.layout, then the function will try to plot your data according to the sensor positions specified in the layout.
Line 23: Line 23:
 When the databrowser opens, you will see buttons to navigate at the bottom and artifact annotation buttons on the right. Note that also artifacts that were marked in automatic artifact detection methods will be displayed here, see **[[tutorial:​automatic_artifact_rejection|automatic artifact rejection]]**. You can click on one of the artifact types, select thet start and the end of the artifact and then double click into the selected area to mark this artifact. To remove such an artifact, simply repeat the same procedure. When the databrowser opens, you will see buttons to navigate at the bottom and artifact annotation buttons on the right. Note that also artifacts that were marked in automatic artifact detection methods will be displayed here, see **[[tutorial:​automatic_artifact_rejection|automatic artifact rejection]]**. You can click on one of the artifact types, select thet start and the end of the artifact and then double click into the selected area to mark this artifact. To remove such an artifact, simply repeat the same procedure.
  
-&lt;note important&gt;+<note important>
  The databrowser will **not** change your data in any way, it will just store your selected or de-selected artifacts in your cfg.  The databrowser will **not** change your data in any way, it will just store your selected or de-selected artifacts in your cfg.
-&lt;/note&gt;+</note>