And why the struggle is real…
9 September 2019
I’ve been having some trouble with this project, mostly because I am typically used to setting a goal before kicking off, and working towards it. I appreciate the concept of tinkering and I understand the importance of it, but without a set goal, I lose my motivation a little, since I have no specific goal to work towards.
Denisa and I illustrated some concepts we wanted to work towards but that was immediately called-out by Clint, yes, during the kick-off Clint specifically stated that we should not present concepts before beginning. But that’s the main challenge for me. I. need. a. concept. to. work. with!
So what I’ve done so far (over the weekend) is: looked at all the samples provided, played around with it such as changing some values and seeing the results on canvas (It’s crazy how changing one single seemingly-insignificant value breaks the entire code down, haha).
I’m extremely drawn towards the emotions sample in the file clmtrackr, I went and looked through the gitHub repo of the original creator of clmtrackr. That helped quite a lot, as I began to understand how the facial model worked. auduno’s clmtrackr also presented some examples on using the face tracker so I also experimented around with those. He also had an emotion tracker sample.
I strove to further understand the code under camera-clmtrackr-emotions, including the files in the library like emotion_classifier.js and emotionmodel.js. I wanted to understand how the different emotions are documented and translated into the score that’s presented on the top left, like the “coefficients” and “bias” stuff seen in emotionmodel.js. And I wanted to play with that, like tweaking the bias, see what happens when it is a positive number or a lower negative value!
Perhaps I could try playing with two different codes and incorporate one into the other? Denisa and I discussed about audio outputs so maybe figure out how that would work into the code, etcetera.
Journal with me! 