Send eesyplan simulation request

[Bachibouzouk]

Sends a request to the simulation server

• send a request via URL (http://127.0.0.1:8000/en/topology/ezp_simulation/<scen_id>)
• send a request via a button in frontend
• modify Simulation to add a ezp_token in addition to mvs_token
• make the user know which server was chosen (for debugging)
• ? let the user choose between MVS and EZP ?

[paulapreuss]

Looks good. I guess if in a first step we want to allow the user to choose between MVS and EZP, it would make to write a results parser that is analogous to the mvs results.

gui/app/projects/requests.py

Line 134 in 2222a53

def parse_mvs_results(simulation, response_results):

However, I guess that at the point where we start constructing the graphs from eesyplan instead, it might no longer make sense to handle them the same way? If we end up restructuring the way that graphs and results are displayed to come from eesyplan instead, we need to make sure we also keep backwards compatibitility with the projects having only the original Results database objects.

[paulapreuss]

In case we might also want to switch between prod and dev queues in staging/production in the future, I think it makes sense to add an environment variable for it to the EZP_POST_URL string (similar to how it is now for MVS_POST_URL)

[paulapreuss]

Yes, this looks like what I was thinking also. I think it is a good idea to save the datapackage into a new field of the Simulation object, maybe we could extend scenario.to_datapackage to take strip_timeseries=True/False or similar (which then replaces the timeseries with foreignkeys), then save json_dp.

[Bachibouzouk]

@paulapreuss - I think setting n_timestamps to 0 is equivalent (I notice I wrote number instead. My bad)