Displaying 20 results from an estimated 2000 matches similar to: "formatC with illegal input crashes Rgui (PR#7686)"
2005 May 03
2
memory problem
Hello!
I am undertaking my first attempt at using compiled C code within R and
have run into this lovely problem when I call my C code (using .C).
The instruction at "0x10001d1b" referenced memory at "0x01fa2000". The
memory could not be "written".
Now this doesn't happen every time and furthermore I've tested the code
in plain C and it all works
2005 Apr 25
2
Installing packages, again
Hi again,
I've just uninstalled R2.01 and installed the new R2.10 on my WindowsXP
machine. I then attempted to install the vegan package from source
files, as I learned to do last week, with the help of some of you. I
have updated my path variable to the new R directory (R/rw2010/bin
instead of R/rw2001pat/bin), and I've still got the HTMLHelpWorkshop
files installed, as well as Perl
2006 Jan 31
5
Queue() with timeout=0
Hello,
i've recently switched over from 1.0.9 to 1.2.3.
I've experienced some (to me) weird behaviour.
This is the config for an example queue.conf:
[654]
wrapuptime=30
timeout=20
strategy=ringall
retry=5
queue-youarenext=queue-youarenext
queue-thereare=queue-thereare
queue-thankyou=queue-thankyou
queue-callswaiting=queue-callswaiting
music=default
monitor-join=yes
monitor-format=
2005 Feb 15
1
Apropos sprintf behavior
If changes to sprintf behavior are being considered, would it
be possible to allow some of the other K&R conversion
specifiers?
xX - for integer to hex conversion, and
c - for ascii value to character conversion
would all be useful for me.
Thanks, Steve Dutky
On Mon, 14 Feb 2005 11:02:20 +0000 (GMT), Prof Brian Ripley
wrote:
+On Mon, 14 Feb 2005, Wolfgang Huber wrote:
+
+> Dear
2008 Jun 19
4
Controlling the length of line with abline(lm())
Hi
I just realized that when I use linear regression to draw a line through my
data points with something like the following:
abline(lm(y ~ x))
the length of the line is infinite, i.e., the line goes beyond the smallest
and the largest data values. This seems not very right to me (not to mention
it looks unaesthetic). I do not mean to imply that the straight-line
behavior of my system is
2005 Apr 21
1
R 2.1.0 for Windows installation error? atanh not in R.dll?
Could someone please tell me what I did wrong to create this message or what I should do to correct this problem?
I downloaded 2.1.0 Windows binary and installed into C:/R/rw2010, using the installer. I ran md5check.exe in C:/R/rw2010/bin/ and got "No errors."
The problem is this:
When I start up Rgui.exe from its shortcut (target= C:\R\rw2010\bin\Rgui.exe --save -sdi, Start in
2008 Jun 09
1
Bug/Error in formatC? (Was: Why doesn't formatC( x, digits=2, format= "g")...)
Hi all
After posting what follows, Duncan Murdoch suggested perhaps a bug
in formatC, or an error on documentation. Any comments?
In particular, bug, error or not, any ideas about how I can
consistently get two significant figures to print?
P.
---------- Original Message ----------
Hi all
I am not a C programmer, but I am trying to understand formatC to
get consistent printing of
2000 Jan 04
0
formatC (bug and fix) (PR#394)
OK:
> formatC(as.double(c(1,0,NA)))
[1] "1" "0" "NA"
NOT OK:
> formatC(as.integer(c(1,0,NA)))
[1] "0" "1072693248" "NA"
> formatC(as.integer(c(0,1,NA)))
[1] "0" "0" "NA"
BUG TRACED TO R-code of formatC()
where
x[!Ok] <- 0
unintendedly changes the storage.mode of x to
2001 Oct 26
1
Bug or new concept in formatC?
As a sequel to my previous mail on cut, formatC does not produce
what I have been taught is significant digits:
> x <- c(1.0793,1.0796, 11.0954, 11.0736 )
> formatC(x,digits=3,format="g")
[1] "1.08" "1.08" "11.1" "11.1"
(3,3,3,3) significant digits OK
> formatC(x,digits=3,format="f")
[1] "1.079"
2009 Jan 27
1
small bug in base::formatC (PR#13474)
Full_Name: Bernd Bischl
Version: 2.8.1
OS: Windows XP Professional
Submission from: (NULL) (129.217.207.95)
Hi,
there seems to be a small bug in formatC:
formatC("foo", format="s", mode="charcacter")
Error in formatC("foo", format = "s", mode = "charcacter") :
'mode' must be "double" ("real") or
2002 Mar 13
1
Commas in formatC
formatC() is great for formatting numbers! But it would be even better if it
could optionally insert commas (or semicolons), e.g.
R> formatC(1234567.89, digits=2, format="f", commas=T)
[1] "1,234,567.89"
Here's a snippet of code that does that, which could more or less just be
inserted into at the end of formatC if any R-core guru were so inclined. "r"
2019 May 30
1
Possible bug in formatC
I do not know if this is a bug or a case of improper documentation. The
documentation for formatC() implies that the difference between the options
format="f" and format="g" is that with "g", scientific format is sometimes
used. There is another difference between them that is not mentioned in the
documentation. drop0trailing=FALSE is ignored when format is set to
1999 Feb 28
0
Formatting in formatC and format (PR#129)
[This turned into a bug report which will go to r-devel, so I have taken it
off r-help.]
Bugs reported here:
(1) formatC's help page need some clarification.
(2) formatC needs to treat modes "double" and "real" as equivalent.
(3) format's help page or (preferably) format needs correction re the
meaning of `digits'
On Sun, 28 Feb 1999, Martin Maechler wrote:
2007 May 25
0
documented/undocumented behavior of as.double(formatC(x, digits=17))
Some days ago, there was a discussion about the command
formatC(exp(1),digits=100,width=-1)
Converting a double value to a string, from which the double may be
reconstructed exactly, may be useful. So, I did some experimentation
with it in my linux installation of R-2.5.0.
I generated a vector x of a large number of random doubles (random sign,
random mantissa with 53 significant bits and
2008 Jun 06
2
Why doesn't formatC( x, digits=2, format="g") doesn't always give 2 sig figs?
Hi all
I am not a C programmer, but I am trying to understand formatC to
get consistent printing of reals to a given number of significant
digits.
Can someone please explain this to me? These first three give what
I expect on reading ?formatC:
> formatC(0.0059999, digits=2,format="fg",flag="#")
[1] "0.0060"
> formatC(0.59999,
2012 Feb 23
3
I'm sure I'm missing something with formatC() or sprintf()
I have a four-digit string I want to convert to five digits. Take the
following frame:
zip
2108
60321
60321
22030
91910
I need row 1 to read '02108'. This forum directed me to formatC previously
(thanks!) That usually works but, for some reason, it's not in this
instance. Neither of the syntaxes below change '2108' to '02108.' The values
in cand_receipts[,1] are of
2000 Jan 12
0
inconsistencies between formatC(), format() and format.char()
Dear R-Developers,
Just a note: there are some inconsistencies between formatC(), format() and
format.char() and cross calling between these functions.
On the one hand
> cat(format('{"}'), "\n")
{\"}
> cat(format.char('{"}'), "\n")
{\"}
is by default format.char(, flag="-") and thus by default calling format()
>
2002 Nov 16
0
formatC with format="fg" displays number in exponential notation (PR#2299)
Full_Name: Frederic Schutz
Version: 1.6.1
OS: Linux
Submission from: (NULL) (128.250.252.193)
The result of the following commands:
> formatC(9.9, 1, format="fg")
[1] "1e+01"
> formatC(99.9, 1, format="fg")
[1] "1e+02"
does not seem to be coherent with what the help page says:
> format: equal to `"d"' (for integers),
2018 Oct 25
1
small bug in formatC?
formatC(0.0001, digits = 3, format = "f", zero.print="< 0.01")
Error in strrep(" ", nc - i1) : invalid 'times' value
The problem, if it is one, is in .format.zeros:
.format.zeros("0.000", "xxxxxx")
Error in strrep(" ", nc - i1) : invalid 'times' value
R version 3.5.1.
David
[[alternative HTML version deleted]]
2006 Jan 23
1
formatC slow? (or how can I make this function faster?
I'm trying to convert a matrix of capture occasions to format that an
external program can read. The job is to basically take a row of
matrix, like
> smp[1,]
[1] 1 1 0 1 1 1 0 0 0 0
and convert it to the equivalent string "1101110000"
I'm having problems doing this in a speedy way. The simplest solution
(calc_history below, using apply, paste and collapse) takes about 2