I was going through the double_loop_optimization notebook (RE case study) to observe the error I was getting in the test_notebooks check (PR #220), which seemingly had to do with a deprecated style setting (i.e., using 'seaborn' for matplotlib plot style), and I noticed that cell 11 (running the double-loop plugin within Prescient simulation) resulted in a lengthy run time:
cbc is being used as the solver on my comp since I don't have gurobi at the moment, so that might be why it took 26 minutes to complete. I only raise the point because if a new user is going through this case study as a learning example, waiting a half hour for a particular cell to finish doesn't seem ideal.
I was going through the double_loop_optimization notebook (RE case study) to observe the error I was getting in the test_notebooks check (PR #220), which seemingly had to do with a deprecated style setting (i.e., using 'seaborn' for matplotlib plot style), and I noticed that cell 11 (running the double-loop plugin within Prescient simulation) resulted in a lengthy run time:
cbcis being used as the solver on my comp since I don't havegurobiat the moment, so that might be why it took 26 minutes to complete. I only raise the point because if a new user is going through this case study as a learning example, waiting a half hour for a particular cell to finish doesn't seem ideal.