Hi,

tar.o.trueAnomaly can return nan, to be valid JSON this should be quoted, as in "nan" or similiar.

Thanks
Tim

I will fix this issue when I update the web pages to optionally use the web socket API. This is planned for the next week or so.

Thanks for the report!

No worries. FYI, according to RFC4627:

" Numeric values that cannot be represented as sequences of digits (such as Infinity and NaN) are not permitted."

and according to ECMA-262:
"Finite numbers are stringified as if by String(number). NaN and Infinity regardless of sign are represented as the string null."

Thanks
Tim