Displaying 3 results from an estimated 3 matches for "n_target".
Did you mean:
_target
2018 May 15
12
[PATCH libldm 00/12] New API: an ability to retrieve created device-mapper devices back after they have been created.
The main goal of these patch series is to implement a new API that allows to retrieve created device-mapper devices for volumes and partitions back after they have been created.
As part of this patch:
- required libdevmapper version was bumped to 1.02. I think it is safe because it was released more then 10 years ago;
- newer version of libdevmapper allowed to simplify code base a little bit;
-
2023 Dec 11
1
Partial matching performance in data frame rownames using [
Dear all,
I have seen that others have discussed the partial matching behaviour of
data.frame[idx,] in the past, in particular with respect to unexpected
results sets.
I am aware of the fact that one can work around this using either
match() or switching to tibble/data.table or similar altogether.
I have a different issue with the partial matching, in particular its
performance when used on
2023 Dec 13
1
Partial matching performance in data frame rownames using [
...}
> }
>
> + unsigned int ic = 9999;
> if(nexact < n_input) {
> /* Second pass, partial matching */
> for (R_xlen_t i = 0; i < n_input; i++) {
> @@ -1642,6 +1643,10 @@
> mtch = 0;
> mtch_count = 0;
> for (int j = 0; j < n_target; j++) {
> + if (!--ic) {
> + R_CheckUserInterrupt();
> + ic = 9999;
> + }
> if (no_dups && used[j]) continue;
> if (strncmp(ss, tar[j], temp) == 0) {
> mtch = j + 1;
>