D2.1 Requirements and Specification - CORBYS

Recommendations

Info

D2.1 Requirements and Specification Indicative priority Mandatory 6.2.1.2 Interfaces This task will use hardware and software that is available at UB to conduct the studies. Therefore, no interfaces to other sub-systems are necessary to conduct the BCI experiments at UB. 6.2.1.3 Roles and responsibilities To conduct the experiments that will help to investigate the detection of human cognitive information related to the motor tasks, the design of a detailed experimental protocol is necessary. This protocol will be designed and discussed in collaboration with BBT partner. The experiments will be conducted by UB with healthy users. UB will provide results of EEG offline and online analysis for the detection of motor intention to BBT in order to integrate the program code into the Brain Computer Interface software architecture that will be developed in task 3.4. 6.2.1.4 Goals and expectations The goal of this task is the detection of motor intention (e.g., before actual leg or feet movement is executed). It is expected that the signal processing can not differentiate between intention of moving right from left leg or foot. 6.2.1.5 Operating environment Laboratory: University of Bremen 6.2.1.6 Resources Hardware: Data will be acquired through a Porti32 amplifier (Twente Medical Systems International, Netherlands). Software: BCI2000 framework software for signal acquisition and stimulus presentation will be used. Materials: 33 Electrodes and 3 EEG caps are required. 6.3 BCI Software Architecture (Task 3.4, BBT) Relevant task: � Design of a brain computer software architecture (TASK 3.4, BBT) This task will provide software architecture for the integration of the BCI-related devices and of the neural decoding mechanisms required in CORBYS (Task 3.5). 48
D2.1 Requirements and Specification 6.3.1 Functional Requirements 6.3.1.1 Interfaces Requirement No. BCISW1 Name: BCI communication interface Description: External interface that communicates with other subsystems using a TCP/IP messages protocol. Reason / Comments: Easy communication and integration between subsystems. Indicative priority Mandatory Requirement No. BCISW2 Name: Therapist GUI Description: The graphical user interface (GUI) allows the therapist to interact with the BCI software. Reason / Comments: Facilitate the use of the BCI software to non-computer experts. Indicative priority Mandatory Requirement No. BCISW3 Name: Subject GUI / User GUI Description: In the training and decoding process subjects are asked to perform some tasks. Reason / Comments: The graphical user interface (GUI) displays commands to the subject (e.g. a visual cue indicating that the subject intends to start walking). Indicative priority Mandatory 6.3.1.2 Goals and expectations Requirement No. BCISW4 Name: BCI software portability Description: The BCI software can run over different operating systems (Windows, Linux, etc.) Reason / Comments: The BCI software can be easily moved from an environment to another. Indicative priority Desirable 6.3.1.3 Resources Requirement No. BCISW5 Name: EEG sensor cap size Description: The cap is available in 3 sizes (small, medium and large); the most appropriate one needs to be chosen depending on the subject head circumference. Anyway the medium-sized cap is suitable for over 95% of all adult subjects. Reason / Comments: An appropriate cup allows achieving a better signal quality. Indicative priority Desirable Requirement No. BCISW6 Name: EEG Electrodes location and number Description: The EEG electrodes are inserted via small holes in the cap. Their position on the scalp, indicated on the cap according to the extended international 10/20 system, and number depends on what brain areas are activated during a specific cognitive task. Ongoing CORBYS research will identify those (Tasks 3.3 and 3.5). Reason / Comments: Specific electrodes placements and number related to the cognitive processes required in CORBYS are needed. Indicative priority Mandatory Requirement No. BCISW7 49
Page 1 and 2:
CORBYS Cognitive Control Framework
Page 3 and 4:
D2.1 Requirements and Specification
Page 5 and 6:
Page 7 and 8: D2.1 Requirements and Specification
Page 57: D2.1 Requirements and Specification
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209:
show all

D2.1 Requirements and Specification - CORBYS

Create successful ePaper yourself

Delete template?

Save as template?