search for: trim

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...

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: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20110129/56283ce0/attachment.html>

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...

(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 de...

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 th...

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...

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 \")" What should I do to recombine the results...

...gt; > 20 minutes). Furthermore there is no progress indication while this > > is happening. > > > > > Nothing bad happens: because it is making frequent requests there > > is no timeout. > > > > (2) I suspect that because we don't have trim support that this is > > actually causing the disk to get fully allocated on the target. > > > > The NBD requests are sent with may_trim=1 so we could turn these > > into trim requests, but obviously cannot do that while there is no > > trim support. &g...

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 differen...

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 voltage drop any more, it reach the 'input.transfer.low', when it would go to...

...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 equivalent to apply(M, 1, Curry(mean, trim=0.1)) would be easier to understand than passing arguments by ... > apply(M, 1, mean, trim=0.1) and much shorter than using an anonymous function > apply(M, 1, function(x) mean(x, trim=0.1) This would be much more useful...

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...

...mart-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 condition, so the system shuts down every time there is a > power failure. I'm confused. When the snmp-ups driver starts, does it immediately see the TRIM state and initiate a shutdown, or does this only happen after going on battery once...

DESCRIPTION OF PROBLEM: Output from format.default sometimes has whitespace around it when using big.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,...

...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 condition, so the system shuts down every time there is a power failure. I realize what I am doing is a bit of a kludge, but I can't get a 208V circuit easily in my house. I am also getting these messages whenever NUT starts "[CR-UPS] Warni...

...refore: (1) Zeroing the disk can take a long time (eg. 40 GB is approx. 20 minutes). Furthermore there is no progress indication while this is happening. Nothing bad happens: because it is making frequent requests there is no timeout. (2) I suspect that because we don't have trim support that this is actually causing the disk to get fully allocated on the target. The NBD requests are sent with may_trim=1 so we could turn these into trim requests, but obviously cannot do that while there is no trim support. Note that this is (sort of) a regression over prev...

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("^ +", "&q...

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 if we didn't have to worry about the seldom-used trim= argument.) Bill Dunlap Sp...

...da2 with "hexedit". After I found it deleted the file, did "sync" and even waited for two minutes (someone suggested sleep 120...), then opened hexedit on /dev/sda2 again, and jumped to the offset to see if the data was still there which it was. hdparm -I says the drive supports TRIM and does "Deterministic read after TRIM" which I interpret to mean that if the data was really discarded, the drive should return zeros (or something else) but not the previous data. So I am not familiar with neither internals of btrfs or SATA/IDE standards so I am clueless here. Is my t...