Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
personal:blog:2017:0203_jump_for_gams_users [2023/12/22 11:24]
antonello [Declaration of the model]
personal:blog:2017:0203_jump_for_gams_users [2023/12/22 11:37]
antonello [Further help] COMPLETED UPDATING OF THE PAGE
Line 196: Line 196:
 ==== Resolution of the model ==== ==== Resolution of the model ====
  
-It is at this point that the solver is called and the model is passed to the solver engine for its solution. The return value is the status of the optimisation (":Optimal" if all went fine)+It is at this point that the solver is called and the model is passed to the solver engine for its solution. The return value is the status of the optimisation (''MOI.OPTIMAL'' if all went fine)
  
 <code julia> <code julia>
-status = solve(trmodel)+optimize!(trmodel) 
 +status = termination_status(trmodel)
 </code> </code>
  
Line 207: Line 208:
  
 <code julia> <code julia>
-if status == :Optimal +if status == MOI.OPTIMAL 
-    println("Objective value: ", getobjectivevalue(trmodel)) +    println("Objective value: ", objective_value(trmodel)) 
-    println(getvalue(x))+    println("Shipped quantities: ") 
 +    println(value.(x))
     println("Shadow prices of supply:")     println("Shadow prices of supply:")
-    [println("$p = $(getdual(supply[p]))") for p in plants]+    [println("$p = $(dual(supply[p]))") for p in plants]
     println("Shadow prices of demand:")     println("Shadow prices of demand:")
-    [println("$m = $(getdual(demand[m]))") for m in markets]+    [println("$m = $(dual(demand[m]))") for m in markets] 
 + 
 else else
     println("Model didn't solved")     println("Model didn't solved")
Line 223: Line 226:
 ==== Editing and running the script ==== ==== Editing and running the script ====
 Differently from GAMS you can use whatever editor environment you wish to code a JuMP script. If you don't need debugging features, a simple text editor like Notepad++ (in windows), gedit or kate (in Linux) will suffice. They already have syntax highlight for Julia.\\ Differently from GAMS you can use whatever editor environment you wish to code a JuMP script. If you don't need debugging features, a simple text editor like Notepad++ (in windows), gedit or kate (in Linux) will suffice. They already have syntax highlight for Julia.\\
-If you want advanced features and debugging capabilities you can use a dedicated Julia IDE, like e.g. [[http://junolab.org/|Juno]].+If you want advanced features and debugging capabilities you can use a dedicated Julia IDE, like the [[https://www.julia-vscode.org/|Julia extension for VSCode]].
  
-If you are using instead the Julia console,  you can run the script as ''julia transport.jl''.+If you are using instead the Julia terminal,  you can run the script as ''julia transport.jl''.
  
 ===== Further help ===== ===== Further help =====
-Documentation of JuMP is available from [[https://jump.readthedocs.io/en/latest/|this page]]. However if you want to do serious things with juMPit is most likely that you will have to either look at the source code or consult the [[https://discourse.julialang.org/c/domain/opt|discussion forum]].+Documentation of JuMP is available from [[https://jump.dev/|this page]], and community-based support is available on [[https://discourse.julialang.org/c/domain/opt|the Discourse forum]].
  
 Happy modelling with JuMP ;-) Happy modelling with JuMP ;-)
personal/blog/2017/0203_jump_for_gams_users.txt · Last modified: 2023/12/22 11:39 by antonello
CC Attribution-Noncommercial-Share Alike 4.0 International
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0