Diego Alejandro Tejada Arango

Results 89 comments of Diego Alejandro Tejada Arango

After discussion with @g-moralesespana we should not add this constraint because it is worse for the MIP. The minimum up/down time should be set by default to 1 always to...

The main takeaways from the hackathon in the WP4 (MOPO project): - The stochastic scenario vintage in the current branch does not support if the `lifetime` changes among scenarios (maybe...

List of existing tests (marked if it passes): - [x] data_structure/migration.jl - [x] data_structure/check_data_structure.jl - [x] data_structure/preprocess_data_structure.jl - [ ] data_structure/temporal_structure.jl: it fails due to the long/short history - [x]...

Add new tests for the following: **objective** - [ ] objective/unit_fixed_om_costs.jl - [ ] objective/storage_fixed_om_costs.jl - [ ] objective/connection_fixed_om_costs.jl - [ ] objective/unit_decommissioning_costs.jl - [ ] objective/unit_mothballing_costs.jl - [ ]...

Hi @manuelma, thanks for the comments; we really need a deep review and understanding of the changes. So, we need more discussion about the changes and refactoring to improve readability...

> > Hi @manuelma, thanks for the comments; we really need a deep review and understanding of the changes. So, we need more discussion about the changes and refactoring to...

@tarskul I can help with that part. A "vanilla version" of the mathematical formulation is a better approach for new users. Then, the users have the sections for Temporal and...

@manuelma it looks much readable, thanks! This will help future users. I suggest a slight change if you agree it is functional. We can be more verbose in the conditions...