-
Notifications
You must be signed in to change notification settings - Fork 18
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
Smart AgentBasedSimulation #72
Comments
rusu24edward
modified the milestones:
Coming... eventually,
Coming soon!,
...Probably not
Aug 5, 2022
For built-in components, we can create a component registry in the GWSF that maps a component's name to itself. Then we can support a builder that takes component names as input and builds out the simulation from there. A rough idea of the code might look something like this:
Then the user can just supply component names instead of having to redefine a new simulation entirely. Outstanding questions:
|
This was referenced Aug 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The environments we design are completely based what we include in the init, namely which components to use. We should make a smart super class that can fill out the rest of the functions, like reset, step, get_obs, etc. based on what we create in the init and some order that we specify for step.
Furthermore, we shouldn't have to make a separate simulation just because a different component is used. So we should think of ways to support varying the components without the user having to redefine the simulation.
Depends on #58
The text was updated successfully, but these errors were encountered: