I observed the following:
match.arg("white", colors())
yields 'white', but
match.arg("whit", colors())
yields:
`Error in match.arg("whit", colors()) :
'arg' should be one of "white", "aliceblue", '...
this message actually comes from `pmatch'. using a suitable subset of
`colors()' works
> Message: 6
> Date: Fri, 09 Oct 2009 10:35:51 -0600
> From: Tony Plate
> Subject: Re: [Rd] weigths in nls (PR#13991)
> To: stephen.b...@cibc.com
> Cc: r-b...@r-project.org, r-de...@stat.math.ethz.ch
> Message-ID: <4acf6667.4060...@acm.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=fl
On Thu, Jun 05, 2008 at 08:57:58AM -0400, Simon Urbanek wrote:
>
> On Jun 5, 2008, at 7:41 AM, Joerg van den Hoff wrote:
>
> >I tripped over the following problem:
> >
> >due to (my?) unresolved problems with cairo graphics under
> >MacOS (graphic window block
I tripped over the following problem:
due to (my?) unresolved problems with cairo graphics under
MacOS (graphic window blocks unrecoverably) I modified my
`.Rprofile' to issue `X11(type = "Xlib")` on each R
startup (as a workaround to automatic opening of a `cairo'
device when issu
On Thu, May 01, 2008 at 02:23:13PM +0100, Barry Rowlingson wrote:
> Joerg van den Hoff wrote:
>
> >X11(antialias="none")
> >
> >I obviously am going to plot to the screen device. where
> >a line width below one pixel does'nt make sense to me.
>
On Thu, May 01, 2008 at 01:00:24PM +0100, Prof Brian Ripley wrote:
> On Thu, 1 May 2008, Joerg van den Hoff wrote:
>
> >
> >using
> >
> >X11(antialias="none")
> >plot(1:10)
> >
> >produces an incomplete plot with 2.7.0. under
> >M
using
X11(antialias="none")
plot(1:10)
produces an incomplete plot with 2.7.0. under
MacOS 10.4.11: both y-axes are missing.the
y-ticks (except the tick at `2' wich is missing)
including labels are there.
this happens with a 1280x854 labtop monitor.
is this known behaviour/a cairo bug?
joer
2 days ago I asked this on r-help, but no luck... since
this is actually a programming question, I post it here
again:
my question concerns the use of `eval' in defining the model
formula for `nls' when performing weighted fits. (I use
version 2.6.2., but according to NEWS there we
I received the following message when installing
a private package:
** preparing package for lazy loading
Loading required package: roiutils
Loading required package: fzrutils
Loading required package: pkc
** help
>>> Building/Updating help pages for package 'psflib'
Formats: text html latex examp
dear list,
I stumbled over the follwing strange behaviour/error when
using `nls' which I'm tempted (despite the implied "dangers")
to call a bug:
I've written a driver for `nls' which allows specifying the
model and the data vectors using arbitrary symbols.
these are internally mapped to consiste
dear list members,
my question concerns computation of confidence intervals in nonlinear
fits with `nls' when weigthing the fit. the seemingly correct procedure
does not work as (I) expected. I'm posting this here since: (A) the
problem might suggest a modification to the `m' component in the retu
I tried two times to get some help for this from the help list but to no avail.
I hope,
it's OK to post this here (once...). if not, please ignore (the rest of) this
mail:
for one of my private packages R CMD CHECK {package} givves me annoying warnings
due to 'missing links' in the manpages for
I raised this question quite some time ago but it quitly went down the
river. I'll give it a second try (before keeping my modified version of
matplot for ever...):
matplot supports vectors (and/or character strings) for a number of
arguments namely `type', `lty', `lwd', `pch', `col', `cex'. al
Hi,
I am writing this email, because I am not sure if the issue I have
discovered is a bug or not.
For a few days I have been fiddling around with a small program that
calculates the reflectance of multilayer dielectric mirrors (eg. bragg
mirrors). It does not really matter what I did, what ma
before getting scolded for submitting a (non-)bug report:
when using the 'symbols' function for plotting boxplot data (i.e. using
'boxplots' symbols), I noted that the x/y-position of the symbols is
associated with the center of the box.
while this is obviously natural for a usual plotting symbol
in my view it's not always good to get this answer, but your "problem"
is not too deeply hidden in the manpages, so simply read the
documentation of read.table:
?read.table
(and look out for the "check.names" flag)
regards,
joerg
__
R-devel@r-proje
hi everybody,
which each release I hope that the section
"weights: an optional numeric vector of (fixed) weights. When present,
the objective function is weighted least squares. _not yet
implemented_"
in the help page of 'nls' is missing the last sentence.
are their any p
17 matches
Mail list logo
