CVC3 subtraction works similarly to addition, which requires a parameter
telling CVC3 where to cut off digits in the computed result.  jTET missed that,
so fix it.

Yanjun Jiang authored Sep 26, 2014 and Matthew Dawson committed Oct 03, 2014

From GenericVariableDeclarationGeneratorTest to GenericVariablesDeclarationGeneratorTest.

Yanjun Jiang authored Sep 25, 2014 and Matthew Dawson committed Oct 03, 2014

Modify all the files that use these two wrong spellings. The right
spelling should be Hierarchy and Hierarchical.

Yanjun Jiang authored Sep 25, 2014 and Matthew Dawson committed Oct 03, 2014

Modify it to the correct spelling, i.e., GenerateLiteralValue. Several
classes which implements this interface are also modified for this reason.

The author tag still had an email address on VariableCollection.  Remove as
javadoc doesn't really handle it.

Add appropriate copyright headers to variable parser pieces.

Update to the latest javadoc maven plugin.  Also start ignoring the antlr
package to avoid a failing build.

Mainly to help in documentation generation, move the antlr parsers to another
package.  Otherwise doesn't affect anything.

New updated documentation.  Partially relies on stuff to still come.

Its time this code had some real comments.  Mark up VariableCollection as
appropriate.

To ensure that the variables stored in a VariableCollection remain the same,
ensure that the maps returned from a VariableCollection are immutable.

Convert the output values in the output Grid from Matlab format to EventB supported
format symbols properly and then collect them while traversing cells. So that we can
also have complex expression in the result Grid. Aslo, the bug that outputVariables
in test cases have no type has been fixed. The realVariableType is mainly used for the
outputVariables now.

From this version on, the tool support complex expression like: (1*(1+1)+2).
This is realized by add parentheses to the EventBGenerator generated expression.
Also fix the problem of using wrong EventB symbols in the result XML before.

These files should be deleted in the support refinement commit. For
some reason this is forgetten. Now we clean them up.

Add the necessary logic to generate predicate subtypes to SAL, along with
hooking up the usual tests to verify it all works correctly.

As SAL doesn't verify the completeness of IF expressions, it requires an ELSE
statement so that non-deterministic behaviour does not creep in.  Fix the grid
generator to always give an ELSE clause.  A single cell is always used for any
IF expression, as it is assumed that the ELSE branch is never taken.

Add a SAL grid generator, using the depth first search walker.  It currently
just generates simple IF statements for each condition, nest IF statements as
appropriate.

To avoid duplication between the EventB and SAL generator, rename the EventB walker
to a more general name.  Also introduce a special interface, to ensure a depth
first walker is never used against a breadth first generator, and vice versa.

Add support to actually declare variables.  Currently only the real and
booleans are supported.

Intial work on SAL code generation.  For now, just deal with Real and Boolean expressions.

By default, all Simulink enumerated values are formed as: enumerationtype.constant
The current MATLAB parser in jTET fails to recognize this.  Fix this so that
it recognizes these constants properly.  Also add a test to verify this mode.
Note that the original style of just the constant is still ok, thought in
a TET block that style may not work.

Variable types now follow variable names in terms of naming rules.  This
relaxes them to allow numbers in the name.

Yanjun Jiang authored Sep 04, 2014 and Matthew Dawson committed Sep 05, 2014

The file name that was used in the refinement relation tag was being
incorrectly generated as tablenameMi, where tablename was the tablename,
and i was the refinement layer.  However, the actual files were called
tablename_Mi.  Fix this by using the same function to generate the name,
and standardize on the tablename_Mi notation.

Yanjun Jiang authored Jul 06, 2014 and Matthew Dawson committed Aug 29, 2014

From this version, two kinds of mode, i.e., Single Output No Refinement
(SONR),Single Output With Refinement(SOWR) are supported.

Yanjun Jiang authored Aug 21, 2014 and Matthew Dawson committed Aug 29, 2014

Seperate the creation of project and generation of table xml files. So
that in the future we can support multiple tables in a project easily.

Yanjun Jiang authored Aug 15, 2014 and Matthew Dawson committed Aug 29, 2014

The JUnit paramerized class is used here instead of using a massive
class repeating the various setup/test procedures.

Combine the several parameters in the constructor to one table object
parameter to make the interface more clean.

Make sure all closeable objects in EventBFileWriter are properly closed,
even in the presence of exceptions.

This new table name property is added when generating EventB files, but
can be used for other purpose too.

maven-assembly-plugin: 2.4 -> 2.4.1, bug fixes mostly.

Since jTET is now getting preped for deployment to Maven Central, update the
POM file, adding various metadata tags.

Update some out of date dependencies.  All test still pass, so everything
should be fine.

Underscores are fine characters for names.  Allow their use as well.  This is
just a change in the lexer, which wouldn't recognize them.

To ensure better test coverage, add boolean and predicate subtypes to the list
of generic tests.  Both are again very simple additions, and all current
generators are fine with them.  They are skippable in the usual way.

At least for the SAL generator for SimCheck, I need to transform the variable
names.  Thus add the ability for Variables to have different names outputed
during generation.  This ensures that a given variable always has its name
match as expected.

Also update the various tests to exercise this new functionality.

jTET needs a large amount of throw away instances of types or their marker
for its work.  Instead of creating a new instance each time, use a static
instance to avoid the work.  It also makes it more obvious when something is
temporary.

Yanjun Jiang authored May 11, 2014 and Matthew Dawson committed Jul 01, 2014

In the previous version, output value is set to begin with 0 and increase by 1 each column, like 0,1,2,3...
Now the output value is really aquired from its corresponding cells.

Yanjun Jiang authored May 02, 2014 and Matthew Dawson committed Jul 01, 2014

Until now we have test cases for one layer table, two layers table, three layerstable and one Simple Insulin Infusion Pump (IIP) table.

Yanjun Jiang authored Apr 28, 2014 and Matthew Dawson committed Jul 01, 2014

For now, only single output single grid tables are supported, and only with simple one operator expressions.
Each row in the conditions grid corresponds a single event in EventB, with each cell in the row corresponding to a guard for the event.

A missing throw keyword allowed an exceptional circumstance to continue, when
an enumeration name conflicted with either another enumeration name or with
a variable.  Add appropriate tests to catch such issues and add the throw
keyword.