** Using WeBWorK **

I think I have solved this issue. If say $mo->{correct_ans} is something like the string x+1=2/3, then I think I can use contextTypeset.pl to create Formula($mo->{correct_ans}), which in this case should output as the string x+1=\frac{2}{3}, and I will use this as the correct_ans_latex_string in the answer checker.

I'm not sure that this workaround should be necessary if everything is working as intended. Generally Compute("xyz") crates an object where something very close to the literal xyz will show up as the correct answer. But in the case of ImplicitPlanes, while correct_ans seems to follow this principle, correct_ans_latex_string does not.