Displaying 20 results from an estimated 4000 matches similar to: "relist.Rd patch"
2009 Jan 19
0
optim() example in relist() help page
I think the optim() example in the Details section of relist()'s help
page is not totally correct. In particular, in the current form it is
not taken into account that vcov should be a symmetric matrix and only
the parameters in the lower (or upper) triangular part should be optimized.
A possible fix is:
ipar <- list(mean = c(0, 1), vcov = c(1, 1, 0))
initial.param <-
2007 May 13
2
relist, an inverse operator to unlist
Hi all,
I wrote a function called relist, which is an inverse to the existing
unlist function:
http://www.econ.upenn.edu/~clausen/computing/relist.R
Some functions need many parameters, which are most easily represented in
complex structures. Unfortunately, many mathematical functions in R,
including optim, nlm, and grad can only operate on functions whose domain is
a vector. R has a
2008 Aug 17
2
Optim stripping attributes from relistable objects
Dear all,
The following code is inspired by the help file for the relist()
function (see?relist), which explicitly details how you can use a
relistable object in conjunction with optim to pass and reconstruct
complex parameter structures/groupings. The idea is that the optim()
function can only work with vectors, but in many cases you would like
to use a complex structure inside the objective
2011 Apr 14
1
Possible bug in 'relist()' and/or 'as.relistable()'
Dear list,
I think I just stumbled across a bug in either 'relist()' and/or
'as.relistable()'. It seems that 'pairlists' can only be un- and relisted as
long as they're not nested:
Good:
a <- as.relistable(as.pairlist(list(a=1, b=2)))
a <- unlist(a)
relist(a)# Works
Bad:
a <- as.relistable(as.pairlist(list(a=1, b=2, c=list(c.1=1, c.2=2))))
a <- unlist(a)
2013 Jun 07
1
relist() is broken when the skeleton is a list with empty list elements
Hi,
relist() is broken when the skeleton is a list with empty list elements:
> x <- list(1:3, integer(0), 11:14)
> relist(unlist(x), x)
[[1]]
[1] 1 2 3
[[2]]
[1] 11 3
[[3]]
[1] 11 12 13 14
Hard to believe that such a bug has been around for 6 years (i.e. since
the introduction of relist()) without ever being noticed.
Cheers,
H.
> sessionInfo()
R
2004 Mar 10
1
Rd - \preformatted, \section and LaTeX problem
Hi,
I have found an unwanted feature in the Rd to LaTeX convertion
regarding \preformatted inside a \section. I have created an Rd
example below, which generates an error in the following 'R CMD check'
step
* creating aroma.affine-manual.tex ... OK
* checking aroma.affine-manual.tex ... ERROR
LaTeX errors when creating DVI version.
This typically indicates Rd problems.
I believe
2011 Nov 25
1
Problem with & question about \preformatted in .Rd
Hi,
The "\preformatted" environment in Rd files doesn't seem to escape
long sequences of backslashes properly when converted to pdf (LaTeX)
documentation. I'm running R version 2.14 (from subversion, revision
57751) on Linux (RHEL). Here's an example from the command line:
echo
2009 Oct 01
2
Rd.sty question: LaTeX expert needed
The Rd.sty LaTeX package is used when building the R manuals, and by the
LaTeX pages produced from the man pages.
I have tracked down some problems G?bor Cs?rdi was having recently (see
"Re: [R] preformatted and '#' in manual pages" in R-help) to a LaTeX
problem, and am trying to work out how to fix it.
Specifically, the .Rd file he was using had a structure like
\dQuote{
2008 Nov 06
2
Two minor escaping issues using \preformatted{....} in Rd format
Hi r-devels,
I have two minor problems with special characters in Rd files when
used within a \preformatted{} markup command:
------------------------------------------------------
1. issue: backslash + single brace
------------------------------------------------------
I would like to write "\\\}" to produce \} on output (documenting
the need to escape the brace once again before
2007 Aug 30
1
suggesting \alias* for Rd files (in particular for S4 method documentation)
Hi,
I do not know if everybody finds index pages of the html-formatted R
help useful, but I know I am at least not the only one who uses them
extensively to get the overview of functions and methods in a package
(even for my own package). Problems arise, however, if a lot of S4
methods need to be documented blowing out the index with (generally
irrelevant) entries like:
2000 Apr 28
0
mvdnorm???
Hello:
There is a function in the MASS library called mvrnorm(), and I wonder
whether R has a corresponding function mvdnorm? I don't think it would be
that tough to write, but has anyone done it yet? Thanks in advance.
Tom Richards
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-help mailing list -- Read
2006 Jan 14
0
RE Addition to the list of supported UPS
Hi Peter,
I've fwded your info to the list, as other people might be interested in.
I've also logged a patch tracker so that you can follow its inclusion:
https://alioth.debian.org/tracker/index.php?func=detail&aid=302882&group_id=30602&atid=411544
As a side note, there is a work underway to merge the similar driver
(mustek, powermust, ...)
into one named megatec. This one
2003 Nov 17
1
\preformatted and $
Hi,
I have been developing a package in R and have been working on
documentation. I have a \details function that contains the following:
\details{
some text
\preformatted{
[my-section]
user = apv
host = 127.0.0.1
}
}
When I run R CMD check I get an error while checking the manual. If I
remove:
\preformatted{
[my-section]
user = apv
host = 127.0.0.1
}
and replace it with
[my-section]
2010 Mar 16
0
FW: How to parse a string (by a "new" markup) with R ?
A version using regular expressions, regexpr() and substr() functions is attached.
Finally everything is packed into splitSeq() function (chunk 14 in the attached file)
Seq<- "GCCTCGATAGCTCAGTTGGGAGAGCGTACGACTGAAGATCGTAAGGtCACCAGTTCGATCCTGGTTCGGGGCA"
Str<-
2009 Nov 13
1
Trailing spaces in POD files
IMHO trailing spaces should be permitted in POD files. Currently
they are prevented by the git upload hook.
The reason to allow them in POD files is because indentation is
used to indicate blocks of preformatted text (the equivalent of
<pre> in HTML). To keep code together in the output if it
contains blank lines you have to add a line containing a single
space.
For an example of where
2011 May 18
1
strucchange package Linux help
When I run the code below on Macintosh and Windows, the plot comes out
fine. However, on Linux, the png generated is invalid from R console,
and loading strucchange crashes rkward. Is this a known issue on Linux
and, if so, is there a workaround? Many thanks!
require(strucchange)
data("RealInt")
bp.ri <- breakpoints(RealInt~1, h=15)
summary(bp.ri)
fac.ri <- breakfactor(bp.ri,
2017 Nov 07
0
New vcov(*, complete=TRUE) etc -- coef(<lm>) vs coef(<aov>)
Dear Martin,
I think that your plan makes sense. It's too bad that aov() behaved differently in this respect from lm(), and thus created more work, but it's not be a bad thing that the difference is now explicit and documented.
I expect that that other problems like this will surface, particularly with contributed packages (and I know that you're aware that this has already happened
2009 Nov 24
0
can't use function vcov with a GAMLSS object??
Hi everyone,
I''m trying to use function vcov to extract the covariance matrix from a
GAMLSS object. But I''m getting some strange errors and I was hoping someone
could help me out? Vcov works with the same model for lm and glm objects,
but not gamlss objects. I''ve searched various help sites to no avail.
Its very possible the reason is that vcov failed though,
2009 Aug 11
1
Awkward escaping with five backslashes within \code{ } in new parse_Rd
Hi R-devels,
I noticed that you are working quite actively on the new Rd-parser
and have made it the default renderer in R-2.10.0dev. So I would
like to come back on an issue I have already raised on this list
last November
("Two minor escaping issues using \preformatted{....} in Rd format")
My setting has slightly changed as \preformatted, AFAICS is not
supported within \describe
2017 Sep 14
0
vcov and survival
Dear Terry,
It's not surprising that different modeling functions behave differently in this respect because there's no articulated standard.
Please see my response to Martin for my take on the singular.ok argument. For a highly sophisticated user like you, singular.ok=TRUE isn't problematic -- you're not going to fail to notice an NA in the coefficient vector -- but I've