Translations:Gurobi/44/en: Difference between revisions

From Alliance Doc
Jump to navigation Jump to search
(Importing a new version from external source)
(Importing a new version from external source)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
If it returns "Success" then you can being using gurobi immediately.  If it returns "Fail" then contact [[Technical_support | contact support]] for help.
If it returns "Success" you can begin using Gurobi immediately.  If the test returns "Fail" then check whether a file named <i>~/.license/gurobi</i> exists; if so, rename or remove this file, reload the module and try the test again.  If it still returns "Fail", check whether there are any environment variables containing GUROBI defined in either of our your <i>~/.bashrc</i> or <i>~/.bash_profile</I> files.  If you find any, comment or remove those lines, log out and log in again, reload the Gurobi module and try the test again.  If you still get "Fail", [[Technical_support | contact support]] for help.

Latest revision as of 13:26, 9 July 2024

Information about message (contribute)
This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.
Message definition (Gurobi)
If it returns "Success" you can begin using Gurobi immediately.  If the test returns "Fail" then check whether a file named <i>~/.license/gurobi</i> exists; if so, rename or remove this file, reload the module and try the test again.  If it still returns "Fail", check whether there are any environment variables containing GUROBI defined in either of our your <i>~/.bashrc</i> or <i>~/.bash_profile</I> files.  If you find any, comment or remove those lines, log out and log in again, reload the Gurobi module and try the test again.  If you still get "Fail", [[Technical_support | contact support]] for help.

If it returns "Success" you can begin using Gurobi immediately. If the test returns "Fail" then check whether a file named ~/.license/gurobi exists; if so, rename or remove this file, reload the module and try the test again. If it still returns "Fail", check whether there are any environment variables containing GUROBI defined in either of our your ~/.bashrc or ~/.bash_profile files. If you find any, comment or remove those lines, log out and log in again, reload the Gurobi module and try the test again. If you still get "Fail", contact support for help.