Open nickolasclarke opened 4 years ago
The kWh range on these is pretty big! Do you know why?
Do you know what "Power" means in the context of the buses?
@r-barnes Re kwh: I think its simply different bus models and perhaps more importantly the year of development. I think some of those listed are pretty old, mostly novelty models. BYD and Proterra have a significant portion of the market I believe, so they should serve as a good baseline for what would be expected in the field.
Re Power: I believe on that graphic it is the rate of charge it can accept. It seems unlikely from the context that it is the motor output. Forgot to cite that image, I'll see if I can track it down.
@r-barnes sorry, I forgot gh doesnt render latex in markdown.
I think it would be reasonable to transform the bus data into a YAML file, which we can later parse with YAML.jl.
Maybe CSV is better: the table format makes things easier to read and manipulate.
Basic Costs / Inputs:
Archived Version
Modeling Objective: Minimize the cost of an EV bus deployment
Optimization
min $\sum^{n}_{i=1}x_i$ subject to $g_i(x)$ and $h_j(x)$
Decision Variables
The decisions the model is making, in order to minimize our costs.
These are all discrete integers, but I think that they could be treated as continous and simply round up to the nearest int value.
Inequality Constraints (a ranged constraint) $g(x)$
note: I think all of these could be set as equality constraints instead, and addressed through scenarios
Equality Constraints (fixed constraint) $h(x)$
Scenario runs
For each feed, the model should be run with a minimum of high/medium/low values for the relevant equality constraints. This would result in a combinations table of all possible scenarios. We can add more nuance to this 3
cite