Displaying 20 results from an estimated 3000 matches similar to: "(PR#7942) extra spaces before imag part when printing complex numbers"
2004 Jun 22
0
Re: (PR#7005) X11 , plot(...expression(...)): missing parentheses
Martin Maechler wrote:
> >>>>> "humbertc" == humbertc <humbertc@univ-mlv.fr>
> >>>>> on Tue, 22 Jun 2004 13:16:58 +0200 (CEST) writes:
>
> humbertc> Full_Name: Cyril Humbert
> humbertc> Version: 1.9.1
> humbertc> OS: Debian GNU/Linux (i386)
> humbertc> Submission from: (NULL) (193.50.159.2)
>
2005 Apr 27
0
(PR#7803) print.data.frame(), wrong column names alignement,
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--27464147-733928972-1114633091=:27258
Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
I've managed to solve this, but the major problem I had was not R but that=
=20
printf was not
2004 Jun 22
0
Re: (PR#7005) X11 , plot(...expression(...)): missing parentheses
>>>>> "humbertc" == humbertc <humbertc@univ-mlv.fr>
>>>>> on Tue, 22 Jun 2004 13:16:58 +0200 (CEST) writes:
humbertc> Full_Name: Cyril Humbert
humbertc> Version: 1.9.1
humbertc> OS: Debian GNU/Linux (i386)
humbertc> Submission from: (NULL) (193.50.159.2)
humbertc> Hello,
humbertc> For the X11 graphic
2002 Jun 27
3
plot(..., type="h") w/ origin not at y=0
Is it a way to make plots with vertical lines, like plot(x, y, type="h"),
but starting from a different value than y=0.
For example, with x=1:3, y=-(1:3), y.orig=-3 :
-1 |
|
y -2 | |
| |
-3 | | |
1 2 3
x
Thanks
--
Cyril Humbert
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-help mailing list --
2002 May 28
1
hitting ^C breaks readline history (PR#1606)
Full_Name: Cyril Humbert
Version: 1.5.0
OS: linux
Submission from: (NULL) (193.50.159.2)
Hitting ^C breaks readline history (when R is stared in an xterm).
xterm -e R
^C -> arrow key and history stop working.
For example, up-arrow gives "^[[A".
ldd ./R.bin
[../..]
libreadline.so.4.1 => /usr/lib/libreadline.so.4.1 (0x40020000)
libncurses.so.5 =>
2005 Apr 07
1
complex tangent (PR#7781)
Full_Name: Peter Fortini
Version: 2.0.1
OS: Windows 2000
Submission from: (NULL) (65.246.187.164)
When the imaginary part of the argument is very large, the complex tangent
function returns 0+NaNi. For example, tan(1+1000i)=0+NaNi; it should be 0+1i
Easy to fix in complex.c, as the original NaN came from division of sinh and
cosh that had reached machine infinity.
static void z_tan(Rcomplex
2010 Mar 25
2
print(big+small*1i) -> big + 0i
Should both parts of a complex number be printed
to the same precision? The imaginary part of 0
looks a bit odd when log10(real/imag) >=~ getOption("digits"),
but I'm not sure it is awful. Some people might
expect the same number of significant digits in the
two parts.
> 1e7+4i
[1] 10000000+0i
> 1e7+5i
[1] 10000000+0i
> 1e10 + 1000i
[1] 1e+10+0e+00i
>
2002 Mar 18
1
line breaks
I have a question about the function of line feeds/carriage returns in
an all linux (R, vi to write scripts) environment. In my scripts I have
a few functions, using { or ( to wrap commands on the next line.
Usually this is fine, but sometimes R appears confused by line wrappings
(more likely of course it is me who is confused). I tried ';' to
explictly break the line, but no dice.
An
2023 Nov 06
1
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
>>>>> Michael Chirico
>>>>> on Sun, 5 Nov 2023 09:41:42 -0800 writes:
> This is another follow-up to the thread from September
> "Recent changes to as.complex(NA_real_)".
> A test in data.table was broken by the changes for NA
> coercion to complex; the breakage essentially comes from
> c(NA, 0+1i)
> # vs
2023 Nov 08
1
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
So, to summarize, the open questions are:
(1) Should as.complex(NA_character_) give complex(r=NA_real_, i=0)
instead of NA_complex_?
(2) Should the first argument in c(NA, x) and c(NA_integer_, x),
where typeof(x) == "complex", be promoted to complex(r=NA_real_, i=0)
instead of NA_complex_?
My opinions:
(1) No. The imaginary part of the
2023 Nov 09
1
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
>>>>> Mikael Jagan
>>>>> on Wed, 8 Nov 2023 11:13:18 -0500 writes:
> So, to summarize, the open questions are:
> (1) Should as.complex(NA_character_) give complex(r=NA_real_, i=0)
> instead of NA_complex_?
> (2) Should the first argument in c(NA, x) and c(NA_integer_, x),
> where typeof(x) == "complex", be promoted
2016 Mar 18
1
formatting of complex matrix
While working on the printing code, my colleague Zbyn?k ?lajchrt noticed that complex matrixes are sometimes misaligned:
> { matrix(1i,2,13) }
[,1] [,2] [,3] [,4] [,5] [,6] [,7] [,8] [,9] [,10] [,11] [,12] [,13]
[1,] 0+1i 0+1i 0+1i 0+1i 0+1i 0+1i 0+1i 0+1i 0+1i 0+1i 0+1i 0+1i 0+1i
[2,] 0+1i 0+1i 0+1i 0+1i 0+1i 0+1i 0+1i 0+1i 0+1i 0+1i 0+1i 0+1i 0+1i
(the values in the last four columns
2023 Nov 07
1
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
Thanks Martin. My hang-up was not on what the outcome of as.complex(NA)
should be, but rather, how I should read code like c(x, y) generally. Till
now, I have thought of it like 'c(x, y)' is c(as(x, typeof(y)), y)` when
"type(y) > type(x)". Basically in my mind, "coercion" in R <->
as.<newtype>(.) (or coerceVector() in C).
So I tracked down the source
2009 Aug 02
1
Inaccurate complex arithmetic of R (Matlab is accurate)
Dear All,
Hans Borchers and I have been trying to compute "exact" derivatives in R using the idea of complex-step derivatives that Hans has proposed. This is a really, really cool idea. It gives "exact" derivatives with only a minimal effort (same as that involved in computing first-order forward-difference derivative).
Unfortunately, we cannot implement this in R as the
2010 Feb 15
1
[PATCH] drm/nouveau: fix pramdac_table range checking
On Mon, Feb 15, 2010 at 03:40:56PM +0300, Dan Carpenter wrote:
> This is the results from:
> make C=1 CHECK="/path/to/smatch -p=kernel" bzImage modules | tee warns.txt
> grep -w overflow warns.txt | uniq -f 3 | tee err-list
>
> I hacked on the buffer overflow check last weekend and these are the
> results. It has way more false positives than the other bug
2005 Jan 11
1
integrate() and complex values
[apologies for possible multiple post]
Hi
The manpage for integrate() does not mention imaginary numbers.
I found the following unexpected:
> integrate(function(x){0*x+1+1i},0,1)
1 with absolute error < 1.1e-14
>
(I would expect 1+1i here)
One can write a little wrapper, but it's not straightforward.
Would it be hard to accommodate such functions in integrate()?
Some other
2002 Oct 17
1
xyplot(y~x, type="l") with missing values (NA)
With the function plot(x, y, type="l") points are not connected
when x or y contain a missing value (NA). Is it possible to do
the same with the lattice function xyplot() ?
For example:
library(lattice)
x <- c(1, 2, NA, 4, 5)
y <- x
plot(x, y, type="l")
xyplot(y~x, type="l")
In the first plot, the point 2 is not connected to the point 4
whereas there are
2010 Mar 27
3
Calculate variance/covariance with complex numbers
Anybody knows what functions can be used to calculate
variance/covariance with complex numbers? var and cov don't seem to
work:
> a
1
V1 0.00810014+0.00169366i
V2 0.00813054+0.00158251i
V3 0.00805489+0.00163295i
V4 0.00809141+0.00159533i
V5 0.00813976+0.00161850i
> var(a)
1
1 1.141556e-09
Warning message:
In var(a) : imaginary parts discarded in
2016 Jun 03
0
complex NA's match(), etc: not back-compatible change proposal
With 'z' of length 8 below, or of length 12 previously, one may try
sapply(rev(z), match, table = rev(z))
match(rev(z), rev(z))
I found that the two results were different in R devel r70604.
A shorter one:
> z <- complex(real = c(0,NaN,NaN), imaginary = c(NA,NA,0))
> sapply(z, match, table = z)
[1] 1 1 2
> match(z, z)
[1] 1 1 3
An explanation of the behavior: With normal
2006 Jan 28
1
Complex Matrix Exponentials.
Hello,
I was curious if there was a complex valued matrix exponential function
available for R? I have some Laplace transforms of occupation times
for a hidden Markov model. The matrix exponential function in the msm
package does not seem to handle complex values. For example
> MatrixExp(diag(1i,2))
[,1] [,2]
[1,] 1 0
[2,] 0 1
Warning message:
imaginary parts