You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, TokenNumericValidator doesn't even accept E as part of a double, so it just ignores tokens with doubles in scientific notation. This is troublesome for problems using this validator because they usually ask for "full precision", and adding any formatting to the output introduces rounding errors and problem solvers don't know with what precision they should print them out with, and languages like C/C++ and Java just use scientific notation in the output when they see fit.
This all means that 1E-9 != 0.000000001, for example, which is not acceptable.
Context in Spanish on the omegaUp side here.
Currently,
TokenNumericValidator
doesn't even acceptE
as part of adouble
, so it just ignores tokens with doubles in scientific notation. This is troublesome for problems using this validator because they usually ask for "full precision", and adding any formatting to the output introduces rounding errors and problem solvers don't know with what precision they should print them out with, and languages like C/C++ and Java just use scientific notation in the output when they see fit.This all means that
1E-9 != 0.000000001
, for example, which is not acceptable.A possible solution is to:
e
andE
here.e
andE
into account here-
after theE
sThe text was updated successfully, but these errors were encountered: