Data model of erecord_vpz application

Data model of the erecord_vpz application

Schema

• VpzPath

• VpzAct

  • one VpzOrigin

  • one VpzInput

    • one VleBegin
    • one VleDuration

    • many VleCond

      • many VlePar

    • many VleView

      • many VleOut

  • one VpzOutput
  • one VpzWorkspace

VpzAct ‘comes’ (is built) from a VpzPath or a VleVpz

Data model

VleBegin

Vle begin

VleCond

Vle condition

VleDuration

Vle duration

VleOut

Vle output data

Vle output data (of a VleView)

VlePar

Vle parameter

Vle parameter (of a VleCond).

It contains some information about the parameter (name, value…), that is got or not into a request answer (it depends on the options given into the request).

A value type can value : “boolean”, “integer”, “double”, “string”, “xml”, “set”, “map”, “tuple”, “table”, “matrix, “none”, “”.

VleView

Vle view

VpzAct

Vpz activity

It is defined from a VleVpz or a VpzPath

VpzInput

Vpz input

Other denominations : input information of a vpz ; vpz input information, input conditions of a simulator.

The vpz input information corresponds with the configuration (experiment) defined into the vpz file (information such as parameters, duration, begin…).

VpzOrigin

Vpz origin

VpzOutput

Vpz output

Other denominations : output information of a vpz ; vpz output information, simulation results of a simulator.

The vpz output information corresponds with the simulation results.

VpzPath

Vpz path

A VpzPath corresponds with a vpz file absolute path that gives : its location into a vle package into a models repository (providing the required environment for running simulations) and its vpz name.

VpzWorkspace

Vpz workspace

A VpzWorkspace is attached to a VpzAct. It defines a workspace directory dedicated to the Vpz activity (manipulation).