search for: selivanov

...ector, not a matrix . ??, 21 ????. 2018 ?. ? 20:54, Rui Barradas <ruipbarradas at sapo.pt>: > Hello, > > Use drop = FALSE. > > a[1, , drop = FALSE] > # col1 > #row1 1 > > > Hope this helps, > > Rui Barradas > > ?s 16:51 de 21/11/2018, Dmitriy Selivanov escreveu: > > Hello here. I'm struggling to understand R's subsetting behavior in > couple > > of edge cases - subsetting row in a single column matrix and subsetting > > column in a single row matrix. I've read R's docs several times and > haven't > &...

Hi mailing list and R-core. Could someone from R-core please help me to create account in bugzilla? I would like to submit issue related to gc() to wishlist. Related context is here - https://stat.ethz.ch/pipermail/r-devel/2017-July/074715.html -- Regards Dmitriy Selivanov [[alternative HTML version deleted]]

2017-08-11 16:00 GMT+02:00 Martin Maechler <maechler at stat.math.ethz.ch>: >>>>>> Dmitriy Selivanov <selivanov.dmitriy at gmail.com> >>>>>> on Fri, 11 Aug 2017 17:33:31 +0400 writes: > > > Hi mailing list and R-core. Could someone from R-core please help me to > > create account in bugzilla? I would like to submit issue related to gc() to >...

...ld use 'adrop()' from the 'abind' package: abind:: adrop(a[1,,drop=FALSE], drop=1) first subsets, then drops the row-dimension, so gives what you're looking for. Hope this solves your problem. Best regards, Emil Bode ?On 21/11/2018, 17:58, "R-devel on behalf of Dmitriy Selivanov" <r-devel-bounces at r-project.org on behalf of selivanov.dmitriy at gmail.com> wrote: Hi Rui. Thanks for answer, I'm aware of drop = FALSE option. Unfortunately it doesn't resolve the issue - I'm expecting to get a vector, not a matrix . ??, 21 ????. 2018 ?...

...uot;, "row2"), c("col1"))) a[1, ] # 1 It returns *unnamed* vector `1` where I would expect named vector. In fact it returns named vector when number of columns is > 1. Same issue applicable to single row matrix. Is it a bug? looks very counterintuitive. -- Regards Dmitriy Selivanov [[alternative HTML version deleted]]

...rbanek" < simon.urbanek at r-project.org> ???????: > > > On Aug 11, 2017, at 12:57 PM, I?aki ?car <i.ucar86 at gmail.com> wrote: > > > > 2017-08-11 16:00 GMT+02:00 Martin Maechler <maechler at stat.math.ethz.ch>: > >>>>>>> Dmitriy Selivanov <selivanov.dmitriy at gmail.com> > >>>>>>> on Fri, 11 Aug 2017 17:33:31 +0400 writes: > >> > >>> Hi mailing list and R-core. Could someone from R-core please help me to > >>> create account in bugzilla? I would like to submit issue r...

Dmitriy Selivanov (selivanov.dmitriy at gmail.com) wrote: > Consider following example: > > a = matrix(1:2, nrow = 2, dimnames = list(c("row1", "row2"), c("col1"))) > a[1, ] > # 1 > > It returns *unnamed* vector `1` where I would expect named vector. In fact > i...

>>>>> Dmitriy Selivanov <selivanov.dmitriy at gmail.com> >>>>> on Fri, 11 Aug 2017 17:33:31 +0400 writes: > Hi mailing list and R-core. Could someone from R-core please help me to > create account in bugzilla? I would like to submit issue related to gc() to > wishlist. I wil...

Hi All, I have problem with fonts. Some texts in programs running under wine aren't displayed. Problem is mainly with texts that describe some input boxes. There's a screenshot of Skype attached. wine version: 20040213 system: Mandrake 9.2 Problem occured with: Baldurs Gate 2 Skype TeamSpeak2rc2 I've tried: - coppying windows fonts to ~/.wine/c_drive/windows/Fonts - changing

