search for: standardise

Dear Rusers, I want to standardise the values of x/y coordinates to the unit square, i.e. make the x-values all lie within [0,1] and all the y-values lie within [0,1] in the bottom example. I had thought to use scale() function to do it, but it seems that it's used to standardise a variable and the scaled value was not within [...

Hi I have a data comprised of repeated measures of growth (5-15 records per individual) for 580 fish (similar to Orange dataset from nlme library). I would like to standardise these growth measures (yi – ŷ/sd) using mean and standard deviation unique to each fish. Can someone suggest a function that would help me do this? I’ve had a look at scale and sweep but can’t find a worked example that does what I’m after Cheers John [[alternative HTML version deleted]]

...ve the greater effect on a local atmospheric variable. The data is taken from a database that has 20391 data points (Z1). A simplified version of the data I'm looking at is given below, but I have a problem in that there is a disagreement in sign between the regression coefficients and the standardised regression coefficients. Intuitively I would expect both to be the same sign, but in many of the parameters, they are not. I am aware that there is a strong opinion that using standardised correlation coefficients is highly discouraged by some people, but I would nevertheless like to see the...

...dard deviations of the principal components'. However, when I calculate the principal components for the USArrests data set, I don't find this to be the case: Here is how I calculated the principal components and got the 'sdev' values: > scaledUSArrests <- scale(USArrests) # standardise the variables to have variance 1 and mean 0 > myPCA <- princomp(scaledUSArrests) # do the PCA > myPCA$sdev Comp.1 Comp.2 Comp.3 Comp.4 1.5590500 0.9848705 0.5911277 0.4122639 As far as I understand, the principal components themselves are stored in the 'scores' valu...

Dear All, I am a undergraduate using R for the first time. It seems like an excellent program and one that I look forward to using a lot over the next few years, but I have hit a very basic problem that I can't solve. I want to produce a standardised histogram, i.e. one where the area under the graph is equal to 1. I look at the manual for the histogram function and find this: freq: logical; if 'TRUE', the histogram graphic is a representation of frequencies, the 'counts' component of the result; if ...

Dear R-users, I need to standardize residuals using standard deviation. Is the 'stdres' the proper function? Beside other methods (for standardization and normalization), are there some approaches how to standardize using standard deviation? Here is the sample of my residuals: Zres040 Zres0820 Sres040 Sres0820 PCres040 -2.101740 -2.0682900 1.6328500 0.5046730

...ant to standardize the vars 1-3 (actually - there are many more) by class, so I define z.mean.sd <- function(data){ return.values <- (data - mean(data)) / (sd(data)) return(return.values) } now I can call for each var z.var1 <- by(df.vars$var1, group, z.mean.sd) which gives me the standardised data for each subgroup in a list with the subgroups z.var1 <- unlist(z.var1) then gives me the z-standardised data for var1 in one vector. Great! Now I would like to do this for the whole dataframe, but probably I am not thinking vectorwise enough. z.df.vars <- by(df.vars, group, z.m...

...CHABLE executed at <filepath> report_fatal_error failures: LLVM ERROR: this is the message Looking at the existing output, and how they are used, I think llvm_unreachable and assertions do not need standardising, since they are purely for internal usage, whilst report_fatal_error should be standardised to the same as other normal errors (i.e. lower-case first letter, trailing full stop). What do people think? James -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200323/3b6f7e3c/attachment.html>

The biggest problem with Vorbis comments are too loose specifications and too little standardisation. Another problem is attribution of involved parties. Currently only the ARTIST field name is supported in software. More standardised field names need to be worked out for organisations and persons involved in the production of the recording. See: http://wiki.xiph.org/index.php/VorbisComment#Attributing_involved_parties I have made a some suggestions, but as I have said earlier: Vorbis comments are no good when it comes to i...

yes this is darkice. perhaps we could work in 'icy-public' support...? --mark On Tuesday, Jul 8, 2003, at 19:58 US/Pacific, Arc wrote: > On Tue, Jul 08, 2003 at 03:40:42PM -0500, oddsock wrote: >> what source client is generating that ? > > I believe they run darkice, Mark Burdett would have to supply more > specific details as this is a relay of their lofi-mp3

...nd entering these, but again this is incorrect. This language is from the following: lm.LMtests(model, listw, zero.policy=FALSE, test="LMerr", spChk=NULL) Arguments model - an object of class lm returned by lm listw - a listw object created for example by nb2listw, expected to be row-standardised (W-style) Any help is welcomed. Thanks. -Jill *************************************************** Jill L. Caviglia-Harris, Ph.D. Assistant Professor Economics and Finance Department Salisbury University Salisbury, MD 21801-6860 phone: (410) 548-5591 fax: (410) 546-6208

...; kernel function may have an additional parameter which is a pointer to > __local memory space, which would not be necessary on GPUs. Then in > fact you would use a standard calling convention on a CPU. > > But for GPUs, I think using the calling convention is appropriate. > If we standardise the calling convention number, this can be the > default behaviour. I don't think we want LLVM-IR coming from an OpenCL C frontend to be different for GPU and CPU targets. In my view, the frontend should be parameterised by only two (more or less) parameters: bitness (32/64) and endianness...

...or), when the effect of other factors have been accounted for. The model is of the form: fit<-glm(Y~Year+Mo+Area+Ship+Eff,family=gaussian(link="log"),data=data) where Year is categorical and has T levels (labeled 1 to T in the data). Help much appreciated on how to extract these 'standardised' annual estimates of Y and their standard errors. Rub?n

