BEL can fail trace without triggering error #99
Conversation
|
@SWRIganderson , got it! |
| @@ -232,24 +238,32 @@ impl LocomotiveSimulation { | |||
| self.loco_unit | |||
| .set_cur_pwr_max_out(None, self.power_trace.dt(self.i))?; | |||
| self.solve_energy_consumption( | |||
| self.power_trace.pwr[self.i], | |||
| if self.allow_trace_miss { | |||
There was a problem hiding this comment.
@SWRIganderson , this did it!
There was a problem hiding this comment.
@calbaker I'll check this out tonight.
|
@calbaker Thanks for getting this pulled off. The optional powertrace constraint works well. I was able to mess with it this weekend. It fails when it should, and does not fail when it shouldn't. I have a modified BEL example that I would like to include in ALTRIOS, but its probably needs to be cleaned up a bit. I will be committing it in the next couple of days once I get things dressed up for slides for the meeting on wednesday. The other thing that I think we should change is to make the allow_trace_miss argument an optional one with a default to false. I think this is a really useful argument that could easily shoot someone in the foot if they don't get it right. Let me know what you think about this. |
…o powertraces to demonstrate a potential pathway to identify optimal bel route deployment from event recorder data.
|
@SWRIganderson , I'd recommend putting your working BEL demo that shows trace miss working in |
… into fix/97-allow-bel-trace-miss
added PyYAML
solves #97