Malavika-Srinivasan / CAS741

Course Website for CAS 741
Other
0 stars 1 forks source link

MIS - Comments about notation #35

Closed bmaclach closed 5 years ago

bmaclach commented 5 years ago

Some question and comments about the notation used in the MIS:

bmaclach commented 5 years ago

Forgot one:

Malavika-Srinivasan commented 5 years ago
  1. think you should include the primitive type boolean in your table in section 4, and then when you later refer to booleans (section 6.4.1) just use the notation symbol B (\mathbb{B} in LaTeX) - Done

  2. For conditional rules, you sometimes use \Rightarrow and sometimes use \Longrightarrow. Is there a difference in the meaning between the two? If not, they should be made consistent. - They don't mean anything. Changes everything to \Longrightarrow

  3. n section 7.4.4 for interpHermite, for the y vector you introduce a notation where you have a superscript number in parentheses such as y0(1). What does this mean? - The superscript represents the derivative. (1) means first derivative. I made an explicit note of it in the document as well.

  4. When you specify the dimensions of an array, such as Rn-1Xm, I think it would be more readable if you used \times in LaTeX instead of "X", or just use a comma - changed to \times. Thanks.

  5. The notation you use for quantifiers doesn't quite match up with Hoffman and Strooper or Gries and Schneider, which were the references we talked about in class. For example, in section 6.4.4 for verifyInput you have "\forall x \in t \land x \notin R". I think this means that TypeError happens if every x in t is not a real number, but I think what you really want is for the error to happen if any x in t is not a real number, so you should use \exists instead of \forall. However I also do not recognize that specific notation, so maybe I'm wrong. Either way, you should specify in section 4 what notation you are using for quantifiers since it is not Hoffman and Strooper. - I changed the specific instances to \exists.

  6. Throughout section 8.4.4 there is xn and xm, which look like x to the power of n and m. I think these were intended to convey the size of x, so I think these should just say x, and then the type of x should be specified, where the type includes the size (like how you did it in section 7.4.4) - Changes made.