-
Notifications
You must be signed in to change notification settings - Fork 0
CsvToDat Utility
Home > CsvToDat Utility
This topic documents the experimental OpenM++ CsvToDat
utility. CsvToDat
creates Modgen-compatible .dat input files for parameters provided in csv or tsv format.
The CsvToDat
utility is Modgen-specific. It is only relevant for cross-compatible models, and only relevant for cross-compatible models where one or more parameters are supplied in csv
or tsv
format, formats which Modgen does not support. Modgen only supports the Modgen-specific .dat
format.
OpenM++ supports a number of parameter input formats described elsewhere in this wiki. For example, values for the RiskPaths
parameter UnionDurationBaseline
can be specified in several csv
formats such as a file named UnionDurationBaseline.csv
with content like
dim0, dim1, param_value
UO_FIRST, "(-∞,1)", 0.0096017
UO_FIRST, "[1,3)", 0.0199994
UO_FIRST, "[3,5)", 0.0199994
UO_FIRST, "[5,9)", 0.0213172
UO_FIRST, "[9,13)", 0.0150836
UO_FIRST, "[13,∞)", 0.0110791
UO_SECOND, "(-∞,1)", 0.0370541
UO_SECOND, "[1,3)", 0.0370541
UO_SECOND, "[3,5)", 0.012775
UO_SECOND, "[5,9)", 0.012775
UO_SECOND, "[9,13)", 0.0661157
UO_SECOND, "[13,∞)", 0.0661157
For a Modgen model, the parameter UnionDurationBaseline
must be specified in .dat
Modgen format, either in a stand-alone file with a name like Param_UnionDurationBaseline.dat
or perhaps together with other parameters in a file with a name like RiskPaths.dat
. In either case, the content looks something like:
parameters {
// Union Duration Baseline of Dissolution
double UnionDurationBaseline[UNION_ORDER][UNION_DURATION] = {
0.0096017, (2) 0.0199994, 0.0213172, 0.0150836, 0.0110791,
(2) 0.0370541, (2) 0.012775, (2) 0.0661157,
};
};
The CsvToDat
utility can be used to create, for each parameter supplied in csv or tsv format, a corresponding dat
file for the Modgen version of a model. OpenM++ ignores input files with prefix modgen_
, so CsvToDat
deliberately generates .dat
files with that prefix. That ensures that OpenM++ will not attempt to read two versions of the same parameter from two input files, which would result in a build error. Continuing the example, CsvToDat
would create a file named modgen_UnionDurationBaseline.dat
. CsvToDat
will silently overwrite any existing version of a generated file named modgen_UnionDurationBaseline.dat
.
CsvToDat
does not actually read and convert the csv
file UnionDurationBaseline.csv
. Instead, CsvToDat
notes that UnionDurationBaseline
was specified in csv
format by the presence of that file. It then obtains the values of the parameter and its metadata (dimension names) from the published OpenM++ database for the model to construct the contents of the generated file modgen_UnionDurationBaseline.dat
(see above for what the generated contents look like). Thus, it is important to build the OpenM++ version of the model to create an up-to-date OpenM++ database for the model before running csv_to_dat
.
If a parameter value note is supplied for a parameter provided in .csv
or .tsv
format, for example a file UnionDurationBaseline.EN.md
which provides an English note for the parameter values in the file UnionDurationBaseline.csv
, CsvToDat
will read the .md
file and create a corresponding NOTE
comment in the generated file modgen_UnionDurationBaseline.dat
. Lists and code blocks in the markdown file will be transformed to their Modgen equivalents in the generated NOTE
comment.
CavToDat
will silently replace an existing file like modgen_XYZ.dat
if the file XYZ.csv
exists. It will not remove an existing file modgen_ABC.dat
if the corresponding file ABC.csv
is absent. An 'orphan' file like modgen_ABC.dat
may have been created by a previous invocation of CsvToDat
when the model contained the parameter ABC
which was subsequently removed or renamed. Orphan files like modgen_ABC.dat
may need to be removed manually to avoid errors when the Modgen model is run and attempts to read the parameter ABC
which no longer exists in the model.
This subtopic describes the command line options of the CsvToDat
utility.
CsvToDat
is experimental, and options and behaviour may change in subsequent releases.
A complete list of options and arguments is displayed by issuing the command
perl CsvToDat.pl -h
CsvToDat [-hkv] [long options...]
-h --help print usage message and exit
-v --version print version and exit
--model STR name of model
--ompp_database STR path of ompp database containing scenario
--scenario_folder STR path of scenario folder for generated dat
files
--scenario STR name of scenario (default is Default)
-k --keep_tmp keep temporary files in folder ./tmp_CsvToDat
--verbose verbose log output
The arguments --model
, --ompp_database
, and --scenario_folder
are required. --model
is a name which is usually the same as the model folder, and the other two arguments are paths. See below for an example.
The -k
argument is optional and does not affect the operation of CsvToDat
. Without this flag, CsvToDat
tells the dbcopy
utility to write metadata and parameters to a temporary folder which is deleted when CsvToDat
completes. This flag will instead place dbcopy
output to a fixed subfolder named ./tmp_CsvToDat
where it can be examined.
The argument --scenario
is optional. The default value is the Default
scenario. This option is untested.
The CsvToDat
utility is supplied as the Perl script CsvToDat.pl
as well as the stand-alone executable CsvToDat.exe
for the convenience of Windows users who may not have Perl installed. The two versions function identically. In this example the Perl script version is used.
Consider a model named RiskPaths_csv
which is a clone of the RiskPaths
model, but with some input parameters specified in a csv
format instead of the .dat
format.
A command prompt is opened, and the current working directory set to the model folder RiskPaths_csv
.
The Default scenario folder RiskPaths_csv/parameters/Default
contains the following files:
C:\Development\X\ompp\models\RiskPaths_csv>dir parameters\Default
Volume in drive C is OS
Volume Serial Number is 14E2-D15F
Directory of C:\Development\X\ompp\models\RiskPaths_csv\parameters\Default
2021-06-14 09:06 PM <DIR> .
2021-06-14 09:06 PM <DIR> ..
2021-06-12 04:12 AM 179 AgeBaselineForm1.id.csv
2021-06-12 04:12 AM 88 AgeBaselinePreg1.value.csv
2021-06-12 04:12 AM 22 CanDie.csv
2021-06-12 04:12 AM 82 Framework.odat
2021-06-14 10:24 AM 484 RiskPaths.dat
2021-06-12 04:12 AM 426 UnionDurationBaseline.csv
6 File(s) 2,211 bytes
2 Dir(s) 1,729,317,085,184 bytes free
As can be seen from the file names and extensions, the 4 RiskPaths parameters AgeBaselineForm1
, AgeBaselinePreg1
, CanDie
, and UnionDurationBaseline
are specified using a csv
format. The remaining RiskPaths parameters are specified in .dat
format in the files RiskPaths.dat
and Framework.odat
.
If the Modgen version of the model were run, it would fail with an error about missing values for those 4 parameters.
Next, CsvToDat
is invoked to create Modgen .dat
versions of the missing parameters, as follows:
C:\Development\X\ompp\models\RiskPaths_csv>perl ../../Perl/CsvToDat.pl --model RiskPaths_csv --ompp_database ompp/bin/RiskPaths_csv.sqlite --scenario_folder parameters/Default
CsvToDat
was invoked specifying the three required arguments. In this invocation, the paths to the OpenM++ database and to the scenario folder were specified relative to the current working directory, which was set to the model folder RiskPaths_csv
previously. After CsvToDat
completes, the contents of the scenario directory have changed, as follows:
C:\Development\X\ompp\models\RiskPaths_csv>dir parameters\Default
Volume in drive C is OS
Volume Serial Number is 14E2-D15F
Directory of C:\Development\X\ompp\models\RiskPaths_csv\parameters\Default
2021-06-14 09:06 PM <DIR> .
2021-06-14 09:06 PM <DIR> ..
2021-06-12 04:12 AM 179 AgeBaselineForm1.id.csv
2021-06-12 04:12 AM 88 AgeBaselinePreg1.value.csv
2021-06-12 04:12 AM 22 CanDie.csv
2021-06-12 04:12 AM 82 Framework.odat
2021-06-17 12:08 PM 285 modgen_AgeBaselineForm1.dat
2021-06-17 12:08 PM 267 modgen_AgeBaselinePreg1.dat
2021-06-17 12:08 PM 47 modgen_CanDie.dat
2021-06-17 12:08 PM 331 modgen_UnionDurationBaseline.dat
2021-06-14 10:24 AM 484 RiskPaths.dat
2021-06-12 04:12 AM 426 UnionDurationBaseline.csv
10 File(s) 2,211 bytes
2 Dir(s) 1,729,318,125,568 bytes free
CsvToDat
has created 4 new files with the .dat
extension, one for each parameter which was specified in csv
format. The Modgen version of RiskPaths_csv
can now read these files and build and run without error. The OpenM++ version of RiskPaths_csv
will ignore these 4 new files because their names start with modgen_
, and will continue to build and run without error.
- 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