Skip to main content
Jump to: navigation, search

VIATRA2/Frequently Asked Questions

Revision as of 11:10, 10 June 2008 by (Talk | contribs) (How do I give feedback (bug reports, improvement ideas, experiences, observations)?)


What is VIATRA2?

VIATRA2 is a model transformation tool integrated into Eclipse. TODO

Is it available for free?

Yes. VIATRA2 is licensed under the Eclipse Public License v1.0.

How do I obtain Viatra2?

See VIATRA2 Installation.

How do I give feedback (bug reports, improvement ideas, experiences, observations)?

There are multiple possibilities:

VTML metamodeling


Patterns and pattern language

Can patterns (or a single pattern) reference each other recursively?

Yes. However, the recursion should be well-founded. In certain cases, pattern systems that are not well-founded (but have a sensible fixpoint) are also acceptable, but ensuring their correct behaviour is is the responsibility of the pattern engineer.

Can patterns and gtrules be referenced from other VTCL machines?

Yes. The fully qualified name of the pattern/gtrule should be used instead of the short name. The same applies for VTCL rules.



namespace mydomain.mysubdomain;
machine mymachine {
pattern mypattern(X) = {
rule myrule(in X) = ...


machine myothermachine {
pattern composite(A) = {
      find mydomain.mysubdomain.mymachine.mypattern(A);
rule somerule(in C) = seq{
      call mydomain.mysubdomain.mymachine.myrule(C);
      forall A in C with find mydomain.mysubdomain.mymachine.mypattern(A) do ...

The pattern matcher seems to discard some occurrences of my patterns. Why?

VTCL has injective pattern matching semantics; in other words, pattern occurrences have to be isomorphic to the pattern graph. The practical implication is that no two pattern variables in the same pattern body can take the same value; such occurrences will be rejected. Patterns should be designed with this important phenomenon in mind.

The only exception is explicit variable assignment (e.g. A=B). The relaxing effect of variable assignment also applies indirectly; the assignment can be asserted in a separate pattern called using the find keyword.


 pattern fullsiblings(X, Y) = {
      person.parent(PX1, X, Parent1);
      person.parent(PX2, X, Parent2);
      person.parent(PY1, Y, Parent1);
      person.parent(PY2, Y, Parent2);
As Parent1 and Parent2 are not allowed to coincide due to injectivity, X and Y need two separate common parents. Therefore this pattern does not match half-siblings. Injectivity also keeps X and Y separate, so a single person with two parents does not fit the pattern either.

VTCL transformations


Graphical user interface and usage


Sensoria CASE Tool




Back to the top