Improve report clarity

[ohjerm]

Thomas, Stefan and Morten's comments:

[Sebfrede]

Make a good timeplan
-Ensure we have enough time for a proper evaluation!
-Find Hand-In date

Make Lo-Fi test with "normal" people to find unseen flaws
-Test our base system THEN add one modality to see if it improves and then continue
-When should our data fuse? Should all data fuse at the same time?

Input modality
-Do we need to talk about tongue control or would a joystick be better?

Make sure we write about the stuff we are not implementing / design choices (afgrænsninger)
-Be more clear in writing on what we exactly are going to focus on!

Make a Evaluation Plan
-What do we want to test and how should the setup be?
-Control group vs our program / multiple setups?

Figure out what we want to focus on!
-We only have limited time and resources so find the good stuff
-Object detection vs w/e

Make some concept art
-What does the entire EXOTIC project entail? And what part of it will our project focus on

Test specifications (success criteria)
-When is our system a "success"?
-Rewrite likeability (maintain)
-We would like some quantitative data

Expand on Background Research
-How are people evaluating? How many people, how are they testing (setup), iterations etc.

Find the right weights for the different modalities
-Do we want adaptive weights or preset?

Make sure we don't overcomplicate things and take on too much work
-Better to have a simple and well documented work than too much bad work

Fix report (Stefan's fixes)

More figures for visualization of progress and system
-Will also aid in keeping the "red-thread"
-Red-Thread in writing pls