search for: trimmed

subject: trimmed mean in R seems to round the trimming fraction to r-help at stat.math.ethz.ch. Consider the following example of 10 numbers. 10% trimmed mean is correct but you can see that the result is the same for many trimming fractions till 0.20! For example 13% trimmed mean should use interpolation of sec...

My google-fu is coming up short on this one... I didn''t see that it had been discussed in a while ... What is the status of ZFS support for TRIM? For the pool in general... and... Specifically for the slog and/or cache??? -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hey guys, Pasi mentioned on Li''s (and Owen''s) patches which provide TRIM/UNMAP support to the Linux backend/frontend that: " Isn''t the generic name for this functionality "discard" in Linux? and "trim" being the ATA specific discard-implementation, and "scsi unmap" the SAS/SCSI specific discard-implementation? Just

Hello r helpers! Below is the whole coding for my programme. Before proceed more further, let me explain for you. First of all, I need to compute trimmed mean. Till that step is ok. Then I need to compute ssdw which is sum of square deviation. If I do equal trimming at both tail of distribution that I chose, I will use the first ssd formulae which is "a". But if I am doing unequal trimming, then I will be using "b". My problem is...

(I see this in both R-patched r43124 and R-devel r43233.) In the Argument section of ?mean: trim the fraction (0 to 0.5) of observations to be trimmed from each end of x before the mean is computed. Values outside that range are taken as the nearest endpoint. Then in the Value section: If trim is non-zero, a symmetrically trimmed mean is computed with a fraction of trim observations deleted from each end before the mean is computed. The desc...

Hi! With 3.2-rc4 (probably earlier), Ext4 seems to remember what areas it trimmed: merkaba:~> fstrim -v /boot /boot: 224657408 bytes were trimmed merkaba:~> fstrim -v /boot /boot: 0 bytes were trimmed But BTRFS does not: merkaba:~> fstrim -v / /: 4431613952 bytes were trimmed merkaba:~> fstrim -v / /: 4341846016 bytes were trimmed Is it planned to add this...

Hi all, I am looking for a function in R to trim the last two characters of an 8 character string in a vector. For example, I have the codes 37-079-2, 370079-3,37-079-8 and want to trim them to 37-079 by removing the last two characters. Is sub the correct function to use, and if so how can I specify trimming the last 2 characters? I have read the help file, but can't quite figure out how

My apologies, I know that this is not a new problem, but I'm not sure how to find the answer I want to recursively loop over an object and trim trailing white space. When I use this function on a list of data.frame I get output like this: [1] "c(\" many spaces \", \" many spaces \")" "c(\" many spaces \", \" many spaces

Am 10.04.2018 um 15:03 hat Nir Soffer geschrieben: > On Tue, Apr 10, 2018 at 1:44 PM Richard W.M. Jones <rjones@redhat.com> > wrote: > > > We now have true zeroing support in oVirt imageio, thanks for that. > > > > However a problem is that ‘qemu-img convert’ issues zero requests for > > the whole disk before starting the transfer. It does this using 32 MB

I feel like an idiot posting this because every language I've ever seen has a string function that trims blanks off strings (off the front or back or both). Ideally, it would process whole data frames/matrices etc but I don't even see one that processes a single string. But I've searched and I don't even see that. There's a strtrim function but it does something completely

Hi, Need to get an answer to the following. I find the naming to be little redundant regarding the 'input.transfer.boost.low - hige'. The same goes for input.transfer.trim.low - high. As I find it, there is only one point where the boost or buck (trim) kicks in. Let's say that the nominal voltage is 230 volt, then we have a input.transfer.boost point on say 220 volt. If the

Dear all, I sometimes use the following function: Curry <- function(FUN,...) { # by Byron Ellis, https://stat.ethz.ch/pipermail/r-devel/2007-November/047318.html .orig <- list(...) function(...) do.call(FUN,c(.orig,list(...))) } ... and have thought it might be convenient to have a method for [ doing this. As a simple example, > apply(M, 1, mean[trim=0.1]) # hypothetical

We already have support in the file driver for punching holes during .zero with the may_trim flag (via FALLOC_FL_PUNCH_HOLE), so we should use the same mechanism to support .trim. Note that the NBD spec says that trim is advisory (we can return success even if we did nothing); but at the same time, it's nicer to avoid advertising the feature if we know for sure we can't do it, so we also

On Jan 10, 2014, at 12:58 PM, Elliot Dierksen wrote: > I am using NUT 2.6.5 as part of FreeNAS 9.2.0. I am using an APC Smart-UPS > 5000 RM DL4 with a AP9619 network management card. NUT properly detects > when the UPS goes on battery and initiates a shutdown after the configured > time. The problem I have is that I am using a 208V unit on a 240V circuit. > That means the normal

...ig.mark="," and trim=TRUE. E.g.: > # works ok as long as big.mark is not actually used: > format(c(-1,1,10,999), big.mark=",", trim=TRUE) [1] "-1" "1" "10" "999" > # but if big.mark is used, output is justified and not trimmed: > format(c(-1,1,10,999,1e6), big.mark=",", trim=TRUE) [1] " -1" " 1" " 10" " 999" "1,000,000" > The documentation for the argument 'trim' to format.default() states: trim: logical; if 'F...

I am using NUT 2.6.5 as part of FreeNAS 9.2.0. I am using an APC Smart-UPS 5000 RM DL4 with a AP9619 network management card. NUT properly detects when the UPS goes on battery and initiates a shutdown after the configured time. The problem I have is that I am using a 208V unit on a 240V circuit. That means the normal state for the UPS is "TRIM". NUT doesn't treat that as an on line

We now have true zeroing support in oVirt imageio, thanks for that. However a problem is that ‘qemu-img convert’ issues zero requests for the whole disk before starting the transfer. It does this using 32 MB requests which take approx. 1 second each to execute on the oVirt side. Two problems therefore: (1) Zeroing the disk can take a long time (eg. 40 GB is approx. 20 minutes).

I am looking for a way to trim leading and trailing spaces in a character string in R. For example: "       this is random text        " should become: "this is random text". I have a short function to perform this task as follows: trim <- function(str){        str <- sub("^ +", "", str)        str <- sub(" +$", "", str) }

Both of the following should return NA, but do not in "R version 2.11.0 Under development (unstable) (2010-03-07 r51225)" on 32-bit Windows: > mean(c(1,10,100,NA), trim=.1) Error in sort.int(x, partial = unique(c(lo, hi))) : index 4 outside bounds > mean(c(1,10,100,NA), trim=.26) [1] 55 With na.rm=TRUE they give the correct results. (mean() would be so much simpler

Hi I installed a new SSD in my Macbook running Arch Linux (Kernel 3.1). root partition has btrfs with discard and ssd mount parameters. I wanted to test whether the discard option was actually working, so I performed a testing procedure similar to what is described on various websites. The test file was the output of "seq 100000 999999" which is about 6MB in size. Instead of looking up