How to set up a solution
Learn about the different aspects of setting up your solution.
Setting up a solution that leverages Affective Computing (powered by Virtue)'s capabilities includes the following stages:
Understanding how Affective Computing fits into your solution ecosystem
The first step to getting started with Affective Computing is identifying how you want to leverage our platform's capabilities:
Identify your solution's domain and define its real-world applications.
Identify which Affective Computing by Virtue services you need.
Determine whether you need to build a solution from scratch or integrate an existing solution with Virtue's platform.
Building a blue-ocean solution
You can develop a solution that taps into a completely blue-ocean market.
"Blue-ocean" is a term that refers to new, unknown, or unexplored market spaces where innovators are not obstructed by limitations or competitors. It is an analogy that describes exploring the vast and untapped potential for growth in an uncontested market. The strategy for venturing into blue ocean markets often involves creative and transformative thinking.
Infusing emotion analysis into your solution to improve its human-centricity embodies the concept of a blue-ocean venture in the current technological landscape.
Virtue aims to help you thrive in these markets with our proprietary Affective Computing AIaaS, which helps you factor in authentic human emotions and safeguard human contributions and privacy.
Building a domain-specific solution
You can build a solution that caters to a specific domain.
Considerations when building a solution from scratch
When building a solution from scratch, it is critical to identify its goals and desired impact, carefully design its workflow, and plan and develop its components in a way that enables it to integrate with Affective Computing by Virtue.
Remember, Virtue's framework serves as the engine for providing human-centric capabilities to your solution that you can design and build based on your unique requirements.
✔️ Think about how your end-users would interact with your solution. For example, would your users use a custom app that they would need to download onto their personal devices?
Consider a digital museum guide that provides information to visitors when they explore various interactive exhibits.
This is an excellent use case for elevating user experiences by incorporating personalization. By integrating Affective Computing by Virtue, you can, for example, deliver personalized content tailored to each user's personality and emotional state when they visit specific exhibits.
You must factor in integration with Affective Computing when designing and developing this interface.
For example, this could include doing the following:
Authenticating your interface to send requests to our public APIs.
Set up a script to pass user inputs in real time from the interface to Affective Computing by Virtue through the interact_value parameter of the
Interaction/InteractAPI.
✔️ Plan how you want to collect the different physiological, behavioral, and environmental inputs (that your solution requires to achieve its goal) from users.
Consider a system designed to ensure that taxi drivers adhere to safety protocols when driving.
This is an excellent use case for tailoring preventative measures to users' individual personalities and emotional states for maximum efficiency by integrating Affective Computing by Virtue.
For example, you can monitor each driver's heart rate, identify their state of mind based on their speech, and proactively deliver actions that reinforce safety standards.
You must procure compatible devices or sensors (to collect real-time user inputs) and properly configure their integration with Affective Computing by Virtue.
For example, if your solution requires information about users' heart rates, this might include doing the following:
Procuring our recommended heart rate monitors for users.
Configuring the connection at the device's end (for example, over BLE or using an integration with your sensor's SDKs).
Authenticating the sensor to send requests to our public APIs.
Ensuring that heart rate measurements (in bpm) are sent by your sensor through the beats_Per_Minute parameter of the
Interaction/InteractAPI.
✔️ If your solution involves using simulation to validate an experience or coach an AI system, plan where and how you want to implement the virtual experience.
Consider an enhancement to apparel design practices using simulation with virtual users who have personalities cloned from that of real users.
This is an excellent use case for integrating Affective Computing by Virtue and leveraging our simulation capabilities to infuse personalization into the design process.
You must use an external 3D game engine (for example, Unreal Engine) to implement the simulation and manage the physical aspects of the virtual environment.
You might need to define workflows and other components on this external platform and must properly integrate its output channels with Affective Computing by Virtue.
For example, this could include doing the following:
Configuring components on the external platform that generate the inputs you need for your solution.
Creating interaction channels (when parameterizing your Affective Computing project) that correspond to the inputs.
Authenticating your app on the external platform to send requests to our public APIs.
Ensuring that the inputs passed to the
Interaction/InteractAPI include the respective interaction channel IDs in the interact_value parameter.
Creating and managing projects
A project is an automated application that allows you to define and adjust its parameters to implement a solution with clear objectives that delivers a high degree of personalization.
You can create and manage projects using the Portal or our public APIs.
Working with projects using the Portal
Creating a projectWorking with projects using APIs
Working with projectsParameterizing a project
Parametrization is synonymous with configuration; it refers to the initial settings that you must specify for different project components to properly set up your project(s).
Parameterization is the information architecture that generates the outcome you aim to observe through your solution.
Parametrization is a critical step when setting up your solution as it affects the overall success of the framework.
For example, before declaring (creating and configuring) a triggered action (a situation in which the solution delivers an action to an end-user in response to a specific event or condition), you must first understand the conditions of delivering the action.
When working with simulation solutions (that require two projects for raw data collection and simulation, respectively), you must keep the parameterization consistent across the projects to ensure their interconnection.
By understanding and translating your solution's real-world goals to your project parameterization and linking it to your solution's performance, you can reduce the risk of unplanned behavior when running the solution.
Parameterizing project components using the Portal
You can parameterize the following project components using the Portal, our no-code SaaS GUI platform:
You can parameterize only some project components using the Portal.
For simulation solution projects, you must parameterize additional key project components, namely Entities and Objects, that shape and determine how the simulation is implemented.
To parameterize these components and later run the simulation, you must use our APIs.
Parameterizing project components using APIs
You can parameterize the following project components through a low-code integration with our APIs:
Related information
TutorialsProject managementLast updated
Was this helpful?