@@ -100,6 +100,11 @@ to JuMP (if you will) around:
100100 18 . [[ 2017] Stochastic programming in energy systems] ( #2017-stochastic-programming-in-energy-systems )
101101 19 . [[ 2017] PowerModels.jl: a Brief Introduction] ( #2017-powermodelsjl-a-brief-introduction )
102102
103+ There are also a few related JuliaCon talks
104+
105+ 20 . [[ 2020] Crash Course in Energy Systems Modeling & Analysis with Julia] ( #2020-crash-course-in-energy-systems-modeling--analysis-with-julia )
106+ 21 . [[ 2019] Open Source Power System Production Cost Modeling in Julia] ( #2019-open-source-power-system-production-cost-modeling-in-julia )
107+
103108## [ 2024] Applied optimization with JuMP at SINTEF
104109
105110_ Speaker: Truls Flatberg @trulsf_
@@ -573,6 +578,10 @@ Well, in his [2024 talk](#2024-solving-the-market-to-market-problem-in-large-sca
573578he mentioned that Sienna now runs on problems with 150,000 buses. It's nice to
574579see progress!
575580
581+ @kdheepak 's talks at [ JuliaCon 2019] ( #2019-open-source-power-system-production-cost-modeling-in-julia )
582+ and [ JuliaCon 2020] ( #2020-crash-course-in-energy-systems-modeling--analysis-with-julia )
583+ are also about PowerSimulations.jl and go into complementary detail.
584+
576585[ _ Back to contents_ ] ( #contents )
577586
578587## [ 2017] Stochastic programming in energy systems
@@ -626,3 +635,40 @@ the various relaxations and approximations of AC power flow. This decision has
626635proven to be a very good design choice.
627636
628637[ _ Back to contents_ ] ( #contents )
638+
639+ ## [ 2020] Crash Course in Energy Systems Modeling & Analysis with Julia
640+
641+ _ Speaker: Dheepak Krishnamurthy @kdheepak_
642+
643+ <iframe width =" 560 " height =" 315 " src =" https://www.youtube.com/embed/kQNOG4tGJdg?si=QvTPbIQncBgr37Ev " title =" YouTube video player " frameborder =" 0 " allow =" accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share " referrerpolicy =" strict-origin-when-cross-origin " allowfullscreen ></iframe >
644+
645+ This is a short talk by @kdheepak about PowerSimulations.jl. The "crash course"
646+ in the title is rather apt, because it walks through how to build an run a power
647+ system optimization model in eight minutes. It was useful to watch this video in
648+ conjunction with the other PowerSimulations.jl videos such as
649+ [[ 2024] Solving the Market-to-Market Problem in Large Scale Power Systems] ( #2024-solving-the-market-to-market-problem-in-large-scale-power-systems ) ,
650+ [[ 2019] PowerSimulations.jl] ( #2019-powersimulationsjl ) , and
651+ [[ 2019] Open Source Power System Production Cost Modeling in Julia] ( #2019-open-source-power-system-production-cost-modeling-in-julia ) .
652+
653+ [ _ Back to contents_ ] ( #contents )
654+
655+ ## [ 2019] Open Source Power System Production Cost Modeling in Julia
656+
657+ _ Speaker: Dheepak Krishnamurthy @kdheepak_
658+
659+ <iframe width =" 560 " height =" 315 " src =" https://www.youtube.com/embed/1TipY6g9IzE?si=cbTPZb4Sq_Pt6zW7 " title =" YouTube video player " frameborder =" 0 " allow =" accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share " referrerpolicy =" strict-origin-when-cross-origin " allowfullscreen ></iframe >
660+
661+ This is a talk by @kdheepak about PowerSimulations.jl, which Jose Daniel
662+ [ presented at JuMP-dev 2019] ( #2019-powersimulationsjl ) . Using a small example,
663+ Dheepak goes into more detail around how PowerSimulations.jl uses Julia's
664+ multiple dispatch to build the optimization problems.
665+
666+ There was an interesting question at the end related to how we document models.
667+ @sstroemer mentioned this as well in [ his talk] ( #2023-how-jump-enables-abstract-energy-system-models ) .
668+ Stefan's answer as to write out the models in some form of abstract LaTeX. JuMP
669+ used to print out a compressed form of the model, but we changed to writing out
670+ the scalarized form during the change to MOI because the compressed form
671+ required too many hacks for work and required a lot of maintenance. I'm not sure
672+ what we should do going forward.
673+
674+ [ _ Back to contents_ ] ( #contents )
0 commit comments