Skip to main content

How Affective Computing can forever change the way we look at Computers

What is Affective Computing? 

Affective Computing is the study and development of systems and devices that can recognize, interpret, process, and simulate human affects. It is an interdisciplinary field spanning computer sciencepsychology, and cognitive science.

So in simple terms, it's a study on Human Emotions. Most of the study is restricted to the first 3 keywords - recognize, interpret & process human emotions. How about developing a program that actually has  emotions? 

If we are talking about simulating human emotions, that would just be an emulation of the emotions majority of the humans feel in certain common situations - you give the program a certain input sitaution, it receives it, processes it, maps it, and provides the emotion "it is feeling". Is it the program's emotion? No, that program is simply apathic towards the situation.

What I propose is to make use of a Neural Network structure to actually emulate the Emotion Generating region of the brain. This implies that Affective Computing wouldn't just be called a mixture of Computer Science and Psychology then, but would rather need a major Neurobiological perspective to build a structure that could actually "generate" emotions.

Emotion Generating Region of the Brain

Let's look at the process of Emotion Generation psychologically first before learning about the process biologically. Emotion and Knowledge cannot be said as 2 really exhaustive sets within our memory. A certain stimulus can trigger a memory[knowledge] with which another emotion is associated. That particular emotion need not be a common association with the memory in everyone's mind in the same way that the certain stimulus cannot trigger the same memory in everyone's mind.
Everyone has different memories(experiences, knowledge), and different sets of emotions associated with it. 
Thus, emotions are memory or knowledge-dependent.

Starting a computer program with certain given knowledge/memory can be a better option since a software has no stimuli reception. Thus, all our inputs will be given digitally.

Testing of the Program

How would we test if the program is building its own emotions based on the events happening around it? The initial, and up till now, the only way to interact with such a program could be to shape this as a chat bot. Some expectations from this program could be:
  • Visible irritation in replies when being asked the same questions/inappropriate questions (provided it is built with/has gathered such specific knowledge)
  • A delightful response if a certain user comes back to interact with the program with whom the program had had a constructive discussion.
(This rough idea had to be given to the reader to make sense and visualize the kind of program I am talking about. However, the self-thinker might have realized the possibilities for such a program are truly endless).

Emotion Generation Continued

Now let's get back to this discussion through a neuro-biological perspective. ML Programs successfully emulate a Neural Network, however, it is far from being an actual simulation of the brain.
To truly understand the how's of Emotions in the brain, we need a Neurobiology expert, and I'm far from even understanding the where's of Emotions in the brain. 

With this hurdle, I will have to pause this discussion until I can accumulate more facts about the brain and emotions. Nevertheless, the analysis from a psychological perspective will still need to be further extended for implementation purposes. For instance, for questions about what parameters and quantity of knowledge shall we provide the initial program and the basis of retrieval of such information.

I hope to continue this discussion further. However, I would really appreciate more insights into this project. 


Post a Comment

Popular posts from this blog

Namaste JavaScript Quick Notes

Note:  Akshay Saini's Namaste JavaScript is probably the best course for JavaScript developers out there. These are my personal notes that I made while watching the course; they serve more of as an online quick reference for my understanding and revision, and I hope it benefits anyone reading it too! Everything in JS happens inside an Execution Context. Before a JS code is run, memory is allocated and variables are set as undefined   , and functions are set as their exact code in the scope within the Execution Context. The global execution context hosts all the global variables and function definitions. An Execution Context has 2 components: Memory, that stores variables and functions; and Code, that reads and executes the code. Call Stack maintains the order of execution contexts. Since JS is single threaded and asynchronous, at one point of time, only one function is executed which is at the top of the call stack. For each function, an execution context is created before executi

An introduction to APIs

API is an acronym for Application Programming Interface. Let's start with first defining some basic terms: Browser: These are browsers. To visit any website on the internet, you need a browser. Server: Hmm, this is tough. In simple words, server is a computer. Yes, just like the laptop, or PC at your home. The only difference is that it does not have a screen. Of course, there are other differences in technical specifications, but at its core, the server is just, simply, a computer. That's it. So why is it called a server? Because it serves . When you go to a website like , your computer connects to the internet and gets you your search result. But your computer's internet connection has to get that result from somewhere, right? If the google search result is giving you some answers, the answers have to come from somewhere. What is that place? The answer to that some place is: a server. When you click on the search button on google, or hit enter after typing, &q

Review: Nestjs - Finally a scalable way to build APIs

I have been thinking about this for a long time. There HAS to be a defined way to build APIs in a scalable way.  If you have used Node, Express, etc in your side projects, you might have felt that after a point in development, debugging truly becomes a pain. Sure, enterprise-level API codes are great. But a lot of times, these configurations are too much, and probably not even needed in other projects. To be honest, I haven't seen a lot of Open-Source API codes either to make a judgement on how experienced developers build their APIs. Anyway, I came across an amazing framework recently, and I think if you are coding a complex API, this should be your way to go. Nest.js Nest.js is a framework for building efficient, reliable and scalable server-side applications.  You essentially break your APIs into controllers, services, and modules, which allow you to modularize the smallest of functionalities in your endpoints or the API as a whole. Why is modularizing important? As I have talk