DEPRECATED - Moved to VSCode → https://github.com/chrispahm/gams-ide
A GAMS IDE plugin for Atom. Provides a compilation checker for your GAMS models,
a sidebar for symbol investigation/navigation, and a data panel. Also supports listing files (.lst).
When you run into issues or bugs, please be so kind and submit an issue here on GitHub, or write a short mail.
You can install from Settings view (shift-comma) by searching for linter-gams.
Alternatively, you can install through the CLI by running:
apm install linter-gams
In order to function properly, linter-gams needs a valid GAMS executable. It will check for the latest GAMS version found in the PATH variable and the default install directories (Win: C:/GAMS/*/*/, N:/soft/GAMS*/, OSX: /Applications/GAMS*/sysdir/, /Applications/GAMS*/Resource/sysdir/).
If no installation was found in the default directories, you need to specify one in the packages settings pane (as shown in the picture above). Linter-gams runs on top of a regular GAMS installation, therefore the general GAMS licensing restrictions apply.
Linter-gams will try to find out if your GAMS file is part of a GGIG project and will do the necessary adjustments by itself. If you are working on a (non GGIG) multi-file model and want to specify the GAMS entry file, you may do so in the package settings pane. Note that you don't need to specify a path, but rather the actual entry point file name (e.g. entryFile.gms). Linter-gams will search for this file in the parent directories.
linter-gams will install all necessary packages for GAMS development. Those include syntax highlighting, the base linter (used for error underlining), and some GAMS helper functions which will be explained here.
If you work on a GGIG project (CAPRI / FARMDYN), make sure you add the trunk folder (the one containing the gams and GUI folder) of your checkout as your Project Folder in Atom (ctrl-shift-a or File -> Add Project Folder...).
This feature is enabled by default, and will work as long as a valid GAMS executable is defined in the settings pane. The appearance of the linter can be adjusted by changing the settings in the linter-ui-default package. For GAMS development, I currently use the settings as shown in the following image:
Note that by default, only the first error will be displayed, as typically subsequent errors may be resulting from that first error. Also note that errors will only be shown in active files -> if you work on a file which is currently not enabled (e.g. due to GUI settings in GGIG projects) no error checking will be done on that file.
You can change the maximum amount of errors shown in the settings pane. If you change the maximum amount of errors to display, only the first error will be highlighted with the severity 'Error', the second as a 'Warning', and all subsequent errors as 'Info' in the linter-ui bottom dock. This way, you can quickly identify the first error, as due to limitations in the linter-ui interface errors cannot be ranked otherwise.
In order to inspect where a variable/parameter/set was defined/assigned values/controlled/referenced or just to see its description, you can open GAMS View by using the shortcut ctrl-o or by opening the command palette (ctrl-shift-p) and typing gams: show. If the cursor is set inside a known symbol, the sidebar will be updated accordingly. A click on a given entry will jump to that symbol (also if the symbol is in another file). If you want to keep the sidebar from constantly updating while moving the cursor (e.g. when deeply inspecting a given symbol), you can click the lock button in the top left corner.
You can also search for a symbol with the searchbar shown at the upper part of the sidebar.
Values of sets and paramters, as well as the equation listing for equations or the column listing for variables can be shown with the new data panel feature. In order to activate, turn on the configuration in the linter-gams configuration panel, open the bottom dock and then click on a GAMS symbol (as shown in the GIF above). The data panel feature will parse your GAMS file for solve statements, and will try to show the available data right before any solve statement. You can cycle through the solve statements with a dropdown menu at the top right of the data panel.
If the data panel does not show any values, make sure that a) your model is free of compilation errors and b) has at least one solve statement
There are multiple options for running your model:
- Click the 'play' button in the sidebar
- Press
shift-enteron your keyboard - Open the command palette (
ctrl-shift-p) and typeGAMS runor justrunfollowed byenter.
The model will be solved in the background, so you can continue working. While the model is solving, the busy-signal dot (usually green) at the bottom will be blinking, and the bottom panel will open showing the models console output. Once the model is solved, the listing file will be opened automatically in a new pane.
It may occur that the .lst file was openend in Atom before GAMS finished writing all information to the file.
This may lead to the sidebar not showing the correct line positions and symbols in the sidebar.
The listing file can be re-parsed by running the gams: reload-listing command from the command palette (ctrl-shift-p/cmd-shift-p).
Sometimes you need to check your parameters/sets values at a given position. Often, an abort statement is used in order to stop execution at that point and to display the values of the parameter. Linter-gams gives you two options on how to speed up that process:
If you type
abort myParameterOrSet;
and run your model (see section above), linter-gams will automatically jump to the parameter display in the listing file. Make sure you have the GAMS View sidebar opened (shift-o), otherwise the listing file will be opened at the beggining of the document.
When working with multiple projects, individual project configuration files can be specified. The project file should be located in the projects root directory. If you need to specify a model-entry file, make sure that the .gamslintc.js file is in the same directory.
Example of a .gamslintc.js configuration file.
module.exports = {
'Gams Executable': 'String',
'Scratch directory': 'String',
'Jump to Abort': true,
'Auto unfold listing entries treshold': 10,
'Only auto unfold display statements': true,
'Default parameter to jump to after solve': 'gamsParameter',
'Multi-file entry point': 'my_model.gms',
'Command Line Arguments - Compilation': ['--myArg=3','--myOtherArg5'],
'Command Line Arguments - Execution': ['--myArg=3','--myOtherArg5'],
'Parse symbol values': false,
'Console limrow': 3,
'Console limcol': 3,
'Console dispWidth': 15
}It may occur, that the GAMS View sidebar is not updating for a symbol that you click upon.
In that case, the symbol you clicked is not read by the GAMS compiler, and you need to check your code logic (e.g. $if statements) for why the symbol is not read.
Example
$SETGLOBAL Country "France"
$iftheni.de %Country%=="Germany"
set test / 'Lederhosen', 'Wurst'/;
* If you click on `test`, `Gams View` will not update or show anything
* because this part of the code is not read by the compiler.
* It will show just fine if you change the value of the $SETGLOBAL to "Germany"
$endif.de
- The pre-installed autosave functionality (Settings -> Packages -> Autosave -> Enable (it's a checkbox inside the packages settings)).
- Using the fuzzy file finder
ctrl-pinstead of searching for a file in the project tree view - Using the main shortcut
ctrl-shift-pand then type what you want to do (likeBookmark,top,bot) - Jumping to the next error (even if its in a different file) by opening the command palette (
ctrl-shift-p) and typinglinter nextor even shorterli ne. You can also click on the error in the error pane at the bottom. - The amazing filter-lines package (especially useful in Listing files). Just highlight the desired word/symbol and press
ctrl-alt-f. Similar to KEDITS ALL command.
Please feel free to submit an issue or a pull request!
linter-gams is available under the MIT license.
Note that this packages is not affiliated to the official GAMS development corp.