In the background mode GMDH Shell performs modeling simulation without any interaction. ​The easiest way to launch the program ​in the background mode is to use the command line key **''/​auto''​**

+

-

+

-

+

-

Use of the key **''/​auto''​** executes the project located in the current directory. So, the usual way for background processing is to configure a project visually and then run it from the command line. Example: ​"''​"GMDH Shell.exe"​ /auto''"​ No other settings required.

+

-

+

-

+

-

+

-

If the project is located in another directory, you'll need to run "''"​GMDH Shell.exe" ​/auto:​C\MyData''"​. Of course, there should be a configured project (''​gmdh_shell.ini''​) in that directory.

- All settings stored in that section are configurable from command line. For example, ​to set **''​step''​** ​to 10, write **''/​pr.step:10''​**.

+

* ''/​im''​ — importer

* ''/​im''​ — importer

-

* ''/​pr''​ — preprocessor

* ''/​pr''​ — preprocessor

-

* ''/​ca''​ — solver

* ''/​ca''​ — solver

-

* ''/​po''​ — postprocessor

* ''/​po''​ — postprocessor

-

* ''/​ex''​ — exporter

* ''/​ex''​ — exporter

+

- Some settings are stored in the so-called “shared storage”, accessible to several plug-ins. For example: ''<​nowiki><​Storage name="​gs.prepro"><​decompositionlimit>​0</​decompositionlimit></​nowiki>''​ → ''/​pr.gs.prepro.decompositionlimit:​0''​

-

+

:!: The plug-in may have some extra options ​not stored in the ''​.gsp''​, but listed in the documentation.

-

+

-

:!: The plug-in may have some extra options ​that aren'​t ​stored in ''​gmdh_shell.ini''​.

**Data Science** and **Load forecasting** editions of GMDH Shell are supplied with an export module that outputs predictions in the command line mode. C++ source codes of the module - a [[http://​www.codeblocks.org|CodeBlocks]] project is available in the installation directory "​..\Plugins\ExportForecast-source.zip"​.

+

The module automatically performs export of predictions when GMDH Shell is launched using the command line. Predictions are saved to **simulation_result.txt** in the project directory.