Dear Bioconductor developers,
In the CAGEr package, I created a "CAGEexp" class that extends
"MultiAssayExperiment" without adding new slots, in order to define generic
functions that require CAGEr-specific contents in the colData slot.
Unfortunately, when run in the development branch of
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)
Ok, Thank you very much.
Best,
Ti Tai
引述 "Shepherd, Lori" :
Your package does look clean for BiocInstaller/biocLite - looking
at the dependency I think this is coming from when your package is
Installed and from the dependency gage that has not been updated
yet. I think you can
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
Hi,
I just found based on user reports that the old version of my package
Logolas for R 3.4 and Bioc 3.6 is broken. It does install fine but the main
function does not run. Everything seems to be fine however for R 3.5 and
Bioc 3.7. I would like to produce either an error message if someone < R
Dear Arun,
thank you for checking the workaround scripts.
I've modified detectCores() to use GetLogicalProcessorInformationEx. It
is in revision 75198 of R-devel, could you please test it on your
machines? For a binary, you can wait until the R-devel snapshot build
gets to at least this svn
Hi Nitesh,
After looking more closely, I went with option 1 that you clearly
outlined below. The cherry picked version of the history is now the
origin/master one at
https://github.com/jtleek/sva-devel/commits/master. From
http://bioconductor.org/developers/how-to/git/resolve-duplicate-commits/
Rich Calaway pointed out that S4 came out c. 1996-97, not 1991.
Bill Dunlap
TIBCO Software
wdunlap tibco.com
On Sun, Aug 26, 2018 at 8:30 PM, William Dunlap wrote:
> > the lack of a decimal place had historically not been significant
>
> Version 4 of S (c. 1991) and versions of S+ based on it
Thank you Nitesh!
I'll talk to Jeff and Claire.
Best,
Leo
On Sat, Aug 25, 2018 at 2:00 AM Turaga, Nitesh
wrote:
>
> Hi Leo,
>
> I’ll try to help you with this issue.
>
> The duplicates commit you have on your package “sva” come from the pre-git
> era of Bioconductor. There are three ways we
Your package does look clean for BiocInstaller/biocLite - looking at the
dependency I think this is coming from when your package is Installed and from
the dependency gage that has not been updated yet. I think you can safely
ignore this warning and when gage is updated it should
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,
Dear Tomas, Inaki and the rest of R-devel team,
thank you for your explainations and suggestions. I talked with gEcon
development team and we decided to change our implementation along the
lines you suggested.
Best regards,
Karol Podemski
pt., 17 sie 2018 o 13:38 Tomas Kalibera
napisał(a):
>
most likely L comes from Michel or Obelisk.
http://img.izing.ml/MARSHALL.html = why you are making Mars colonization
(and space) "just a game"
http://img.izing.ml/IT.html = why i could care less.
ᐧ
On Sun, Aug 26, 2018 at 11:30 PM, William Dunlap via R-devel <
r-devel@r-project.org> wrote:
> >
Hi,
It's anamiR.
Best,
Ti Tai Wang
引述 "Shepherd, Lori" :
What is the name of your package?
It is possible it could be coming from one of the packages you
depend or import. If you are sure you replaced all the instances in
your package this could be the case.
Lori Shepherd
20 matches
Mail list logo
