Hi again,
GAMS 45.6.0 was released yesterday. It comes with GAMS Studio 1.16.4 which contains the bug fix. Thanks again for reporting.
Best,
Clemens
Search found 57 matches
- 2 months ago
- Forum: Bugs
- Topic: GDX Export in Studio
- Replies: 2
- Views: 13379
- 3 months ago
- Forum: Bugs
- Topic: GDX Export in Studio
- Replies: 2
- Views: 13379
Re: GDX Export in Studio
Hi Rob,
Indeed this is a bug. We are going to publish a fix for this as soon as possible. Thanks for reporting.
Best,
Clemens
Indeed this is a bug. We are going to publish a fix for this as soon as possible. Thanks for reporting.
Best,
Clemens
- 2 years ago
- Forum: API
- Topic: ModuleNotFoundError: No module named '_gams2numpy'
- Replies: 9
- Views: 44314
Re: ModuleNotFoundError: No module named '_gams2numpy'
Jan,
With setuptools>=60.0.0 a breaking change has been introduced. Due to this breaking change the GAMS Python files are not installed correctly. To solve the issue, please try setting SETUPTOOLS_USE_DISTUTILS=stdlib before running setup.py
Let me know if this helps,
Clemens
With setuptools>=60.0.0 a breaking change has been introduced. Due to this breaking change the GAMS Python files are not installed correctly. To solve the issue, please try setting SETUPTOOLS_USE_DISTUTILS=stdlib before running setup.py
Let me know if this helps,
Clemens
- 2 years ago
- Forum: Syntax
- Topic: Running NEOS from Python API
- Replies: 7
- Views: 7612
Re: Running NEOS from Python API
I assume that the error is the same when running Kestrel from command line. So it seems that setting the SSL_CERT_FILE in [GAMS dir]\gmske_nt.cmd is not enough. If you allow me an experiment, could you change the following line of code in [GAMS dir]\gmske_nx.py (line 537): self.neos = xmlrpc.client....
- 2 years ago
- Forum: Syntax
- Topic: Running NEOS from Python API
- Replies: 7
- Views: 7612
Re: Running NEOS from Python API
Hi, It seems that the Kestrel solver uses an invalid certificate. Actually it should be aware of cacert.pem located in [GAMS dir]\GMSPython\Lib\site-packages\certifi. Does the Kestrel solver work from command line, if you do not have a Python script in between? There is also a Python example that de...
- 2 years ago
- Forum: API
- Topic: Python API error message
- Replies: 2
- Views: 5959
Re: Python API error message
Pei Huang, The PKG installer on macOS allows to add the GAMS system directory to the PATH variable when a Terminal is opened. You might want to double-check its content using echo $PATH , but since you are able to call gams and gamslib, I guess that this is set up correctly. If you run the python in...
- 3 years ago
- Forum: API
- Topic: unhashable type: 'GamsSetRecord'
- Replies: 2
- Views: 4690
Re: unhashable type: 'GamsSetRecord'
Looks like you are trying to use your dictionary qta with GamsSetRecords instead of keys. So you most likely want to do qta[(j.key(0),k.key(0))] instead of qta[(j,k)]
Best,
Clemens
Best,
Clemens
- 3 years ago
- Forum: API
- Topic: Matrix to GDX from Python
- Replies: 3
- Views: 5235
Re: Matrix to GDX from Python
I can not say anything about csr_matrix in particular, but if possible, you can skip the zeros of any sparse matrix representation when writing to an instance of GamsParameter. Filling data using the Object-oriented Python API always works record based by calling my_symbol.add_record([key1, key2,......
- 3 years ago
- Forum: API
- Topic: Matrix to GDX from Python
- Replies: 3
- Views: 5235
Re: Matrix to GDX from Python
Hi, You can represent the matrix as a 2-dimensional GAMS parameter using the following code: from gams import * A=[[0., 0., 0., 0., 0.], [0., 0., 0., 0., 0.], [0., 0., 0., 0., 0.], [0., 0., 0., 1., 0.], [0., 0., 0., 0., 1.]] ws = GamsWorkspace(".") db = ws.add_database('data') mat = db.add...
- 4 years ago
- Forum: API
- Topic: Python 3.7
- Replies: 1
- Views: 3954
Re: Python 3.7
Renger, First of all we need to distinguish between the use of the GAMS Python API and the GAMS Embedded Code Facility . While the GAMS Python API is provided for different version of Python, the Embedded Code Facility requires a Python 3.6 right now. The error message comes from the setup.py script...