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
My fpCompare package deals with this for the basic relational operators, but having equivalent functionality to test intervals/ranges may be useful. Although, I recognize that this kind of change may break backwards compatibility / reproducibility without a mechanism (package option?) to use the alternate behaviour.
The text was updated successfully, but these errors were encountered:
@achubaty thanks for raising this issue. This is indeed a problem.
If I import the operators from fpCompare, and setting an option to intrval.use_fpCompare=FALSE for backwards compatibility. When this option is set to TRUE, I would use the fpCompare functions inside the internals with the set fpCompare.tolerance option.
Hi @achubaty intrval treats operators more holistically than numeric to numeric, and I get errors when I simply replace >= with %>=% etc. That is because:
This is a useful package, I'm sad I hadn't started using it sooner!
Have you considered using more robust comparisons to deal with floating point number problems? See below.
My
fpCompare
package deals with this for the basic relational operators, but having equivalent functionality to test intervals/ranges may be useful. Although, I recognize that this kind of change may break backwards compatibility / reproducibility without a mechanism (package option?) to use the alternate behaviour.The text was updated successfully, but these errors were encountered: