-
Notifications
You must be signed in to change notification settings - Fork 37
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
saving a copy of _dd_.gdx #4
Comments
Thanks. The saving of this file is already done at compile time. Only the renaming is done at execution phase, and that is because of the rename with a timestamp. There is no standard use case for a restart file being created from TIMES, and so the compile and execution phases would occur at the same time under all normal use cases. However, if you can show how to conveniently create the timestamp at compile time (such that works both under latest and older GAMS versions), doing also the rename at compile time as you suggested will be implemented according to your suggestion. Thanks for contributing to improving TIMES. |
You can access the time routines via
|
Thanks for the proposed method. |
Here is a streamlined variant I tested on Windows, hopefully this would work also on Linux:
|
I can confirm that this works also on Linux. |
This change (compile time rename of the data-only gdx file) will be in the next release. I know one user, @kanors-emr , who I expect to be affected by it, due to somewhat "non-standard" modes of usage, and therefore notified hereby in advance. |
In
prepxtra.mod
aput_utility 'shell'
is used to rename the_dd_.gdx
file and store it in a different location with a file name that contains some kind of time stamp. This saving of the_dd_.gdx
which is created and handled at compile time is done at execution time. Due to GAMS save/restart capabilities the compile and execution phase can happen at very different times and even on different machines. It would be cleaner if the saving of this file is done in the compilation phase of GAMS.The text was updated successfully, but these errors were encountered: