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.

Sign up for GitHub

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

Jump to bottom

Splitting out the deme management part of the code into its own module? #89

Open
linas opened this issue Sep 18, 2021 · 1 comment
Open

Splitting out the deme management part of the code into its own module? #89

linas opened this issue Sep 18, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@linas
Copy link
Member

linas commented Sep 18, 2021 •
edited
Loading

I'm in the process of writing a research proposal that would need to have some kind of deme management system, similar to what ASMOSES does. This is all very much up in the air, and totally unclear, but ...

If it ever occurs to you that the deme management part of this system could be split out into it's own module, that would be a good thing. This is low priority and not urgent.

The mention of ASMOSES for deme management is here: https://github.com/opencog/learn/blob/master/README-Vision.md
@linas linas added the enhancement New feature or request label Sep 18, 2021
@linas linas mentioned this issue Aug 3, 2022
Open
@linas
Copy link
Member Author

linas commented Sep 20, 2023

See also opencog/moses#105 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@linas