balacij / cas-703-project Goto Github PK

When comparing real numbers, we should allow the user to define a tolerance value for equivalence of reals. Otherwise, equivalence of calculated real numbers will be nearly impossible.

I should have 3 expressions. One of them for condition and two for if and then.

The markdown renderer should give basic information about the calculator, the algorithm employed, and all symbols.

We should add the simulation/evaluation @hassanzaker proposed.

• Absolute value for numerics
• sin, cos, and tan for numerics
• round, ceil, and floor for real -> integer conversions
• itor for integer -> real conversion

If calculator 1 has output set A, and calculator 2 has input set subset of A, then we should be able to 'connect'/compose the calculators into 1 big calculator.

          Also, add Modulus, Greatethan, GreaterEqual, Lessthan, LessEqual, and NotEqual.

Originally posted by @hassanzaker in #26 (comment)

We should write a “code” renderer in some programming language. It might be good for us to avoid Java, and go to something else.

Specifically, we should know our:

1. "must have" requirements,
2. "nice to have" requirements, and
3. "we wanted, but not enough time/too difficult" requirements.

Prospective code snippet:

calculator potato with
	symbols
		constants
			x = 4 : Real m
			y = 10 : Real kg
		inputs
			n : Integer ~ Number of items
			a : Vector (Real m) n ~ Items
		intermediates
			b : Real m ~ Sum of items
		outputs
			c : Real m ~ Sum of items, doubled
	steps
		b = sum(a)
		c = 2 * a

We should have a syntax for defining test cases on the calculators. This should rely on the simulation to make sure that the calculator is actually ok.