Does anyone out there already have a utility to rename ogg files based on the tags? I want to re-standardise on "[track number] - [artist] - [track name].ogg" but my files are currently not that. It should be easy enough, as everything is tagged, but I'm sure someone else has written this already. Or are there Perl libraries to read tags? Otherwise I'll have to do it then donate it to th...

...veloper_database: &developer_database adapter: mysql username: me password: something host: 127.0.0.1 development: <<: *developer_database database: foobar_development test: <<: *developer_database database: foobar_test This was done so that the database names are standardised across developers but the details of the actual database connection are modifiable by the developer (another developer will alter *just* the details in developer_database). What I''d like is to have the ''development'' and ''test'' entries in config/databas...

Hi I know how to referenc R in a scientific paper - but is there a standardised way to reference packages? Thanks Rainer -- NEW EMAIL ADDRESS AND ADDRESS: Rainer.Krug at uct.ac.za RKrug at sun.ac.za WILL BE DISCONTINUED END OF MARCH Rainer M. Krug, Dipl. Phys. (Germany), MSc Conservation Biology (UCT) Plant Conservation Unit Department of Botany University of Cape Tow...

Dear all, I am looking for some interactive study materials on Principal component analysis. Basically I would like to know what we are actually doing with PCA? What is happening within the dataset at the time of doing PCA. Probably a 3-dimensional interactive explanation would be best for me. I have gone through some online materials specially Wikipedia etc, however what I need a "movable

Hello folks. I''ve got a problem that I can''t work out the solution to. My base workstation node definition says essentially: node base-workstation { file { etc-sudoers: name => "/etc/sudoers", ... } } This works fine, all of our workstations get a standardised sudoers file. However, I have one user on a workstation who needs a specialised sudoers file. If I define that file inside of the node definition, I get a duplicate definition error, which is right, it is a duplicate. Is there a clean solution to this kind of problem? --~--~---------~--~----~-...

...cf(((fit.res-mean(fit.res))/sd(fit.res))^2) fit.fore = predict(fit, n.ahead=test) ##Use ARIMA GARCH To fit residuals from ARIMA Model 1. fitted.gar<-garchFit(formula =~arma(2,1)+garch(1,1),data=*fit.res*,cond.dist = "std",trace=FALSE) sresi=fitted.gar@residuals/fitted.gar@sigma.t ###Standardised Residuals acf(sresi) acf(sresi^2) fore.res<-predict(fitted.ga, n.ahead=test) OR 2. fitted.gar<-garchFit(formula =~arma(2,1)+garch(1,1),data=*delta*,cond.dist = "std",trace=FALSE) sresi=fitted.gar@residuals/fitted.gar@sigma.t ###Standardised Residuals acf(sresi) acf(sresi^2) fore...

Update: I looked through VirtIO 1.0 and 1.1 specs, data format their, including byte order, is defined on a per-device type basis. RPMsg is indeed included in the spec as device type 7, but that's the only mention of it in both versions. It seems RPMsg over VirtIO isn't standardised yet. Also it looks like newer interface definitions specify using "guest native endianness" for Virtual Queue data. So I think the same should be done for RPMsg instead of enforcing LE? Thanks Guennadi On Mon, Jun 08, 2020 at 09:37:15AM +0200, Guennadi Liakhovetski wrote: > Hi Mic...