Jody Dillon comments

Results 75 comments of


                                            Jody Dillon

setting of fixed_om_costs severly limiting modeling horizon/performance

@Tasqu this seems like a low hanging fruit performance-wise - but does it give us clues how to improve things more generally?

setting of fixed_om_costs severly limiting modeling horizon/performance

One of the things I think we should do is implement higher level switches ... for example if particular parmeters are not defined or used at all, there is no...

setting of fixed_om_costs severly limiting modeling horizon/performance

@OliverLinsel that's consistent with what we have found. However, this isn't the same as creating a pre-compiled system image for SpineOpt. If you do this, then you get the improved...

Update variable and constraint names after rolling

Ah - is there a cheap way to fix this behaviour?

Update variable and constraint names after rolling

I was referring to performance rather than coding effort :-)

Update variable and constraint names after rolling

There may be issues when you want to use the conflict resolution functionality to diagnose infeasibilities - that's actually the reason I implemented to constraint names to begin with

Update variable and constraint names after rolling

There is the `compute_conflict!` JuMP function... but the constraint names were for originally identifying infeasibilities reported by the solver

Update variable and constraint names after rolling

I not sure... perhaps a long run would die midway through because of an infeasibility - it would be a pity then, to have to change some parameters and rerun...

Update variable and constraint names after rolling

That sounds good

Rename time-slice relationships for more clarity.

I thought in the renaming we were going to better capture that it can work in both directions... i.e. with `t_consecutive_t(t_before=t1)` you get the next t, but if you call...