On Sat, 12 Aug 2017, Dmitriy Selivanov wrote: > Strange because in my all my experiments calling malloc.trim always helped > - memory reported by top decreased to the level it supposed to be. Do you > have in mind case when calling malloc.trim won't do anything? Also > shouldn't MALLOC_TRIM_THRESHOLD_ env variable h...

> On Aug 11, 2017, at 12:57 PM, I?aki ?car <i.ucar86 at gmail.com> wrote: > > 2017-08-11 16:00 GMT+02:00 Martin Maechler <maechler at stat.math.ethz.ch>: >>>>>>> Dmitriy Selivanov <selivanov.dmitriy at gmail.com> >>>>>>> on Fri, 11 Aug 2017 17:33:31 +0400 writes: >> >>> Hi mailing list and R-core. Could someone from R-core please help me to >>> create account in bugzilla? I would like to submit issue related to gc() to &...

...ented in blazer. Am I right ? Offcourse, I can workaround this problem: NOTIFYCMD /usr/local/sbin/check_lowbatt /usr/local/sbin/check_lowbatt uspc myups | grep battery.charge res=$? ... But it's an ugly hack... Is there any better solution ? I missed something ? -- Thanks in advance. Pavel Selivanov

On 12 August 2017 at 15:10, luke-tierney at uiowa.edu wrote: | As the Python posts poitns out, it is possible to use alternate malloc | implementations, either rebuilding R to use them or using LD_PRELOAD. | On Ubuntu for example, you can have R use jemalloc with | | sudo apt-get install libjemalloc1 | env LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libjemalloc.so.1 R | | This does not seem to hold

...scratched my head because there were no such problem on my laptop running on OS X!). So I'm not sure that such problem can be ignored. Consider following examples - we will create large list with many small objects (code which contains fully reproducible example here - https://gist.github.com/dselivanov/d2ff0435a352424d2c7329d918293946): large_list = lapply(1:1e6, function(i) { runif(100) }) rm(large_list) gc() After that on OS X *resident memory* memory successfully shrinks to ~ 100mb, but on Ubuntu is remains at ~ 1gb. I understand that this 1gb of ram can be (and will be) reused for allocat...

...rly, if someone cared, I could (presumably) alter the default R build > for Debian and Ubunto to also switch to jemalloc. > > Anybody feel like doing some empirics? > > Dirk > > -- > http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org > -- Regards Dmitriy Selivanov [[alternative HTML version deleted]]

...Sebastian Meyer and investigated by more helpers in PR#16184. * Low-level socket read/write operations have been fixed to correctly signal communication errors. Previously, such errors could lead to a segfault due to invalid memory access. Reported and debugged by Dmitriy Selivanov in PR#17850. * quantile(x, pr) works more consistently for pr values slightly outside [0,1], thanks to Suharto Anggono's PR#17891. Further, quantile(x, prN, names=FALSE) now works even when prN contains NAs, thanks to Anggono's PR#17892. Ditto for ordered fact...

...Sebastian Meyer and investigated by more helpers in PR#16184. * Low-level socket read/write operations have been fixed to correctly signal communication errors. Previously, such errors could lead to a segfault due to invalid memory access. Reported and debugged by Dmitriy Selivanov in PR#17850. * quantile(x, pr) works more consistently for pr values slightly outside [0,1], thanks to Suharto Anggono's PR#17891. Further, quantile(x, prN, names=FALSE) now works even when prN contains NAs, thanks to Anggono's PR#17892. Ditto for ordered fact...

...Sebastian Meyer and investigated by more helpers in PR#16184. * Low-level socket read/write operations have been fixed to correctly signal communication errors. Previously, such errors could lead to a segfault due to invalid memory access. Reported and debugged by Dmitriy Selivanov in PR#17850. * quantile(x, pr) works more consistently for pr values slightly outside [0,1], thanks to Suharto Anggono's PR#17891. Further, quantile(x, prN, names=FALSE) now works even when prN contains NAs, thanks to Anggono's PR#17892. Ditto for ordered fact...