|
|
|
[[_TOC_]]
|
|
|
|
# Getting Started
|
|
|
|
Editing data using this method is a manual way for you to inspect the scroll data and at the same time mark it up into different components.
|
|
|
|
This method can be used before and after editing the data using scripts, depending on what aspects of the data you are looking at. Selections can help you visually interpret the data but also saves the selection on the data. This information can be used later to isolate the data into the different selections.
|
|
|
|
This method can be used before and after [editing the data using scripts](https://git.sharcnet.ca/bucanl_eeglab_extensions/vised_marks/wikis/vised), depending on what aspects of the data you are looking at. Marks can help you visually interpret the data and will also save the marks selections on the data that you have made. This information can be used later to isolate or chop up the data into the different selections.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In order to start directly editing and placing marks by interacting with the scroll data go to:
|
|
|
|
In order to start directly editing and placing marks load the scroll data by going to:
|
|
|
|
* *Edit -> Visually Edit in Scroll Plot*
|
|
|
|
|
|
|
|
|
|
|
|
The first pop up that shows up should look similar to the figure below.
|
|
|
|
|
|
|
|
|
|
|
|
If you haven't already go check out the [Configuration Page](https://git.sharcnet.ca/bucanl_eeglab_extensions/vised_marks/wikis/config) to find out what each of these interface fields are. If you have already created or loaded a configuration file then most of these fields will already be complete. The most important field for this manual editing method is the *key select command [keyselectcommand]* as it is where you can define each of your editing key strokes. You will be creating a cell array of strings that should follow this pattern:
|
|
|
|
If you haven't already go check out the [Configuration Page](https://git.sharcnet.ca/bucanl_eeglab_extensions/vised_marks/wikis/config) to find out what each of these interface fields are. If you have already created or loaded a configuration file then most of these fields will already be complete.
|
|
|
|
***
|
|
|
|
|
|
|
|
The most important field for this manual editing method is the *key select command [keyselectcommand]* as it is where you can define each of your editing key strokes. You will be creating a cell array of strings that should follow this pattern:
|
|
|
|
* **key_press,function_called('key_action1','key_value1'...'key_action2','key_value2'...)**
|
|
|
|
* Each on a separate line
|
|
|
|
|
| ... | ... | @@ -20,7 +23,7 @@ First is the keyboard key that you going to assign a certain action to. Next a c |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ve_eegplot and ve_edit function both contain different key actions in them, some of which are outlined below. You can call as many key_action as you would like in the same function. You can also assign a key to call two different functions, by simply creating a new line and reusing the same designated key stroke.
|
|
|
|
ve_eegplot and ve_edit function both contain different common actions you may want as hotkeys in them, some of which are outlined below. You can call as many key_action as you would like in the same function. You can also assign a key to call two different functions, by simply creating a new line and reusing the same designated key stroke.
|
|
|
|
|
|
|
|
### ve_edit
|
|
|
|
|
| ... | ... | @@ -84,7 +87,6 @@ The process to remove a mark is very similar. Start by using the winrej tool to |
|
|
|
```matlab
|
|
|
|
M,ve_edit('rwm','custom_mark')
|
|
|
|
```
|
|
|
|
|
|
|
|
or
|
|
|
|
|
|
|
|
```matlab
|
| ... | ... | |
