Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

getsolvetime in JuMP 0.19 #1891

Closed
anelkawang opened this issue Mar 8, 2019 · 3 comments
Closed

getsolvetime in JuMP 0.19 #1891

anelkawang opened this issue Mar 8, 2019 · 3 comments
Labels
good first issue This issue is recommended for new users, it does not require a thorough understanding of the package Status: Help Wanted Help is welcome on this issue Type: Documentation

Comments

@anelkawang
Copy link

In the previous JuMP version, there is a "getsolvetime" function to get the solving time. Is there a similar functions in JuMP 0.19? I haven't found the descriptions in the document. Thank you.
@blegat
Copy link
Member

blegat commented Mar 9, 2019

You can do MOI.get(model, MOI.SolveTime())

@blegat blegat added good first issue This issue is recommended for new users, it does not require a thorough understanding of the package Status: Help Wanted Help is welcome on this issue labels Mar 30, 2019
@blegat
Copy link
Member

blegat commented Mar 30, 2019

We should add a solve_time function, this is a good first issue for new contributors.

@guilhermebodin guilhermebodin mentioned this issue Apr 8, 2019
Merged
@mlubin
Copy link
Member

mlubin commented Apr 13, 2019

Implemented in #1928

@mlubin mlubin closed this as completed Apr 13, 2019
@blegat blegat mentioned this issue May 5, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue This issue is recommended for new users, it does not require a thorough understanding of the package Status: Help Wanted Help is welcome on this issue Type: Documentation
Milestone
No milestone
Development

No branches or pull requests
3 participants
@blegat @mlubin @anelkawang