-
Notifications
You must be signed in to change notification settings - Fork 0
Oms API Read Run Microdata aggregated Ids
Read a "page" of aggregated microdata values from model run.
-
Aggregate one or more microdata value attribute (float of integer type attribute). For example, two aggregations:
OM_AVG(Income) , OM_MAX(Salary + Pension)
. -
Group by one or more dimension attributes (enum-based or bool type attribute). For example, group by two dimension attributes:
AgeGroup , Sex
. -
Page is part of output table values defined by zero-based "start" row number and row count. If row count <= 0 then all rows below start row number returned.
-
Dimension(s) returned as enum id, not enum codes.
-
Method verb must be POST and Content-Type header "application/json".
Following aggregation functions avaliable:
-
OM_AVG
mean of accumulators sub-values -
OM_SUM
sum of accumulators sub-values -
OM_COUNT
count of accumulators sub-values (excluding NULL's) -
OM_COUNT_IF
count values matching condition -
OM_MAX
maximum of accumulators sub-values -
OM_MIN
minimum of accumulators sub-values -
OM_VAR
variance of accumulators sub-values -
OM_SD
standard deviation of accumulators sub-values -
OM_SE
standard error of accumulators sub-values -
OM_CV
coefficient of variation of accumulators sub-values
It is also possible to use parameter(s) in calculation, parameter must be a scalar of float or integer type.
For example: OM_COUNT_IF(Income > param.High)
, where param.High
is a value of scalar parameter High
in that model run.
For more details please see: Model Output Expressions
JSON body POSTed to specify entity name, page size, row count, filters and row order. It is expected to be JSON representation of db.ReadCalculteMicroLayout structure from Go library. See also: db.ReadLayout structure from Go library.
// ReadCalculteMicroLayout describe microdata generation read layout, aggregation measures and group by attributes.
type ReadCalculteMicroLayout struct {
ReadLayout // entity name, run id, page size, where filters and order by
CalculateMicroLayout // microdata aggregations
}
// CalculateMicroLayout describes aggregations of microdata.
//
// It can be comparison aggregations and/or calculation aggregations.
// Comparison aggregation must contain [base] and [variant] attribute(s), ex.: OM_AVG(Income[base] - Income[variant]).
// Calculation aggregation is attribute(s) aggregation expression, ex.: OM_MAX(Income) / OM_MIN(Salary).
type CalculateMicroLayout struct {
Calculation []CalculateLayout // aggregation measures, ex.: OM_MIN(Salary), OM_AVG(Income[base] - Income[variant])
GroupBy []string // attributes to group by
}
// CalculateLayout describes calculation expression for parameters, output table values or microdata entity.
// It can be comparison calculation for multiple model runs, ex.: Expr0[base] - Expr0[variant].
type CalculateLayout struct {
Calculate string // expression to calculate, ex.: Expr0[base] - Expr0[variant]
CalcId int // calculated expression id, calc_id column in csv, ex.: 0, 12000, 24000
Name string // calculated expression name, calc_name column in csv, ex.: Expr0, AVG_Expr0, RATIO_Expro0
}
// ReadLayout describes source and size of data page to read input parameter, output table values or microdata.
//
// Row filters combined by AND and allow to select dimension or attribute items,
// it can be enum codes or enum id's, ex.: dim0 = 'CA' AND dim1 IN (2010, 2011, 2012)
type ReadLayout struct {
Name string // parameter name, output table name or entity microdata name
FromId int // run id or set id to select input parameter, output table values or microdata from
ReadPageLayout // read page first row offset, size and last page flag
Filter []FilterColumn // dimension or attribute filters, final WHERE does join all filters by AND
FilterById []FilterIdColumn // dimension or attribute filters by enum ids, final WHERE does join filters by AND
OrderBy []OrderByColumn // order by columnns, if empty then dimension id ascending order is used
}
Methods:
POST /api/model/:model/run/:run/microdata/calc-id
For example:
curl -v -X POST -H "Content-Type: application/json" http://localhost:4040/api/model/modelOne/run/Microdata%20in%20database/microdata/calc-id -d @read_m1_person_calc_1.json
Arguments:
:model - (required) model digest or model name
Model can be identified by digest or by model name. It is recommended to use digest because it is uniquely identifies model. It is possible to use model name, which is more human readable than digest, but if there are multiple models with same name in database than result is undefined.
:run - (required) model run digest, run stamp or run name
Model run can be identified by run digest, run stamp or run name. It is recommended to use digest because it is uniquely identifies model run. Run stamp, if not explicitly specified as model run option, automatically generated as timestamp string, ex.: 2016_08_17_21_07_55_123. It is also possible to use name, which is more human readable than digest, but if there are multiple runs with same name in database than result is undefined.
JSON body arguments:
Example 1: Aggregate Person
entity to get OM_AVG()
average Income
value and group it by AgeGroup , Sex
dimension attributes.
{
"Name": "Person",
"Calculation": [{
"Calculate": "OM_AVG(Income)",
"CalcId": 2401,
"Name": "Avg_Income"
}
],
"GroupBy": [
"AgeGroup",
"Sex"
]
}
Example 2.
- aggregate
Person
entity - calculate two values:
-
OM_AVG()
average ofIncome
value, adjusted by using parameterStartingSeed
values -
OM_AVG()
average ofSalary + Pension
value, adjusted by using parameterStartingSeed
values
-
- and group it by
AgeGroup , Sex
dimension attributes - filter only rows where:
- enum id's of dimension
AgeGroup IN [20, 40]
- and enum id's of dimension
Sex = 1
- enum id's of dimension
{
"Name": "Person",
"Calculation": [{
"Calculate": "OM_AVG(Income) * (param.StartingSeed / 100)",
"CalcId": 2401,
"Name": "Avg_Income_adjusted"
}, {
"Calculate": "OM_AVG(Salary + Pension + param.StartingSeed)",
"CalcId": 2404,
"Name": "Avg_Salary_Pension_adjusted"
}
],
"GroupBy": [
"AgeGroup",
"Sex"
],
"Offset": 0,
"Size": 100,
"IsFullPage": true,
"FilterById": [{
"Name": "AgeGroup",
"Op": "IN",
"EnumIds": [20, 40]
}, {
"Name": "Sex",
"Op": "=",
"EnumIds": [1]
}
],
"OrderBy": [{
"IndexOne": 2,
"IsDesc": true
}, {
"IndexOne": 3,
"IsDesc": true
}
]
}
Name - (required) entity name
Offset - (optional) zero-based start row to select aggreagted microdata values
Size - (optional) max row count to select rows, if size <= 0 then all rows selected
IsFullPage - (optional) if true then always return non-empty last page of data
FilterById - (optional) conditions to filter enum id's of dimension attributes
OrderBy - (optional) list of columns indexes (one based) to order by
Filter conditions joined by AND and can have following operations:
= - enum id equal to: AgeGroup = 20
!= - enum id not equal to: AgeGroup <> 20
> - enum id greater than: AgeGroup > 20
>= - enum id greater or equal: AgeGroup >= 20
< - enum id less than: AgeGroup < 20
<= - enum id less or equal: AgeGroup <= 20
IN - in the list of id's: AgeGroup IN (20, 30, 40)
BETWEEN - between min and max: AgeGroup BETWEEN 20 AND 40
IN_AUTO - automatically choose most suitable: = or != or IN or BETWEEN
Order by specified by one-based column(s) index(es) in result. Columns always contain enum id's, not enum codes and therefore result ordered by id's.
First two columns are run_id, calc_id
:
SELECT run_id, CalcId AS calc_id, AgeGroup, Sex, ..., calc_value FROM .... ORDER BY 1, 2,...
JSON response:
{
Layout: {
Offset: actual first row number of the page data (zero-base),
Size: actual data page row count,
IsLastPage: true if this is last page of data
},
Page: [....page of data...]
}
Result:
* Trying [::1]:4040...
* Connected to localhost (::1) port 4040
> POST /api/model/modelOne/run/Microdata%20in%20database/microdata/calc-id HTTP/1.1
> Host: localhost:4040
> User-Agent: curl/8.4.0
> Accept: */*
> Content-Type: application/json
> Content-Length: 753
>
< HTTP/1.1 200 OK
< Content-Type: application/json
< Date: Fri, 29 Dec 2023 03:53:37 GMT
< Content-Length: 609
<
{
"Page": [{
"Attr": [{
"IsNull": false,
"Value": 40
}, {
"IsNull": false,
"Value": 1
}, {
"IsNull": false,
"Value": 57665830.54215979
}
],
"CalcId": 2404,
"RunId": 219
}, {
"Attr": [{
"IsNull": false,
"Value": 20
}, {
"IsNull": false,
"Value": 1
}, {
"IsNull": false,
"Value": 100657151.25
}
],
"CalcId": 2404,
"RunId": 219
}, {
"Attr": [{
"IsNull": false,
"Value": 40
}, {
"IsNull": false,
"Value": 1
}, {
"IsNull": false,
"Value": 71069306.57187325
}
],
"CalcId": 2401,
"RunId": 219
}, {
"Attr": [{
"IsNull": false,
"Value": 20
}, {
"IsNull": false,
"Value": 1
}, {
"IsNull": false,
"Value": 134209535
}
],
"CalcId": 2401,
"RunId": 219
}
],
"Layout": {
"Offset": 0,
"Size": 4,
"IsLastPage": true,
"IsFullPage": true
}
}
- 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++
- Authored Model Documentation
- Built-in Attributes
- Censor Event Time
- Create Import Set
- Derived Tables
- Entity Attributes in C++
- Entity Function Hooks
- Entity Member Packing
- Entity Tables
- Enumerations
- Events
- Event Trace
- External Names
- Generated Model Documentation
- Groups
- Illustrative Model
Align1
- Lifecycle Attributes
- Local Random Streams
- Memory Use
- Microdata Output
- Model Code
- Model Documentation
- Model Languages
- Model Localization
- Model Metrics Report
- Model Resource Use
- Model Symbols
- Parameter and Table Display and Content
- Population Size and Scaling
- Screened Tables
- Symbol Labels and Notes
- Tables
- Test Models
- Time-like and Event-like Attributes
- Use Modules
- Weighted Tabulation
- File-based Parameter Values
- 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 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