Hello,
This sounds like a problem you should discuss with/report to the
maintainer of the particular package you are using, and you can get
their email address from the DESCRIPTION file.
Cheers,
Max
On 2017-11-10 07:23 AM, Cho, In-Ho [CCE E] wrote:
Dear R developers:
My group are facing
Hi Younathan,
You can ignore the first note: it simply says that this is a new package.
The second note highlights a few possible problems with your DESCRIPTION
file. It flags the word "Plasmode" as being possibly misspelled; if it
isn't, you can ignore the comment. Then it points out that the
Hi Phil,
As you said yourself, if you can't reproduce the message locally, it
will be difficult to fix. But maybe the following will help: I looked at
your Github repository, Tand it seems the only changes that were made to
your files in the man/ directory since your successful release of
mir
Hi Larisa,
This has been covered before; see
https://mailman.stat.ethz.ch/pipermail/r-devel/2014-March/068497.html
Essentially, it is reminder to check that this information is correct.
As such, you can ignore it if it is indeed correct.
Max
On 2017-04-28 09:15 AM, LARISA ZAMORA MATAMOROS
Hi Ege,
For writing to standard output/error, you can use Rcout or Rcerr
(defined by Rcpp; they even have a vignette showing how to use it in the
Rcpp gallery). Alternatively, if you're using C code, you can replace
printf by Rprintf (this is explained in Writing R extensions, section 6.5).
Hi Vineetha,
The key part of Writing R extensions is section 1.2.3., especially the
following sentence: "Packages making use of Fortran 90/95 features
should use file extension.f90or.f95for the source files".
Incidentally, your question has already been asked on this mailing list:
https://stat
Hi Bill,
This is just a hypothesis, but it could have something to do with the
fact that you're using parallel::mclapply inside your function pk.nca?
This would certainly explain why you have different behaviours on
Windows and Unix systems. It would also explain why you get a different
behav
