Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update flow through AI constructs #120

Closed
asgibson opened this issue Feb 16, 2024 · 1 comment · Fixed by #122
Closed

Update flow through AI constructs #120

asgibson opened this issue Feb 16, 2024 · 1 comment · Fixed by #122
Assignees
Labels
convention Repository coding and documentation standards enhancement New feature or request

Comments

@asgibson
Copy link
Contributor

The current flow of low-level and high-level data through the constructs is not how it should be.
Learners do not access high-level data results from Knowledge constructs.
Planners are not currently updated or allowed to render reason.
Complex reasoners are unable to see high-level data from previous complex reasoners.

In addition, Knowledge constructs are having render reason called too many times and in an odd order.
Knowledge constructs will all update, then reason.
Learners will all update, then reason.
Planners will all update, then reason.
Complex reasoners will individually update and reason prior to the next complex reasoner updating and reasoning.

@asgibson asgibson added enhancement New feature or request convention Repository coding and documentation standards labels Feb 16, 2024
@asgibson asgibson self-assigned this Feb 16, 2024
@asgibson asgibson linked a pull request Feb 23, 2024 that will close this issue
@asgibson
Copy link
Contributor Author

The |= operator used in complex reasoners:

intelligent_outcomes['complex_systems'] |= {plugin.component_name:plugin.render_reasoning()}

Has only been in Python since 3.9. Because of the recent decision to provide more backward compatibility for Python versions, this needs reverted to use the dict function update instead of the |= operator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
convention Repository coding and documentation standards enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant