... | ... | @@ -5,17 +5,21 @@ Additional to this schema, you can find a rough overview here. A general knowled |
|
|
|
|
|
The root XML element has to be <HPnG>. Within this root there can and should be the 3 kinds of model objects <places>, <transitions> and <arcs>.
|
|
|
|
|
|
Within the <places> section there can be an arbitrary number of <DiscretePlace> and <ContinuousPlace> elements. Both should contain the unique attribute "id".
|
|
|
Within the <places> section there can be an arbitrary number of <discretePlace> and <continuousPlace> elements. Both should contain the unique attribute "id".
|
|
|
|
|
|
Discrete Places should also contain the attribute "marking" which implies the number of tokens of this place in the initial state and its value has to be convertible to an Integer value.
|
|
|
|
|
|
Continuous Places should have the attibutes "capacity" for the place's maximum fluid capacity and "level" for the fluid level of the place in the initial state, both values have the be convertible to Double values.
|
|
|
Continuous Places should have the attributes "capacity" for the place's maximum fluid capacity and "level" for the fluid level of the place in the initial state, both values have the be convertible to Double values.
|
|
|
|
|
|
|
|
|
Within the <transitions> section there can be 5 kinds of transitions: <ImmediateTransition>, <DeterministicTransition>, <GeneralTransition>, <ContinuousTransition> and <DynamicContinuousTransition>. Transitions should also contain an "id" attribute.
|
|
|
Within the <transitions> section there can be 5 kinds of transitions: <immediateTransition>, <deterministicTransition>, <generalTransition>, <continuousTransition> and <dynamicContinuousTransition>. Transitions should also contain an "id" attribute.
|
|
|
|
|
|
Immediate, deterministic and general transitions have the attributes "weight" (Double) and "priority" (Integer) for resolving conflicts. In addition deterministic transitions need the attribute "discTime" as Double compatible value for their time to fire after enabling.
|
|
|
|
|
|
General transitions also need the attribute "policy" which can have one of the values "resume", "repeatdifferent" or "repeatidentical", defining what happens to the enabling time when a general transition is disabled and enabled again. Furthermore the attribute "cdf" defines the cumultative distribution function for the firing of the transition and depending on this attribute different sub XML elements of the type <parameter> are needed with the attributes "name" and "value". See the list for all parameters needed.
|
|
|
General transitions also need the attribute "policy" which can have one of the values "resume", "repeatdifferent" or "repeatidentical", defining what happens to the enabling time when a general transition is disabled and enabled again. Furthermore the attribute "cdf" defines the cumulative distribution function for the firing of the transition and depending on this attribute different sub XML elements of the type <parameter> are needed with the attributes "name" and "value". See the list for all parameters needed.
|
|
|
|
|
|
Continuous transitions should have a "rate" attribute (Double) and dynamic continuous transitions need the sub elements <pid> with the attribute "coef" (for weighting) and containing the id of the referenced continuous transition.
|
|
|
|
|
|
The <arcs> section can contain the elements <discreteArc>, <continuousArc> and <guardArc>. All arcs have the attributes "id" and "weight" (as defined above) and "fromNode" and "toNode" for referencing the id of the connected place and transition.
|
|
|
|
|
|
In addition continuous arcs should have the attributes "share" (Double) and "priority" (Integer). Guard arcs can be test or inhibitor arcs and accordingly have a Boolean flag attribute "isInhibitor". |