You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, trying to follow this tutorial on qiime2 micom testing with gurobi optimization.
The software was installed in a shared filesystem. A different user than the person who installed the software ran the following miicom tradeoff command:
problem = gurobipy.read(tmp_file_name)
File "src/gurobipy/gurobi.pxi", line 3779, in gurobipy.read
File "src/gurobipy/gurobi.pxi", line 112, in gurobipy.gurobi.read
File "src/gurobipy/gurobi.pxi", line 60, in gurobipy.gurobi._getdefaultenv
File "src/gurobipy/env.pxi", line 70, in gurobipy.Env.__init__
gurobipy.GurobiError: User name mismatch (licensed to '[email protected]', current user is '[email protected]')
The issue does not occur when the user who installed the package is running the software. Can more than one user run the software? In other words can I add more than one user into the license file? Can I give more than 1 hostname? Because we are working on an HPC cluster.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi, sorry for the late reply (vacay). Personal licenses can not be shared as far as I know. You could try with a WLS license or a site license. For HPC/docker we usually use the WLS license, though you will have to renew it regularly.
Problem description
Hi, trying to follow this tutorial on qiime2 micom testing with gurobi optimization.
The software was installed in a shared filesystem. A different user than the person who installed the software ran the following miicom tradeoff command:
The user got the following error:
The issue does not occur when the user who installed the package is running the software. Can more than one user run the software? In other words can I add more than one user into the license file? Can I give more than 1 hostname? Because we are working on an HPC cluster.
Thanks!
The text was updated successfully, but these errors were encountered: