-
Notifications
You must be signed in to change notification settings - Fork 0
Omc Run Options
Home > Model Development Topics > OpenM++ compiler arguments and options
This topic documents the arguments and options of the OpenM++ compiler (omc). These arguments and options are normally used indirectly by build system components shipped with OpenM++ for the supported development environments.
- Model Code
- File-based Parameter Values: Representing parameter values in files
- ini File Format
There are a number of options which control model compilation and publishing. The most frequently used are:
- model name
- input directory containing model .ompp or .mpp source files
- input directory with model parameters (a.k.a. "scenario" .dat files or parameters .csv files)
- input scenario name
The OpenM++ compiler (omc) gets run options in the following order:
- as command line arguments
- from options ini-file
- use default values
Following options are supported by omc command line:
-
-Omc.ModelName
name/of/model/executable, e.g. RiskPaths -
-Omc.ScenarioName
name/of/base/scenario, e.g. Base, it can be list of names -
-Omc.InputDir
input/dir/to/find/source/files -
-Omc.OutputDir
output/dir/to/place/model/cpp_and_h_and_sql/files -
-Omc.UseDir
use/dir/with/ompp/files -
-Omc.ParamDir
input/dir/to/find/parameter/files/for/scenario, it can be list of directories -
-Omc.FixedDir
input/dir/to/find/fixed/parameter/files/ -
-Omc.SqlDir
input sql/script/dir to create model SQLite database -
-Omc.SqliteDir
output directory to create model SQLite database -
-Omc.SqlPublishTo
create sql scripts to publish inSQLite,MySQL,PostgreSQL,MSSQL,Oracle,DB2
, default:SQLite
-
-Omc.CodePage
code page for converting source files, e.g. windows-1252 -
-Omc.MessageLanguage
language to display output messages, default: user environment settings -
-Omc.MessageFnc
localized message functions, default:LT,logMsg,logFormatted,WriteLogEntry,WarningMsg,ModelExit
-
-Omc.ModelDoc
generate human-readable model documentation (User Edition), default: false -
-Omc.InDocDir
input/dir/to/find/authored/model/documentation/files/ -
-Omc.OutDocDir
output directory to create model documentation files, e.g.:ompp/bin/doc
-
-Omc.NoLineDirectives
suppress #line directives in generated C++, default: false -
-Omc.NoMetadata
suppress production of model metadata (model cannot be run), default: false -
-Omc.TraceScanning
detailed tracing from scanner, default: false -
-Omc.TraceParsing
detailed tracing from parser, default: false -
-OpenM.IniFile
some/optional/omc.ini
Or you can use short form of command line arguments:
-
-m
short form of-Omc.ModelName
-
-s
short form of-Omc.ScenarioName
-
-i
short form of-Omc.InputDir
-
-o
short form of-Omc.OutputDir
-
-u
short form of-Omc.UseDir
-
-p
short form of-Omc.ParamDir
-
-f
short form of-Omc.FixedDir
-
-d
short form of-Omc.InDocDir
-
-ini
short form of-OpenM.IniFile
Each option has a unique key string associated with it, i.e.: Omc.InputDir
.
You can use this key to specify either as a command line argument or in an ini-file Section.Key entry. For example:
omc.exe -m RiskPaths -Omc.InputDir ../code -ini my-omc.ini
would compile model RiskPaths
source files: ../code/*.ompp
and ../../code/*.mpp
with some other options specified through my-omc.ini file.
Omc do compile model source *.ompp and *.mpp files and create model.sqlite database with parameter values from *.odat, *.dat, *.csv, *.tsv and *.md files:
omc.exe -m RiskPaths -i ../code -s Default -p ../parameters/Default
Command above will read *.odat, *.dat, *.csv, *.tsv and *.md files from ../parameters/Default
directory and create RiskPaths.sqlite
database with Default
input set of parameters (Default
scenario).
It is possible to create multiple input sets of parameters (multiple scenarios) when you are building the model:
omc.exe -m RiskPaths -i ../code -s Default,Other -p ../parameters/Default,../parameters/other/dir
Above command will create two input sets of parameters:
- scenario
Default
from *.dat, *.odat, *.csv, *.tsv and *.md files in../parameters/Default
directory - scenario
Other
from *.csv, *.tsv and *.md files in../parameters/other/dir
Please note that the second or subsequent scenario directory (if present) can contain only CSV or TSV and Markdown files and not .dat or .odat files.
For more information on specifying parameter values using .csv or .tsv files, please see the topic File-based Parameter Values.
For more information on specifying parameter values using .dat or .odat files, please refer to Modgen documentation.
To specify name of ini-file you can use -ini
or -OpenM.IniFile
command line option. Please see OpenM++ ini-file format to find out more.
Example of omc ini-file:
;
; This is an example of omc.ini options file
;
;
; Omc-specific options
;
[Omc]
;
; model name, it must be specified either on command line or here
; no default value
;
; ModelName = NewCaseBased
;
; name of default set of input parameters (a.k.a. base scenario data)
; it can be multiple names separated by comma or semicolon
;
; default = Default
;
; ScenarioName = Default
; ScenarioName = Default,Other,Test
;
; input directory to get source .ompp or .mpp files to compile
; default = current directory
;
; InputDir = ./code
;
; output directory to place generated .cpp and .h files for the model
; default = current directory
;
; OutputDir = ./src
;
; use directory to resolve 'use' statements
; default = directory/of/omc.exe/../use/
;
; UseDir = ../../use
;
; parameter directory to get source .dat or .csv files to publish a scenario
; it can be multiple directories separated by comma or semicolon
;
; default = Default
;
; ParamDir = ../parameters/Default
; ParamDir = ../parameters/Default,../parameters/Other/dir,../parameters/some/Test
;
; fixed directory to get source .dat files with fixed parameter values
; default = Fixed
;
; FixedDir = ../parameters/Fixed
;
; directory where common sql scripts located (used to create SQLite database)
; default = directory/of/omc.exe/../sql/
;
; SqlDir = ../../sql
;
; output directory to create model.sqlite database
; default: value of OutputDir (see above)
;
; SqliteDir = ./src
;
; database providers comma-separated list
; supported providers: SQLite,MySQL,PostgreSQL,MSSQL,Oracle,DB2
; default: SQLite
;
; SqlPublishTo = SQLite
;
; code page for converting source files into utf-8
; default on Linux: utf-8 (no conversion)
; default on Windows: current user code page, e.g.: windows-1252
;
; CodePage = windows-1252
; language to display output messages
; default: Windows Control Panel or Linux LANG
;
; messageLang = en-CA
;
; localized message functions
; first argument of the Function("const char * message",...) translated into other language
; by lookup in omc.message.ini where "message" = "translated message"
; default: LT,logMsg,logFormatted,WriteLogEntry,WarningMsg,ModelExit
;
; MessageFnc = LT,logMsg,logFormatted,WriteLogEntry,WarningMsg,ModelExit
; suppress #line directives in generated cpp files
; default: false
;
; NoLineDirectives = false
; dsuppress production of model metadata (model cannot be run)
; default: false
;
; NoMetadata = false
; detailed tracing from scanner
; default: false
;
; TraceScanning = false
; detailed tracing from parser
; default: false
;
; TraceParsing = false
; if true then generate model documentation
; default: false
;
; ModelDoc = false
; input directory to find authored model documentation files
; default: ../doc
;
; InDocDir = ../doc
; output directory to create model documentation files
; default: $(TARGET_DIR)/doc
;
; OutDocDir = ompp/bin/doc
;
; Common openM++ run options supported by omc
;
[OpenM]
;
; log settings:
; log can be enabled/disabled for 3 independent streams:
; console - cout stream
; "last run" file - log file with specified name, truncated on every compiler run
; "stamped" file - log file with unique name, created for every compiler run
;
; "stamped" name produced from "last run" name by adding time-stamp and pid-stamp, i.e.:
; omc.log => omc.2012_08_17_16_04_59_148.1234.log
;
LogToConsole = true ; log to console
LogNoMsgTime = true ; if true then do not prefix log messages with date-time
; LogToFile = false ; log to file
; LogToStampedFile = false ; log to "stamped" file
; LogUseTimeStamp = false ; use time-stamp in log "stamped" file name
; LogUsePidStamp = false ; use pid-stamp in log "stamped" file name
; LogFilePath = omc.log ; log file path, default = current/dir/omc.log
; LogSql = false ; debug only: log sql statements (reserved, but not used by omc)
- Windows: Quick Start for Model Users
- Windows: Quick Start for Model Developers
- Linux: Quick Start for Model Users
- Linux: Quick Start for Model Developers
- MacOS: Quick Start for Model Users
- MacOS: Quick Start for Model Developers
- Model Run: How to Run the Model
- MIT License, Copyright and Contribution
- Model Code: Programming a model
- Windows: Create and Debug Models
- Linux: Create and Debug Models
- MacOS: Create and Debug Models
- MacOS: Create and Debug Models using Xcode
- Modgen: Convert case-based model to openM++
- Modgen: Convert time-based model to openM++
- Modgen: Convert Modgen models and usage of C++ in openM++ code
- Model Localization: Translation of model messages
- How To: Set Model Parameters and Get Results
- Model Run: How model finds input parameters
- Model Output Expressions
- Model Run Options and ini-file
- OpenM++ Compiler (omc) Run Options
- OpenM++ ini-file format
- UI: How to start user interface
- UI: openM++ user interface
- UI: Create new or edit scenario
- UI: Upload input scenario or parameters
- UI: Run the Model
- UI: Use ini-files or CSV parameter files
- UI: Compare model run results
- UI: Aggregate and Compare Microdata
- UI: Filter run results by value
- UI: Disk space usage and cleanup
- UI Localization: Translation of openM++
-
Highlight: hook to self-scheduling or trigger attribute
-
Highlight: The End of Start
-
Highlight: Enumeration index validity and the
index_errors
option -
Highlight: Simplified iteration of range, classification, partition
-
Highlight: Parameter, table, and attribute groups can be populated by module declarations
- Oms: openM++ web-service
- Oms: openM++ web-service API
- Oms: How to prepare model input parameters
- Oms: Cloud and model runs queue
- Use R to save output table into CSV file
- Use R to save output table into Excel
- Run model from R: simple loop in cloud
- Run RiskPaths model from R: advanced run in cloud
- Run RiskPaths model in cloud from local PC
- Run model from R and save results in CSV file
- Run model from R: simple loop over model parameter
- Run RiskPaths model from R: advanced parameters scaling
- Run model from Python: simple loop over model parameter
- Run RiskPaths model from Python: advanced parameters scaling
- Windows: Use Docker to get latest version of OpenM++
- Linux: Use Docker to get latest version of OpenM++
- RedHat 8: Use Docker to get latest version of OpenM++
- Quick Start for OpenM++ Developers
- Setup Development Environment
- 2018, June: OpenM++ HPC cluster: Test Lab
- Development Notes: Defines, UTF-8, Databases, etc.
- 2012, December: OpenM++ Design
- 2012, December: OpenM++ Model Architecture, December 2012
- 2012, December: Roadmap, Phase 1
- 2013, May: Prototype version
- 2013, September: Alpha version
- 2014, March: Project Status, Phase 1 completed
- 2016, December: Task List
- 2017, January: Design Notes. Subsample As Parameter problem. Completed
GET Model Metadata
- GET model list
- GET model list including text (description and notes)
- GET model definition metadata
- GET model metadata including text (description and notes)
- GET model metadata including text in all languages
GET Model Extras
GET Model Run results metadata
- GET list of model runs
- GET list of model runs including text (description and notes)
- GET status of model run
- GET status of model run list
- GET status of first model run
- GET status of last model run
- GET status of last completed model run
- GET model run metadata and status
- GET model run including text (description and notes)
- GET model run including text in all languages
GET Model Workset metadata: set of input parameters
- GET list of model worksets
- GET list of model worksets including text (description and notes)
- GET workset status
- GET model default workset status
- GET workset including text (description and notes)
- GET workset including text in all languages
Read Parameters, Output Tables or Microdata values
- Read parameter values from workset
- Read parameter values from workset (enum id's)
- Read parameter values from model run
- Read parameter values from model run (enum id's)
- Read output table values from model run
- Read output table values from model run (enum id's)
- Read output table calculated values from model run
- Read output table calculated values from model run (enum id's)
- Read output table values and compare model runs
- Read output table values and compare model runs (enun id's)
- Read microdata values from model run
- Read microdata values from model run (enum id's)
- Read aggregated microdata from model run
- Read aggregated microdata from model run (enum id's)
- Read microdata run comparison
- Read microdata run comparison (enum id's)
GET Parameters, Output Tables or Microdata values
- GET parameter values from workset
- GET parameter values from model run
- GET output table expression(s) from model run
- GET output table calculated expression(s) from model run
- GET output table values and compare model runs
- GET output table accumulator(s) from model run
- GET output table all accumulators from model run
- GET microdata values from model run
- GET aggregated microdata from model run
- GET microdata run comparison
GET Parameters, Output Tables or Microdata as CSV
- GET csv parameter values from workset
- GET csv parameter values from workset (enum id's)
- GET csv parameter values from model run
- GET csv parameter values from model run (enum id's)
- GET csv output table expressions from model run
- GET csv output table expressions from model run (enum id's)
- GET csv output table accumulators from model run
- GET csv output table accumulators from model run (enum id's)
- GET csv output table all accumulators from model run
- GET csv output table all accumulators from model run (enum id's)
- GET csv calculated table expressions from model run
- GET csv calculated table expressions from model run (enum id's)
- GET csv model runs comparison table expressions
- GET csv model runs comparison table expressions (enum id's)
- GET csv microdata values from model run
- GET csv microdata values from model run (enum id's)
- GET csv aggregated microdata from model run
- GET csv aggregated microdata from model run (enum id's)
- GET csv microdata run comparison
- GET csv microdata run comparison (enum id's)
GET Modeling Task metadata and task run history
- GET list of modeling tasks
- GET list of modeling tasks including text (description and notes)
- GET modeling task input worksets
- GET modeling task run history
- GET status of modeling task run
- GET status of modeling task run list
- GET status of modeling task first run
- GET status of modeling task last run
- GET status of modeling task last completed run
- GET modeling task including text (description and notes)
- GET modeling task text in all languages
Update Model Profile: set of key-value options
- PATCH create or replace profile
- DELETE profile
- POST create or replace profile option
- DELETE profile option
Update Model Workset: set of input parameters
- POST update workset read-only status
- PUT create new workset
- PUT create or replace workset
- PATCH create or merge workset
- DELETE workset
- POST delete multiple worksets
- DELETE parameter from workset
- PATCH update workset parameter values
- PATCH update workset parameter values (enum id's)
- PATCH update workset parameter(s) value notes
- PUT copy parameter from model run into workset
- PATCH merge parameter from model run into workset
- PUT copy parameter from workset to another
- PATCH merge parameter from workset to another
Update Model Runs
- PATCH update model run text (description and notes)
- DELETE model run
- POST delete model runs
- PATCH update run parameter(s) value notes
Update Modeling Tasks
Run Models: run models and monitor progress
Download model, model run results or input parameters
- GET download log file
- GET model download log files
- GET all download log files
- GET download files tree
- POST initiate entire model download
- POST initiate model run download
- POST initiate model workset download
- DELETE download files
- DELETE all download files
Upload model runs or worksets (input scenarios)
- GET upload log file
- GET all upload log files for the model
- GET all upload log files
- GET upload files tree
- POST initiate model run upload
- POST initiate workset upload
- DELETE upload files
- DELETE all upload files
Download and upload user files
- GET user files tree
- POST upload to user files
- PUT create user files folder
- DELETE file or folder from user files
- DELETE all user files
User: manage user settings
Model run jobs and service state
- GET service configuration
- GET job service state
- GET disk usage state
- POST refresh disk space usage info
- GET state of active model run job
- GET state of model run job from queue
- GET state of model run job from history
- PUT model run job into other queue position
- DELETE state of model run job from history
Administrative: manage web-service state
- POST a request to refresh models catalog
- POST a request to close models catalog
- POST a request to close model database
- POST a request to delete the model
- POST a request to open database file
- POST a request to cleanup database file
- GET the list of database cleanup log(s)
- GET database cleanup log file(s)
- POST a request to pause model run queue
- POST a request to pause all model runs queue
- PUT a request to shutdown web-service