Hansjörg Neth

Started to re-structure `plot.FFTrees()`, but splitting into multiple parts (e.g., ROC curve as separate function) may facilitate maintenance. When trying to call `showcues()` with `data = "test"` (e.g., `plot(heart.fft, data...

The release of **FFTrees** 1.7.0 has fixed the most obvious plotting issues, but the corresponding code is still pretty bulky and should be simplified further. Beyond additional cleanups, I'd advocate...

I'd consider the most immediate needs to be addressed in the recent release of **FFTrees** version 1.7.5 (on 2022-09-15). However, as new ideas/needs may arise and `plot.FFTrees()` is still pretty...

PR #95 has addressed the bug, but still uses the `data` argument for both string and data frame inputs. Additionally, the issue of locally vs. globally changing an `FFTrees` object...

I now see the _missing value_ topic as part of a much larger issue that essentially asks "What should be done when we lack knowledge?". Apart from ignoring or guessing,...

**Thanks** for raising this topic again! I've been planning to address the problem of missing inputs for a while, but always been distracted by more immediate issues. Based on the...

I fully agree — and trusting your gut feelings is usually a good idea. So yes, PR whatever you have — I'd be happy to help when I can.

Thanks, Nathaniel, for your PRs on this issue! As I was chasing another bug simultaneously (which led to perfect FFTs not being found, since `grow_tree == FALSE` for cases of...

Including `NA` values in **categorical** (character, factor, or logical) predictors seems to work pretty well now, so the primary issue here could be considered to have been solved. However, I'm...

**A status update** (on the discussion above and the **reprex** results): As it turns out, allowing for `NA` values in **numeric predictors** is more complicated than we thought. Adding some...