Hi John,
It's possible that I didn’t follow what you did, but it appears as if you call
globalVariables() *inside* the function. Instead try to do as Richard Heiberger
suggested and place the call outside of the function, e.g., in a source file in
the package R directory named globals.R. (Of
Unfortunately, makes things much worse. I'd tried something like this already.
> * checking examples ... ERROR
> Running examples in ‘rootoned-Ex.R’ failed
> The error most likely occurred in:
>
>> ### Name: rootwrap
>> ### Title: zeroin: Find a single root of a function of one variable within
Does this solve the problem?
if (getRversion() >= '2.15.1')
globalVariables(c('envroot'))
I keep this in file R/globals.R
I learned of this from John Fox's use in Rcmdr.
On Mon, Aug 27, 2018 at 8:28 PM, J C Nash wrote:
> In order to track progress of a variety of rootfinding or optimization
In order to track progress of a variety of rootfinding or optimization
routines that don't report some information I want, I'm using the
following setup (this one for rootfinding).
TraceSetup <- function(ifn=0, igr=0, ftrace=FALSE, fn=NA, gr=NA){
# JN: Define globals here
groot<-list(ifn=ifn,
Yay! I got it to work! I used the ~/.R/Makevars, and all is well.
Thanks again,
Erin
Erin Hodgess, PhD
mailto: erinm.hodg...@gmail.com
On Mon, Aug 27, 2018 at 2:29 PM Kevin Ushey wrote:
> Hi Erin,
>
> The R extensions manual should be helpful here -- in particular, see the
> sections on
Thank you, Kevin!
I put together the Makevars file:
PKG_LIBS = $(LAPACK_LIBS) $(BLAS_LIBS)
FC=c:/progra~1/PGICE/win64/18.4/bin/pgf90
SAFE_FFLAGS="-Lc:/progra~1/PGICE/win64/18.4/lib/pgf90.dll
-Lc:/progra~1/PGICE/win64/18.4/lib/pgc14.dll"
rmpiFort.obj: rmpiFort.f90
$(FC) $(SAFE_FFLAGS)
Hi Erin,
The R extensions manual should be helpful here -- in particular, see the
sections on the 'src/Makevars' file and configuration of the Fortran
compiler:
https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Using-Makevars
In particular, in your 'src/Makevars' file, you'll likely
Hello!
I'm building a package on Windows 10 which uses the PGI Fortran compiler.
I have a Makefile set up in the src directory, and when I run "make all",
the subroutines compile beautifully.
Now I want to create my package. When I run R CMD check, naturally,
gfortran is called. Is there a
I still do not undertsand why you cannot stop scala and related
connections at the end of each example. You can insert a comment that
this is not needed if you have follow up tasks for scala.
Best,
Uwe
On 27.08.2018 07:14, David B. Dahl wrote:
Henrik,
Thanks for the suggest. Yes,
