Saturday, October 31, 2015

Progress Report 3

This past week was a short one, primarily because we missed STEM class on Tuesday due to the College English field trip. On Thursday, we continued to explore and follow the OpenVIBE sample scenario tutorials and proceeded to create them using the OpenVIBE Designer application. In particular, completed 'Designer Tutorial 4: Window Manager' (http://openvibe.inria.fr/designer-tutorial-4/). We followed the tutorial and ended up creating a series of displays and topographic maps:

Next week, we plan to wrap up the OpenVIBE simple scenario tutorials and use our newly founded navigational skills to create our scenarios. We will look to Andre's and Ryan's scenarios from last year to guide us through the process. In addition, we hope to figure out a way to connect the NeuroSky Mindwave headset to Openvibe on the Windows computer, as we will need our brain data in the future. Lastly, we will continue to update our Gantt Chart on the basis of changes to our plans. 

Sunday, October 25, 2015

progress report 2

Since the past progress report we have not made much progress on our issue connecting the neurosky headset to a windows computer. Apparently, windows obnoxiously keeps rejecting the neurosky driver and installing their own, which then won’t succesfully connect. Although we have worked with the neurosky drive and looked for help on several online forums, we could not find a solution.

Our project is multi-faceted, though. We have learned that instead of sitting on that problem and halting the rest of our work until we find a solution, we can focus on a different aspect of our research. We have done so by directing our attention towards OpenVibe.

Using one of the computers the last year’s OpenVibe group used, we explored the OpenVibe platform as per our past research. We utilized the tutorials on OpenVibe’s website and created our own few scenarios, using the given boxes. The scenarios are not of heavy importance; they were just meant as exercises, and taught us valuable OpenVibe navigation skills.

Next week, we will continue with more OpenVibe tutorials to familiarize ourselves with OpenVibe as authors. In addition, we will be utilizing last year’s recorded EEG data in our scenarios, until we can successfully connect the Neurosky headset.

We have added a goal to our Gantt chart: we want, with the help of the OpenVibe tutorials, build a functioning scenario with several boxes, maybe even something pre-recorded like the handball game.

Tuesday, September 29, 2015

Gantt chart

https://drive.google.com/folderview?id=0BypNBzRHej1dR1ZydkRzXzE4Rkk&usp=sharing

Sunday, September 20, 2015

Resource from Last Year


    RE: Initial Planning & Coordination

    Project Description & Merits
    Describe the project in your own words and list the possible contribution your project can have to advance the field of STEM or solve societal problems.
    • Our project is concerned with interpreting brain signals using OpenViBE, which is an open source platform dedicated to designing, testing, and using brain-computer interfaces.
    • Our project can be used in various ways. The technology of interpreting brainwaves and using them to control devices has far-reaching implications, especially for disabled people. Through OpenVIBE, we hope to design a BCI that may perhaps one day be used for convenience.

    Group/Team Communication
    Who will be involved in your project (team) and relevant projects (group)? How to communicate effectively with each other? What are the tools for project collaboration?
    • Team - Brian Wong and Sarah Landau
    • Groups - groups 4, 5, and 6
    • The key to effective collaboration is communication. Updating each other on progress or complications will definitely make things smoother going ahead.  
    • How to communicate with other teams (5 & 6)? Have you set up some mechanism (chat group, Google doc, or Git Hub)?
    • Since you are going to develop analysis and classification algorithms for team 5 & 6, you should understand their topics and tune your research directions accordingly. Of course, at the very beginning, you can start following something in the tutorials (maybe not directly related to their topics) for learning purpose. Once you set up the whole analysis, classification, and online testing mechanism, you can then modify it to adapt to their needs.

    Prior Work/Resource Inventory
    Go to the Project Resource website to review the current resource and prior work. Update the page.
    • Have you conduct your extensive literature survey?

    Technology Analysis
    Identify the scientific and technical knowledge/skills involved in your project.
    • Familiarization with the OpenVIBE platform
    • Familiarization with the Neurosky Headseat (and Emotiv Insight headset)
    • Should be in more details such as the flow chart of the signal processing and feature extraction, the classification algorithms (such as SVM and LDA), online testing,  OpenVibe library, subject testing method/process, etc..

    Competence
    Identify skill sets, technical competence in your group, and list the missing ones which need to be acquired.
    • Sarah needs to polish up on physics
    • Brian needs to familiarize himself with the OpenVIBE library
    • You forgot to list what competence you already have.
    ·       
    Safety
    Identify any safety issues regarding the build, use, store, and dispose of materials and tools
    • Nothing really to worry about.


    Equipment, materials & budget
    List the key materials and equipment required for your project. Identify the key items needed to be purchased and their prices.
    • Windows computer
    • Nuerosky headset (and Emotiv Insight headset)
    • Do you think you can share the headsets with them or you may need one for your team?

    Schedule
    What are the goals/milestones/plans of your project in the next week? What are the task assignments for each team member?
    • We will both sit down and compare our notes on the summer assignments. We will also review the assignments and try to operate the OpenViBE with the headset together.