-
Notifications
You must be signed in to change notification settings - Fork 926
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
Remove schedulers from benchmark models. #2308
Conversation
for more information, see https://pre-commit.ci
Performance benchmarks:
|
Performance benchmarks:
|
I don’t understand how BoltzmannWealth gets slower while doing less (being already on Probably just a fluke. |
Performance benchmarks:
|
I think it has to do with the data collection in the Boltzman wealth model. I need to dig deeper to confirm. |
My hunch is correct. The old boltzman wealth model contained a bug. It used a schedule but no agents were added to it. The datacollecter then collected data from the agents in the schedule (which were None). So, the new benchmark is correct. Also, this means that the deprecation of schedules should result in an update to the datacollector. In fact, I think the entire agent_collector can be deprecated in favor of the new agent type stuff. |
Yeah, that's correct, you can also see it in #2300. These two are completely equivalent: self.datacollector = DataCollector(
agent_reporters={"energy": "energy"},
agenttype_reporters={
Agent: {"energy": "energy"}
} We will redesign this whole thing any way. Let's leave the API alone for now. Implementation wise, these parts could be updated as soon as the schedulers are actually removed. Lines 231 to 237 in e6874ad
In between we could add a warning. But I don't think that's easy or worth it. This PR is good to go! |
this removes the schedulers from the benchmark models (in one case it was in the init but not used in step anyway).