default estimator type

[axelpale]

Current nudged.estimate throws an error if estimator property is not defined.

This could be improved by:

• select a default estimator type, for example TSR, if the property is not defined.

However, this change can introduce hard-to-detect bugs if the user wrongly remembers or types the property name. For example if the user writes type: 'TS' or estimate: 'TS' instead of estimator: 'TS' then the bug will be found only after an unexpected multi-pointer rotation occurs.

[axelpale]

Additionally, a missing or bad estimator property currently throws a misleading toUpperCase error.

Likely the best course is to check availability of params.estimator and throw a proper error message if the property is missing.

[axelpale]

Additionally, there is a bug in the default switch case of the estimate function, near line 80. The error message should read params.estimator but it reads params.type instead. Replace it with params.estimator.

The bug can be seen in the error message:

> nudged.estimate({
  estimator: 'RRR',
  domain: ...
  range: ...
})
Uncaught Error: Unknown estimator type: undefined

The correct error message should be Uncaught Error: Unknown estimator type: RRR.