Skip to main content

CloudEnv deprecation

Answered
Paul Costache
Edited
  • Gurobi-versary
  • First Comment
  • First Question

Hello ! I was just playing with one model and it throws an error:

CloudEnv is deprecated, use Env(params={...}) instead

This is how I initially used CloudEnv:

 

``env=gp.Env.CloudEnv(logfilename="", accessID=GUROBI_ACCESS_ID, secretKey=GUROBI_SECRET_KEY)``

Now, I have tried the following, but to no avail:

       ` `env=gp.Env(params={"logfilename":"", "accessID":fr"{GUROBI_ACCESS_ID}", "secretKey":fr"{GUROBI_SECRET_KEY}"})``
 
I have tried to look up the deprecation warning in the docs but didnt find anything. What is the new correct syntax ? Thanks !
 

 

1

Comments

7 comments

Date Votes
  • Official comment
    Ronald van der Velden
    • Gurobi Staff

    Hi Paul,

    The parameter names to use are slightly different than the parameters to the original `CloudEnv` function. The syntax looks like this:

    params = {
    'CloudAccessID': '...',
    'CloudSecretKey': '...',
    'CloudPool': '...'
    }
    e = gp.Env(params=params)

    Best regards,
    Ronald

  • Official comment
    Simranjit Kaur
    • Gurobi Staff
    This post is more than three years old. Some information may not be up to date. For current information, please check the Gurobi Documentation or Knowledge Base. If you need more help, please create a new post in the community forum, or try Gurobot, our chatbot interface offering instant, expert-level support.
  • Paul Costache
    • Gurobi-versary
    • First Comment
    • First Question

    Thank you sooo much Ronald ! Have been digging in your manual and API reference for ages now !!

    0
  • Ronald van der Velden
    • Gurobi Staff

    Sorry about that... the parameter names to be used as dictionary keys with this syntax are basically the official parameter names listed here. But I understand it can be confusing in the context of this deprecation message!

    0
  • Paul Costache
    Edited
    • Gurobi-versary
    • First Comment
    • First Question

    Additionally, are there any other changes to the API ? That's because a previously working model now spits 'the JSON object must be str, bytes or bytearray, not tuple'. Thank you !

    0
  • Ronald van der Velden
    • Gurobi Staff

    Not sure... could you post a code snippet that illustrates the error?

    0
  • Paul Costache
    • Gurobi-versary
    • First Comment
    • First Question

    It comes from a seemingly unrelated variable declaration. It's a bit weird because it worked a few days ago:

    list_materials=json.loads(list_materials)['data'].
    It probably is a mistake of mine so I will look further into each data structure !  Thanks !
    0

Post is closed for comments.

Didn't find what you were looking for?

New post