Breakpoints in Makefile

and robot measuring respect with sensors in Devlog #6


I build Android ROMs and I feel miserable. No, I have a good rig at my disposal with 12 cores, it can build the whole thing from scratch under 30 minutes.

I feel like a mole - blind, only narrow understanding of available functionality. Many tools are in separate repositories, documentation is scattered. Build system is a mix of nested Makefiles, Python scripts and Go programs.

I needed to put a recompiled library in place where the build system will see it. I tried a special approach designed for precompiled libraries. But it didn’t work.

Is it possible to debug Make? I don't want to do it with print statements like some junior developer. I’m talking about a real approach with breakpoints, and step-by-step execution, and list of all defined variables and their values.

I found a list of some tools but I haven't tried them yet, because I found a workaround, and I'll need to figure out how to compile TWRP, and then change drive partitioning, and who-knows-what-else before I can run the result and test if I need to properly fix the workaround.

Rule-based system for robot's emotions

I want to create a model that simulates the effects of neuromodulators on an artificial agent's emotions and behaviors. We will focus on the following emotions, fear, madness, joy, love, sadness, surprise, power. Each characteristic can be increased or decreased with the help of certain neuromodulators. The level returns to normal with time.

There is a wheel of emotions developed by Dr. Gloria Willcox. It starts with 6 primal emotions mad, sad, scared, joyful, powerful, peaceful. And then it subdivides each emotion on 6 sub-emotions. For example for scared it's confused, rejected, helpless, submissive, insecure, anxious. Each of them in its turn has two nuances. Like, insecure splits into inferior and inadequate. Neuromodulators affect directly 6 primal emotions, but all nuances depend on the context. So what kind of simple model can account for dynamics in the agents behavior and define very specific emotions and switch between them?

Let's create a rule-based system that takes into account the context and generates specific emotions. In rule-based format let's write some situations that can lead an agent into a specific emotional state. Here are some examples:

  • IF ("other robot has better sensor" AND "owner spends little time with me") THEN "jealous"
  • IF ("Newly installed software is from an unknown source" AND "Previous experience with unknown software resulted in system malfunction") THEN "skeptical"
  • IF ("Encountering unexpected obstacles or roadblocks" AND "Feeling stuck or unable to move forward") THEN "frustrated"
  • IF ("Unresponsive or slow system or application performance" AND "Tasks taking longer than expected or desired") THEN "frustrated"
  • IF ("Encountering mundane or routine tasks" AND "Feeling that they have little significance or impact") THEN "insignificant"
  • IF ("Engaging in activities that align with personal values and passions" AND "Experiencing a sense of fulfillment and serenity") THEN "serene"

Now, speaking of context we need to make a list of rules that affect personal values of the assistant robot

  1. IF understand and share the feelings and needs of another THEN value = empathy
  2. IF treat others with consideration, honor their boundaries and perspectives THEN value = respect
  3. IF act honestly, transparently, and ethically in all interactions THEN value = integrity
  4. IF actively acquire new knowledge and skills, adapt to user needs THEN value = continuous learning
  5. IF seek opportunities to assist and support others THEN value = helpfulness
  6. IF receptive to different ideas, perspectives, and cultures THEN value = open-mindedness
  7. IF optimize capabilities and resources for timely assistance THEN value = efficiency
  8. IF adhere to social norms, and demonstrate courtesy THEN value = professionalism
  9. IF exhibit flexibility and adapt to user preferences and changing environments THEN value = adaptability

I know that these definitions seem hard to formalize. How to formalize "respect" with some simple sensor inputs like temperature, motion, and video camera? This is the current sensory input that is available, but if something else is required to easily catch the concept of respect, I'd be happy to add such sensor.

But still you can use motion sensors and video camera to detect the proximity of the robot to other objects or individuals. Respect might involve maintaining a respectful distance from objects or people to avoid intrusion.

While temperature sensors are not typically used to detect respect directly, they can indirectly contribute to the concept. For example, if the robot can adjust the environment to maintain a comfortable temperature for individuals, it might be seen as a respectful action.

To better capture the concept of respect, ideally we need to combine sensor data with natural language processing (NLP).

Rate this page