Release notes

Learn about the new features and enhancements available in the current and previous releases of Affective Computing

(Current version) 1.3.2.3

Released on 28-Oct-2024

The following new features are available in this version:

Ability to view the number of perceptions a VH required for evolution

A new integer type response parameter, perceptions, is available for the Psychological Evolution API to help you gain additional insights about psychological evolution.

If an evolution is observed, this parameter, which is nested in the sessions array in the response, displays the number of perceptions that the respective Virtual Human (VH) experienced.

For detailed information, see Analyze the psychological evolution of VHs during a simulation.

Ability to share users and VHs across projects

You can summon and interact with users and VHs from different projects of the same tenant.

To facilitate this, we have added a new required parameter, ProjectID, to the Interaction/SummonNPC API endpoint, in which you must enter the project ID of the VH that you want to summon.

For API documentation, see Summon a VH.

Entering the project ID is no longer mandatory for the following endpoints of the DestinationEntity API:

• CreateEntities

• GetAllEntities

• UpdateEntity

• DeleteEntity

When calling these APIs, passing values for the ProjectID parameter does not serve any purpose.

For API documentation, see Creating and managing entities.

Performance improvements

We have enhanced our APIs and microservices to optimize the performance and response time of the following events that occur during bulk simulation:

• Starting data augmentation

• Summoning VHs

Additional validation and improved error handling

To improve your experience in working with Orchestra APIs, we have added additional validations at different stages and included relevant HTTP 400 errors, complete with standardized error codes and descriptive messages, to help you debug your issues.

For the complete list of error codes and messages and their detailed explanations, see Error messages.

The following validations are available:

• After the raw data collection (RDC) event is completed, before starting data augmentation for bulk simulations, we validate that the RDC included a minimum of 100 stages. If it didn't, ER0088 is displayed.

• When summoning VHs, first, we validate that the VHs aren't offline (killed). If you try to summon an offline VH, ER0084 is displayed. Then, as you can directly use an VH that is active and online without summoning it again, if you try to summon an active VH, ER0085 is displayed.

• To help you avoid incorrectly summoning and using VHs in interactions, we have also included a number of new validations and corresponding errors related to specific incorrect use cases. For example, we validate if you are trying to perform an interaction with a VH that was never summoned, if you entered an invalid entity ID for a VH, and more.

Previous releases

Version	Release notes	Summary
1.3.2	1.3.2.2	Enhancements to the Interaction/PsychologicalEvolution API to provide clear indicators of Virtual Humans' psychological evolution Tier-based data limits and maintenance protocols Ability to create input interaction channels based on environmental objects Additional validation and improved error handling Support for retrying connection requests from gRPC clients
	1.3.2.1	Uniform API response structure Improved error messaging Support for a minimum of 2 participants in group interactions
1.3.1	1.3.1.1	Support for group interactions: New Interaction/group/InitializeInteraction API for initializing group interactions New Interaction/group/DissolveInteraction API for ending group interactions New group_ID parameter in the Interaction/Interact API to implement group interactions New next_Participant_InteractionSession parameter in the Interaction/Interact API to specify the next participant in directed group interactions New Interaction/PsychologicalEvolution API to gain insights about the psychological evolution of Virtual Humans during simulation. New interaction_identifier response attribute in the Interaction/Interact API to identify successful interaction requests Ability to manually verify actions using the new FeedingData/VerifyActions API Validation of values entered in parameters when creating projects, logics, and actions and initializing interaction sessions.
	1.3.1	Enhancements to IAS to improve conversations based on action feeding, data augmentation, and third-party LLM integrations Enhancements to actions All responses now pass grammar corrections before delivery All actions are kept secret (delivered by EDAA™ only for logics defined within the project) by default New Interaction/StartDataAugmentation_bulk API to perform data augmentation for bulk simulation New project_Purpose parameter in the Project/Create API to specify a new project's purpose Ability to specify simulation_bulk as the project's purpose Ability to create and manage diagnostics logics using the APIs in the new logicDiagnostics collection Ability to enable or disable product calibration mode using the new Project/ActivateProductCalibration and Project/DeactivateProductCalibration APIs respectively.
1.3.0	1.3.0	Removed the requirement to input physiological data in simulation projects Ability to send text responses to EDAA™ (instead of only audio) New (optional) feedingDataId parameter in the Interaction/Interact API to inform EDAA™ about actions that occur during data collection New Interaction/BroadcastAction API to inform VHs about an action performed by another VH that impacts them. EDAA™ only responds with logic actions in data collection projects. Performance improvements: Fixed issues in summoning entities Fixed issues with interactions by the environment in simulation projects Improved the platform's overall response time