If an smtlib checker doesn't generate sample values, use an empty array so
the system can handle everything properly.

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/branches/TableTool_javization@11084 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

In preparation for enumerations, a more complete handling of variable information
is required.  Thus create a VariableCollection and use it appropriately.  As
much as possible, the VariableCollection is pushed down the stack as much as
possible.

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/branches/TableTool_javization@11083 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

VariableParser now needs to store information about custom types (specifically
enumerations).  Thus make parseVariable take an instance now by making it
a method of VariableParser again.  Also change the TET to use a global
singleton (called TET) to store the TET's VariableParser (since the type
information is global to Matlab).

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/branches/TableTool_javization@11082 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

Sometimes when starting up, a previous handle would clash with an existing
handle, causing the TET to fail to load and locking Matlab into a state
where it can no longer exit.  Fix by ensuring on load no previous handle
is ever used, and instead just regenerate all of them.

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@10858 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

Instead of having new instances of VariableParser created, and thus wrapping
a Map<String, Variable> in a very inelegant way, simply have a single method
that actually does the VariableParser work, and directly returns the Map.
Also ensure all tests + Matlab continue to work, and tighten up some extra
imports and Matlab output in affected areas.

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/branches/TableTool_javization@10846 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

The package name matlab2smt is really ugly, and not really representative of
what it really does anymore.  Thus create an expression package for the pieces
representing an expression, and a parsers package for all parsers, including
both the variable and the Matlab parsers.  Also make
MatlabParserOperatorParseTest not rely on (now) private members.  Instead
use the toString methods to get a generator independent representation, and
test that it matches appropriately.

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/branches/TableTool_javization@10845 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

Since the java code is turning into entire toolbox for dealing with tabular
expressions, move the code to an appropriate package.  Even if it doesn't
become a full toolbox (for java), it is deeply used by the Matlab toolbox.
Thus pull the name from there.

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/branches/TableTool_javization@10844 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

Show an option for checking against Z3, and also hook it up to the matlab
code for use.  Everything should be working now.

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/branches/TableTool_javization@10667 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@10096 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/branches/TableTool_javization@9679 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

Due to the fix for the newline issue with Matlab, there
was a buffer underflow.  Fix.


git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@9560 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@9529 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@8671 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

Fix some other issues.


git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@8566 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

If there are multiple lines in an input box, it breaks various things.  Fix that
up by concating them together.  Its a little better.


git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@8555 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

Due to matlab stupidity, it doesn't have an undo functionality in its
input boxes (why?).  The work around involves unfocusing and re-focusing the 
textbox.  In the meantime, the original bug I tried to fix is still out there.


git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@8552 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

There was some code making the input boxes multi-line, for no
reason.  It caused weird random errors though, so disable behaviour.


git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@8519 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

If this handle is deleted, make sure to mark it as such.  Otherwise,
there seems to be a double delete occuring and causing issues.


git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@8511 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@8196 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@8190 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@7726 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@7207 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@7047 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@7026 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

added setting to generate real-time exceptions when input is NaN or when input type constraint is violated

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@6878 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@6716 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@6715 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@6667 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@6620 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@6593 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@6587 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

updated GUI to generalize the typecheck procedure, default prover is now CVC, although this can be changed, currently not saved to the block, so each time you open it will go back to CVC, may want to change this in the future. need to fix some stuff in validation report

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@6562 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@6560 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@6520 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

begnining of application of SMT solver, using CVC3 solver. only works for 1D vertical grids right now, although easy to add more dimensions, etc. ALOT faster than PVS.

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@6519 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@6352 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@6351 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

have a mode working where tool will generate a theory using the simulink types, as well as an constraints expressed in the pvs types. for example if input is x:real, but in simulink diagram input is int8, will create a theory where input is of type int8, copies a pvs theory of the types to the pwd, currently using integer subranges for types, and real for floating pt types, not sure if I should use IEEE754, might lose test case generation with this. Typechecker forces proving that no over/under flow for outputs, this is not always automatic, and grind seems to have trouble with it sometimes.

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@6318 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

can now figure out compiled types of code block, could now use these types for proving, still need a way of consolidating types between input box and port definitions

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@6317 57e6efec-57d4-0310-aeb1-a6c144bb1a8b

edited code looking for unsuppressed output, need better way to do this, also removed the check system block from the block library, it still needs some work

git-svn-id: https://groke.mcmaster.ca/svn/grad/colin/trunk/TableTool@6239 57e6efec-57d4-0310-aeb1-a6c144bb1a8b