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

ScenarioProcessor could be simpler/removed #36

Open
joeha480 opened this issue Dec 15, 2017 · 0 comments
Open

ScenarioProcessor could be simpler/removed #36

joeha480 opened this issue Dec 15, 2017 · 0 comments

Comments

@joeha480
Copy link
Contributor

ScenarioProcessor evaluates different scenarios for efficiency and chooses the most efficient one for further processing (the following interations). However, the way it's implemented is perhaps not optimal, because it is quite complicated and difficult to follow. An easier way of doing this would be to simply copy the results and evaluate a scenario on that copy, and then compare that to the baseline efficiency. Then use the best copy for the rest of the processing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant