-
Notifications
You must be signed in to change notification settings - Fork 113
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.
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
Setting the message model dir
does not work
#415
Comments
Thanks for this report! In order to reproduce and be sure this is fixed, can you say specifically: how does it "not work", or what are the symptoms? For example, I imagine it could be one of:
If (3), can you also give the contents of |
The command does not produce any error (with exception of a warning related pandas package - see below), but it has no effect. In other words, the original GAMS code in the Anaconda installation keeps being used (with the gdx, log and lst files materializing in the model folder of the Anaconda installation). Warning message:
|
My
PS: Note that in an earlier version of this message it said that there was no |
Thanks for the information. This should be small, so I will add it to my list before the 3.3 release. |
Sorry, I think this needs some further info to diagnose:
|
#416 introduced some tests for this functionality that seem to work, including on Windows. Remove the milestone until we have the info needed to diagnose. |
@khaeru, thanks. Related to the questions raised above:
I am realizing that under |
- Expand class docstring. - Add typing. - Don't overwrite values read from file when Config.register() is called (fixes #415).
Setting the
message model dir
via the commandmessage-ix config set "message model dir" /path/for/model/files
does not work for me. I am using the conda basedmessage_ix
installation and wanted to use the GAMS code in my working copy of themessage_ix
repository to allow making changes to the GAMS code.Problem description
I ran the following command in the Anaconda command line so that
message model dir
points to the model folder of my working copy.I also tested the
message-ix copy-model
command which in principle did most of what I was expecting it to do with the exception of copying the files directly sitting in themodel
directory (e.g.,MESSAGE_run.gms
) which would be important as modifications could also be relevant there.Versions
Below is the version information for
ixmp
andmessage_ix
:The text was updated successfully, but these errors were encountered: