Checks for bandwidth in stat_density_2d()
#6375
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to fix #6374
Briefly, it introduces some fallbacks and more informative error messages for calculating the bandwidth in
stat_density_2d()
.The reprex from the issue now runs without errors, due to fallbacks when
h = 0
to usestats::bw.nrd0()
instead ofMASS::bandwidth.nrd()
.Moreover, if the bandwidth is nonsense it will throw an error (demoted to warning by stats). Also noteworthy here is that the contouring step is skipped instead of throwing errors because there is no computed data from the 2D KDE step.
Created on 2025-03-21 with reprex v2.1.1