Displaying 20 results from an estimated 11000 matches similar to: "How to set up an object to share data across diverse functions"
2012 Apr 28
2
Character string to R object
I've been creating some R tools that manipulate objective functions for optimization. In
so doing, I create a character string with R code, and then want to have it in my
workspace. Currently -- and this works fine -- I write the code out, then use source() to
bring it in again. Example:
cstr<-"jack<-function(x){\n cat(\"Silly x:\")\n print(x) \n }\n"
write(cstr,
2010 Nov 16
4
DBLEPR?
Ravi Varadhan and I have been looking at UCMINF to try to identify why it gives occasional
(but not reproducible) errors, seemingly on Windows only. There is some suspicion that its
use of DBLEPR for finessing the Fortran WRITE() statements may be to blame. While I can
find DBLEPR in Venables and Ripley, it doesn't get much mention after about 2000 in the
archives, though it is in the R FAQ
2010 Nov 16
4
DBLEPR?
Ravi Varadhan and I have been looking at UCMINF to try to identify why it gives occasional
(but not reproducible) errors, seemingly on Windows only. There is some suspicion that its
use of DBLEPR for finessing the Fortran WRITE() statements may be to blame. While I can
find DBLEPR in Venables and Ripley, it doesn't get much mention after about 2000 in the
archives, though it is in the R FAQ
2015 Apr 25
2
Title case in DESCRIPTION for package where a word is a function namei
> On 25 Apr 2015, at 13:11 , Prof J C Nash (U30A) <nashjc at uottawa.ca> wrote:
>
> Hendrik pointed out it was the parentheses that gave the complaint.
> Single quotes and no parentheses seem to satisfy R CMD check. Perhaps
> that needs to be in the WRE.
Well, it is in ?toTitleCase:
...However, unknown
technical terms will be capitalized unless they are single
2015 Apr 25
0
Title case in DESCRIPTION for package where a word is a function namei
How about allowing underscore? (I believe WRE is silent on this, and I
have not tried submitting a package with underscore in the title.) As I
pointed out in my OP, _optim()_ works. And we have the advantage that we
can distinguish package from function.
The purpose of consistent editing is surely to provide the affordances
that save us from needing extra documentation, as per Donald Norman's
2012 Apr 05
4
Appropriate method for sharing data across functions
In trying to streamline various optimization functions, I would like to have a scratch pad
of working data that is shared across a number of functions. These can be called from
different levels within some wrapper functions for maximum likelihood and other such
computations. I'm sure there are other applications that could benefit from this.
Below are two approaches. One uses the <<-
2010 Nov 30
5
Minor warning about seq
I spent more time than I should have debugging a script because I wanted
x<-seq(0,100)*0.1
but typed
x<-seq(O:100)*0.1
seq(0:100) yields 1 to 101,
Clearly my own brain to fingers fumble, but possibly one others may want to avoid it.
JN
2015 Apr 24
2
Title case in DESCRIPTION for package where a word is a function name
I was preparing a fix for a minor glitch in my optimx package and R CMD
check gave an error that the title was not in title case. It is
A Replacement and Extension of the optim() Function
R CMD check suggests the incorrect form
A Replacement and Extension of the Optim() Function
'Writing R Extensions' suggests single quotes, i.e.,
A Replacement and Extension of the 'optim()'
2009 Oct 22
2
Advice on how to arrange fix of buglet
Recently I reported a small bug in optim's SANN method failing to report
that it had exceeded the maximum function evaluation limit in the
convergence code. This is a small enough matter that I was reluctant to
create a full-blown bug report. Indeed in the optimx package Ravi
Varadhan and I have been developing on r-forge (under the OptimizeR
project) it was a minimal work around to fix
2012 Mar 01
3
Converting a string vector with names to a numeric vector with names
Not paying close attention to detail, I entered the equivalent of
pstr<-c("b1=200", "b2=50", "b3=0.3")
when what I wanted was
pnum<-c(b1=200, b2=50, b3=0.3)
There was a list thread in 2010 that shows how to deal with un-named vectors, but the same
lapply solution doesn't seem to work here i.e.,
pnum<-lapply(pstr, as.numeric)
or similar vapply
2015 Apr 24
3
Title case in DESCRIPTION for package where a word is a function name
On 24.04.2015 22:44, Ben Bolker wrote:
> Prof J C Nash (U30A <nashjc <at> uottawa.ca> writes:
>
>>
>> I was preparing a fix for a minor glitch in my optimx package and R CMD
>> check gave an error that the title was not in title case.
>
> [snip] to make Gmane happy ...
>
>> I have found
>>
>> A Replacement and Extension of the
2009 Jul 30
3
R User Group listings
There are now several R geographic user groups, and a few have mailing
lists on the R mailing list system. Thanks to Martin M, there's also a
pointer to a page I'm maintaining to list/describe the groups. The page
is at
http://macnash.telfer.uottawa.ca/RUG.html
Contact me if you have a listing. I'm prepared to wikify it if there is
sufficient interest.
John Nash
2009 May 01
1
nlminb - Port library codes
Having looked at documentation and codes, I'm still looking to find out
who did the installation of the Port libraries. As I work on
optimization code improvements, there are often choices of settings
(tolerances etc.), and I'd prefer to learn if there are particular
reasons for choices before diving in and making any adjustments.
It is also worth giving credit where it is due. Given
2011 Feb 22
1
odfWeave graphics glitch
Using R2.12.1 on Ubuntu 10.04.1 I've tried to run the following code chunk in odfWeave
<<fig1, echo=TRUE,fig=TRUE,width=7,height=4>>=
x<-seq(1:100)/10
y<-sin(cos(x/pi))
imageDefs <- getImageDefs()
imageDefs$dispWidth <- 4.5
imageDefs$dispHeight<- 4.5
setImageDefs(imageDefs)
X11(type="cairo")
plot(x,y)
title(main="sin(cos(x/pi))")
2014 Jun 02
1
R CMD check for the R code from vignettes -- thread fraying?
I noted Duncan's comment that an answer had been provided, and went to
the archives to find his earlier comment, which I am fairly sure I saw a
day or two ago. However, neither May nor June archives show Duncan in
the thread except for the msg below (edited for space). Possibly tech
failures are causing misunderstandings.
JN
On 14-06-02 06:00 AM, r-devel-request at r-project.org wrote:
>
2009 Jan 04
1
R/octave/matlab etc.
I'd echo a lot of what has been said about this by the folk who have
been making R work so well. One of the main difficulties is that the
environment of computations affects relative performance. e.g., what
settings did a distro package builder choose. I note that my 3 GHz Dual
Core machine running Ubuntu 8.04 gets
octave 3.0.0
octave:6> tic; a = a + 1; toc
Elapsed time is 0.120027
2009 Sep 14
2
Escaping . in regular expression
If I run
cvec<-c("test.f", "test.sf", "try.g","try.res", "try.f")
print(cvec)
indx<-grep('\.f',cvec,perl=TRUE)
fset<-cvec[indx]
print(fset)
I get
> cvec<-c("test.f", "test.sf", "try.g","try.res", "try.f")
> print(cvec)
[1] "test.f" "test.sf"
2011 Jun 26
1
Default values in control list of function
In building a function for a package, I'd like to set the defaults in a control list,
e.g.,
makeg<-function(parameters, eps = 1.0e-7, control=list(showwork=TRUE, rubbish=1.0e+101)){
etc.
}
This does not provide showwork or rubbish within the function if control() is not fully
specified. Copying others, I've previously set the control defaults within the function
then matched
2015 Apr 25
0
Title case in DESCRIPTION for package where a word is a function name
Hendrik pointed out it was the parentheses that gave the complaint.
Single quotes and no parentheses seem to satisfy R CMD check. Perhaps
that needs to be in the WRE.
However, I have for some time used the parentheses to distinguish
functions from packages. optim() is a function, optimx a package.
Is this something CRAN should be thinking about? I would argue greater
benefit to users than title
2009 Jan 03
1
runif (and other generator) "precision" / man pages
I'm inclined to agree with the view that the "precision" of a generator
should be highlighted better in the manual pages. When I do
?runif
I don't see a mention, but ?.Random.seed DOES give the info, as Duncan
points out, and it is suggested to look there.
A 1-liner with each random number generator
"CAUTION: random number generators use different mechanisms and