similar to: Cannot clean infinite values

Displaying 20 results from an estimated 30000 matches similar to: "Cannot clean infinite values"

2009 Apr 27
3
Cannot clean infinite values
Hello all, I have to import numeric data from file but found it contains Infinite values which need to be eliminated. I tried to replace them in this way: data[which(data=="-Inf")] <- -0.3 data[which(data=="+Inf")] <- 0.3 But, somehow, the Infinite values stayed there. Any suggestions? regards, N. -- View this message in context:
2008 Jan 04
1
PCA error: svd(x, nu=0) infinite or missing values
Hi, I am trying to do a PCA on my data but I keep getting the error message svd(x, nu=0) infinite or missing values >From the messages posted on the subject, I understand that the NAs in my data might be the problem, but I thought na.omit would take care of that. Less than 5% of my cells are missing data. However, the NAs are not regularly distributed across my matrix: certain cases and
2012 Jul 09
3
Package 'MASS' (polr): Error in svd(X) : infinite or missing values in 'x'
Hello, I am trying to run an ordinal logistic regression (polr) using the package 'MASS'. I have successfully run other regression classes (glm, multinom) without much problem, but with the 'polr' class I get the following error: " Error in svd(X) : infinite or missing values in 'x' " which appears when I run the "summary" command. The data file is
2010 Nov 16
1
How to pick out several infinite values when calculating means?
Dear r-help, I want to use tapply to calculate means for a variable. But there were several infinite values in the observations. How can I calculate means not considering these infinite values? Thanks in advance. Regards, Lei [[alternative HTML version deleted]]
2013 Feb 11
0
Error in R (ENFA) : Error in eigen(Se) : infinite or missing values in 'x'
Dear all, I am running an Ecological Niche Factor Analysis in R but I am stuck with a problem. As soon as I ask the software to compute the ENFA, I get the following error message: Error in eigen(Se) : infinite or missing values in 'x' Does anyone know what could be wrong. I do not have missing values in my dataset. Please follow the codes I used for my analysis so far: library
2006 Apr 28
2
cannot kill infinite loop. please help
an error in my rails code caused the framework to send an infinite number of SQL calls to the database. I killed the webrick server, restarted postgres, deleted the /tmp file in my rails application, deleted the bad code, restarted firefox, restarted the webrick server. All to no avail. As soon as I try loading my application, the infinite recursion starts again. I can no longer work. This
2012 Feb 03
3
Cannot get "==" operator to return TRUE
I have a data.frame named "df". The dput of df is at the bottom of this e-mail. What I'd like to do is replace the "n/a " values with NA. On Mac OSX, it works to do this: df[df == "n/a"] <- NA However, it does not work on Ubuntu. See below. Thanks in advance, Garrett > x <- df[27, 4] # complete data.frame dput is below > dput(x) "n/a?"
2009 Jan 12
1
Error in svd(S) : infinite or missing values in 'x'
Hi everyone. I was running correspondence analysis in R with the package 'ca' and I got a error message that I could not solve. > summary(ca(gui)) Error in svd(S) : infinite or missing values in 'x' #where gui is my dat table as follows: 0 90 1 1 0 90 0 0 0 90 5 1 0 95 1 0 0 0 0 0 85 0 0 0 50 0 0 0 90 0 0 0 75 0 0 0 75 0 0 0 0 0 10 25 0 0 5 5 0 0 50 10 0 0 10 20 0 0 1 10 0 0
2011 Nov 05
1
Error in eigen(a$hessian) : infinite or missing values in 'x'
Dear R-users, I'm estimating a two- dimensional state-space model using the FKF package. The resulting log likelihood function is maximized using auglag from the Alabama package. The procedure works well for a subset of my data, but if I try to use the entire data set I get the following error message. Error in eigen(a$hessian) : infinite or missing values in 'x' What's even
2023 Feb 11
1
scan(..., skip=1e11): infinite loop; cannot interrupt
Hello, All: I have a 4.54 GB file that I'm trying to read in chunks using "scan(..., skip=__)". It works as expected for small values of "skip" but goes into an infinite loop for "skip=1e11" and similar large values of skip: I cannot even interrupt it; I must kill R. Below please find sessionInfo() with a toy example. My real problem is a large
2002 Jun 20
0
[R] cut with infinite values -> NA (PR#1694)
You are correct in your expectations. This is a bug: the C code does not cover the cases +/-Inf (because it uses R_FINITE to exclude them). I'll fix it in R-patched: filing with R-bugs for the record. On 20 Jun 2002, Markus [ISO-8859-1] Jäntti wrote: > I am doing work on changes in establishment sizes and came across > behavior that is quite understandable and easily worked around
2003 Sep 28
1
infinite recursion during package installation with methods, setAs
I ran into a problem recently trying to update a package which uses S4 methods using a recent beta of R. I think I can reproduce it with a simple example. I have package called `testpkg' in directory testpkg/. In the R/ subdirectory of testpkg/ I have a file called testpkg.R which contains the following two lines: setClass("testpkg", representation(pts = "list"))
2010 Nov 24
0
[LLVMdev] how to eliminate dead infinite loops?
On Nov 23, 2010, at 9:22 AM, Andrew Clinton wrote: > Most of my programs contain loops that the LoopDeletion pass is unable > to remove. It appears that the following code in LoopDeletion.cpp:152 > is the culprit: > > ScalarEvolution& SE = getAnalysis<ScalarEvolution>(); > const SCEV *S = SE.getMaxBackedgeTakenCount(L); > if
2010 Nov 24
2
[LLVMdev] how to eliminate dead infinite loops?
On 11/24/2010 03:36 PM, Nick Lewycky wrote: > Andrew Clinton wrote: >> Most of my programs contain loops that the LoopDeletion pass is unable >> to remove. It appears that the following code in LoopDeletion.cpp:152 >> is the culprit: >> >> ScalarEvolution& SE = getAnalysis<ScalarEvolution>(); >> const SCEV *S =
2010 Nov 26
1
[LLVMdev] how to eliminate dead infinite loops?
Andrew Clinton wrote: > On 11/25/2010 12:59 PM, Andrew Clinton wrote: >> On 11/24/2010 06:55 PM, Owen Anderson wrote: >>> On Nov 23, 2010, at 9:22 AM, Andrew Clinton wrote: >>> >>> >>>> Most of my programs contain loops that the LoopDeletion pass is unable >>>> to remove. It appears that the following code in LoopDeletion.cpp:152
2012 Nov 14
2
[LLVMdev] Is infinite empty loop dead code?
On Wed, Nov 14, 2012 at 03:32:53PM +0800, 陳韋任 (Wei-Ren Chen) wrote: > On Tue, Nov 13, 2012 at 11:23:02PM -0800, Shuxin Yang wrote: > > Hi, All: > > > > Is it legal to delete empty infinite loop like this : "while(1) {}"? > > It is interesting that both llvm and gcc keep the loop, however Open64 > > delete it. > > I think it's illegal
2010 Nov 24
0
[LLVMdev] how to eliminate dead infinite loops?
Andrew Clinton wrote: > Most of my programs contain loops that the LoopDeletion pass is unable > to remove. It appears that the following code in LoopDeletion.cpp:152 > is the culprit: > > ScalarEvolution& SE = getAnalysis<ScalarEvolution>(); > const SCEV *S = SE.getMaxBackedgeTakenCount(L); > if (isa<SCEVCouldNotCompute>(S)) > return
2012 Nov 14
0
[LLVMdev] Is infinite empty loop dead code?
Following loop (in asm) is often seen in embedded programs. It is used to delay for certain amount of time. If it were not written in asm, compiler would blindly delete the entire loop. How can compiler know such DCE betray program intention? for (i = 0; i < N; i++) { nop; nop; nop } I guess in the gray area, if programmer do not want compiler do something he doesn't expect, he/she
2002 Jun 20
1
cut with infinite values -> NA
I am doing work on changes in establishment sizes and came across behavior that is quite understandable and easily worked around but a little surprising. On R 1.5.1 on Debian unstable (see below for R.version output): > cut.off <- c(-Inf, 0, Inf) > x <- c(-Inf, -10, 0, 10, Inf) > is.numeric(x) [1] TRUE > is.double(x) [1] TRUE > # but > cut(x, cut.off, include.lowest=T) [1]
2023 Mar 13
0
scan(..., skip=1e11): infinite loop; cannot interrupt
With ?if?(!j--)?{ ?????R_CheckUserInterrupt(); ?????j?=?10000; ?} as?in?current?R?devel?(r83976),?j goes negative (-1) and interrupt is checked every 10001 instead of 10000. I?prefer ?if?(!--j)?{ ?????R_CheckUserInterrupt(); ?????j?=?10000; ?} . In?current?R?devel?(r83976),?if?EOF?is?reached,?the?outer?loop?keeps?going,?i?keeps?incrementing?until?nskip.