Displaying 4 results from an estimated 4 matches for "if_ani".
Did you mean:
if_any
2024 Apr 13
1
any and all
Hi Avi,
As D?nes T?th has rightly diagnosed, you are building an "all or
nothing" filter. However, you do not need to explicitly spell out all
columns that you want to filter for; the "tidy" way would be to use a
helper function like `if_all()` or `if_any()`. Consider this example (I
hope I understand your intentions correctly):
```
library(dplyr)
data <- tribble(
2024 Apr 12
2
any and all
Base R has generic functions called any() and all() that I am having trouble
using.
It works fine when I play with it in a base R context as in:
> all(any(TRUE, TRUE), any(TRUE, FALSE))
[1] TRUE
> all(any(TRUE, TRUE), any(FALSE, FALSE))
[1] FALSE
But in a tidyverse/dplyr environment, it returns wrong answers.
Consider this example. I have data I have joined together with pairs of
2017 Jun 05
0
[PATCH v3 1/7] pmu/fuc: add macros for pmu engine counters
v2: removed definitions we won't need anymore
v3: rename IF_NOT_ALL to IF_ANY
Signed-off-by: Karol Herbst <karolherbst at gmail.com>
Reviewed-by: Martin Peres <martin.peres at free.fr>
---
drm/nouveau/nvkm/subdev/pmu/fuc/macros.fuc | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drm/nouveau/nvkm/subdev/pmu/fuc/macros.fuc b/drm/nouveau/nvkm/subdev/pmu/fuc/macros.fuc
2017 Jun 05
7
[PATCH v3 0/7] PMU engine counters
I think I am done reworking the series and getting to a point where I think
it is basically finished. The configuration of the slots could be improved
later on when working on dynamic reclocking, but for now it's good enough to
report the current GPU utilization to userspace.
Patches 1-4 imeplement PMU commands to setup and readout the counters.
Patches 5-6 lets Nouveau make use of 1-4.
Patch