Tue, Jul 16, 2024 at 2:19 AM
Subject: Re: CRAN Submission rkriging 1.0.1
To: Bill Huang <10billhuan...@gmail.com>
Please ask on the mailing list
Best,
Uwe Ligges
On 16.07.2024 08:32, Bill Huang wrote:
> Hi, Uwe.
>
> Thanks for the message! I am not sure how to resolve this issu
s of the GitHub repo are:
https://github.com/billdenney/TopicLongTableR/blob/main/R/topic_long_table_h
eader_footer.R
https://github.com/billdenney/TopicLongTableR/blob/main/man/topic_long_table
_header.Rd
https://github.com/billdenney/TopicLongTableR/actions/runs/5771551599/job/15
645624146#s
I see the problem when I compile the C++ code on Ubuntu 20.04 and the
latest R-devel with
C++ compiler: ‘g++ (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
If I change all the unadorned 'abs' calls in src/nn_matchC_vec.cpp with the
prefix 'std::' the problem goes away.
-Bill
On Thu
some minimal sanitization of the
input, but then we will also ensure that we do anything in a container with
limits applied from the outside, too.
Thanks,
Bill
On Sun, Feb 26, 2023, 4:57 PM Simon Urbanek
wrote:
> Bill,
>
> the short answer is you can't limit anything at R level. A
from users to prevent
malicious behavior?
Thanks,
Bill
[[alternative HTML version deleted]]
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
rintf(string, length, "format ...");
-Bill
On Fri, Feb 3, 2023 at 8:28 AM Brad Eck wrote:
> Dear List -
>
> What’s the latest best practice on trying to reproduce warnings raised
> on CRAN checks?
>
> I updated my epanet2toolkit package earlier this week.
> R CMD che
Even Microsoft added snprintf to Visual C++ in 2015 (not that that matters
for R).
-Bill
On Sat, Jan 21, 2023 at 2:47 AM Duncan Murdoch
wrote:
> On 21/01/2023 5:33 a.m., Holger Hoefling wrote:
> > Hi,
> >
> > thanks for the tip! Is that available everywhere or do I nee
c"
> Sys.setlocale(locale="C")
[1] "C"
> tools::showNonASCIIfile('
https://raw.githubusercontent.com/JamesRamsay5/fda/master/NAMESPACE')
1: export(AmpPhasDecomp,
> rawToChar(readBin('
https://raw.githubusercontent.com/JamesRamsay5/fda/master/NAMESPACE
eval(call)
[That code is completely untested.]
-Bill
On Wed, Dec 14, 2022 at 3:19 PM David Kepplinger
wrote:
> Dear List,
>
> I am working on updating the pense package and refactored some of the
> methods. I have several functions which take the same arguments, hence I'm
&g
e name of the argument. The
format of the seed depends on the generator used - I think it used the
nature of the proffered seed to get the likely generator, but there may
have also been arguments to specify the generator explicitly.
I think this would be a nice thing to add to R's set.seed.
oding(qu)
[1] "UTF-8" "UTF-8" "UTF-8" "UTF-8"
> qx == qu
[1] TRUE TRUE TRUE TRUE
(charToRaw shows that qu and qx are not byte-for-byte identical: '=='
coerces the latin1 strings to utf-8.)
-Bill
On Tue, Jul 19, 2022 at 9:38 AM Spencer
tes
[Is there a more direct way to remove byte code from a function? Or to
inspect it?]
Building Matrix with --no-byte-compile reduces the size of R/Matrix.rdx by
more than half, from 2.7 MB to 1 MB.
-Bill
On Sat, Oct 30, 2021 at 12:00 AM Mosqueira Sanchez, Iago <
iago.mosque...@wur.nl&
Can you tell if the failure to download was due to a Solaris-specific issue
or due to the Solaris test machine not being fully connected to the
internet?
-Bill
On Fri, Sep 24, 2021 at 7:50 AM Roy Mendelssohn - NOAA Federal via
R-package-devel wrote:
> Hi All:
>
> I am getting dinged
o native encoding
unable to translate '' to native encoding
unable to translate '' to native encoding
unable to translate '' to native encoding
unable to translate '' to native encoding
unable to translate '' to native encoding
strncpy( s->data, p, n );
+ s->data[n] = '\0';
s->len = n;
}
I don't know why valgrind isn't working for you.
-Bill
On Mon, Aug 2, 2021 at 4:23 PM Georgi Boshnakov <
georgi.boshna...@manchester.ac.uk> wrote:
> Thanks for looking into thi
I ran the tests of rbibutils-2.2.2, using the latest devel version of R
configured to use valgrind, with
R --debugger=valgrind --debugger-args=--track-origins=yes --quiet -e
'testthat::test_package("rbibutils")'
I saw a lot of 'conditional jump depends on uninitialized value' errors:
==27280== C
I think the problem with RPostgreSQL/sec/RS-DBI.c comes from some changes
to Defn.h and Rinternals.h in RHOME/include that Luke made recently
(2021-07-20, svn 80647). Since then the line
#define s_object SEXPREC
in Rdefines.h causes problems. Should it now be 'struct SEXPREC'?
-Bil
tor >&)
-Bill
On Mon, Jul 5, 2021 at 11:01 AM Duncan Murdoch
wrote:
> On 05/07/2021 10:32 a.m., Ben Bolker wrote:
> >I'm running into trouble checking a new release of the 'broom.mixed'
> > package <https://cran.r-project.org/web/packages/broom.mixed/ind
solve_svd's second argument is 'tolerance', a small scalar value, not the
right hand side of X %*% beta == Y. It returns the [approximate] inverse
of X, not beta.
solve_svd(cor.x2,cor.y) should probably be solve_svd(cor.x2)%*%cor.y (or
just solve(cor.x2,cor.y)).
-Bill
On Fri, J
The offending line in path_coeff seems to be
betas[i, 2:nvar] <- t(solve_svd(cor.x2, cor.y))
where i is a single integer, nvar is 15, and the right hand side is a 14 by
14 matrix. What is this line trying to do? Did it ever give the correct
result?
-Bill
On Fri, Jun 4, 2021 at 7:39 AM B
lt;- -> [<-.data.frame -> matrix
Execution halted
In the current R-devel the matrix command matrix(value, nrow, ncol)
complains if length(value)>nrow*ncol, so you need to truncate 'value'.
(Previously matrix() would silently truncate value.)
-Bill
On Thu, Jun 3, 2021 at 5:57
cli does export col_red - did you omit the 'r' when calling it from your
package or vignette?
On Thu, Apr 29, 2021 at 9:29 AM Danielle Maeser wrote:
> Hi Duncan,
>
> I really appreciate your response. Unfortunately, I am still receiving the
> error below.
>
> If anyone has ideas, I'd appreciate
S=c("weights","subset","offset"))
usesNSE(FUN="~") # missing ARGUMENTS means all args are NSE
This information would be stored in the environment that contains FUN.
-Bill
On Sat, Apr 24, 2021 at 6:18 AM Martin Maechler
wrote:
> >>>>> Ben Bolker
Have you run the offending examples under valgrind on Linux with
gctorture(TRUE)?
-Bill
On Thu, Apr 1, 2021 at 11:51 AM Zhang, Wan wrote:
>
> Hello,
>
> In our package “BET” version 0.3.4 published on 2021-03-21, there is a
> “memory not mapped” error on Solaris 10.
&g
I haven't followed all the code branches in tools:::.check_packages(),
but some of them use --vanilla when running the R subprocess that does
the checking. I think that would mean that libraries in ~/R would not
be in the search path.
-BIll
On Mon, Mar 8, 2021 at 8:45 AM Thierry Onkelinx
id Fortran logicals out of
habit.
-Bill
On Thu, Feb 18, 2021 at 1:59 AM Paul Schmidt-Walter
wrote:
>
> Hi Bill,
>
> thanks a lot for your suggestion!
>
> I managed to use Gabors Docker image to reproduce the warning... I
> already found a solution, by turning LOGICAL to INTEGER in
I suspect your problem is that, at least with the recent gnu
compilers, the Fortran 'c_logical' maps to the C _Bool, not the C int.
-Bill
On Wed, Feb 17, 2021 at 11:38 AM Paul Schmidt-Walter
wrote:
>
> Dear Team,
>
> My package 'LWFBrook90R' (https://github.com/p
Try using their official names, Rf_ScalarReal, Rf_eval, Rf_install, etc.
You may have #defined R_NO_REMAP in code that you did not show us.
-Bill
On Tue, Jan 5, 2021 at 1:42 PM Oliver Madsen
wrote:
> This is maybe better suited for Rcpp-devel or another mailing list. If so,
> I apo
e, not meaning compiler optimization), so optimization is
preferable. But, it's a fair point that I don't know the value of the
different -O optimization levels for what is only long algebra.
Thanks,
Bill
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
ation completed successfully (though installation failed as
expected because the compiled .dll couldn't load on 32-bit R).
Thanks,
Bill
[[alternative HTML version deleted]]
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
.Rd file should be edited by hand,
> instead of auto-generated?
I don't think roxygen2 intentionally converts \u sequences, I think this is
just a consequence of the parse() + deparse() roundtrip:
x <- '"\\u03bc"'
charToRaw(x)
#> [1] 22 5c 75 30 33 62 63 22
y <-
5c7e63bbad
4194320e07/R/unicode_to_ascii.R#L28-L31
And the documentation is here:
https://github.com/billdenney/bsd.report/blob/454caf217c5b333af1d65c7e63bbad
4194320e07/man/unicode_to_ascii.Rd#L17-L24
Do you have any suggestions on how to make this code/documentation work with
Codoc?
Tha
xport is not desired.
Thanks,
Bill
-Original Message-
From: Duncan Murdoch
On 17/02/2020 10:05 a.m., b...@denney.ws wrote:
> Does anyone know why the S3 method for name class objects is not found
> when checking the package?
I think you need to register knit_print_helper_formula.nam
}[!tbp]
\begin{center}
\begin{tabular}{l}
\hline\hline
\multicolumn{1}{c}{}\tabularnewline
\hline
~\tabularnewline
a\tabularnewline
b\tabularnewline
\hline
\end{tabular}\end{center}
\end{table}
While I’m wanting an equation:
$$a = b$$
Thanks,
Bill
From: Richard M
master/R/knit_print.formula.R
#L60-L79):
knit_print_helper_formula <- function(x, ...) {
UseMethod("knit_print_helper_formula")
}
# Some other methods
knit_print_helper_formula.name <- function(x, ...) {
# Function body
}
Does anyone know why the S3 meth
path(Sys.getenv("HOME"),
"datapkg_cache")` if they have not set the option.
To me #3 sounds best, but I'd like to be sure that I'm not missing something.
Thanks,
Bill
-Original Message-
From: Uwe Ligges
Sent: Sunday, December 15, 2019 11:54 AM
To: b...@den
ally with the umbrella
package. I believe that it is considered poor form to write within the
library location for a package except during installation.
What is the best practice for caching the resulting large dataset which is
locally-generated?
Thanks,
Bill
[[alternative HTML ve
ppropriate \alias
>
> entries, and all their arguments documented.
>
> The \usage entries must correspond to syntactically valid R code.
>
> See chapter 'Writing R documentation files' in the 'Writing R
>
> Extensions' manual.
>
>
>
&
t;
>entries, and all their arguments documented.
>
>The \usage entries must correspond to syntactically valid R code.
>
>See chapter 'Writing R documentation files' in the 'Writing R
>
>Extensions' manual.
>
>
>
> I have t
Extensions' manual.
I have tried variants of escaping the parenthesis like "\(" and "\\(" and
the unescaped variant "(", too.
Thanks,
Bill
[1] In case the first thought is, "don't write formula which have a f
hub.com/billdenney/TopicLongTableR/blob/master/man/topic_long_tab
le_header.Rd#L9
That generated a similar issue but check showed "\..." (backslash then 3
dots) instead of what is shown in the 2 backslashes case when check showed
just "...".
So, while I agree that 4 backslashes would m
case when check showed just "...".
So, while I agree that 4 backslashes would make the most sense for the .Rd
file, there is still an issue somewhere with that 4 backslashes case.
Thanks,
Bill
-Original Message-
From: Duncan Murdoch
Sent: Saturday, August 24, 2019 8:37 A
last_page = NULL, subsequent_page_notification
= "continued \\ldots", verbatim = NULL)
Docs: function(x, bottom_border = "\hline", bottom_all_pages = NULL,
bottom_last_page = NULL, subsequent_page_notification
= "continued .
opying it into the .Rd with extra escaping for the backslashes
(well, roxygen2 is doing the extra escaping).
Rd text
--
topic_long_table_header(x, col_names = NULL,
above_col_names = "hline", below_col_names = "hline",
subsequent_page_notification = &q
subsequent_page_notification = "\... continued",
latex_header = NULL)
```
I'm not sure, but I think that the solution is to add more protection to the
\s when generating the roxygen or perhaps wrapping the arguments in some
form of verbatim block (
uot;To use the foo.bar function, please install package A.")
}
Thanks,
Bill
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
kages.
I'm going to implement that unless someone indicates something that I'm missing.
Thanks,
Bill
>
> I can ask to translate that into the current session language using
>
> gettext("NaNs produced", domain = "R")
>
> Figuring out the right
cific R error (about
coercion) without testing the formatting of the error text?
The only solution that immediately occurs to me is to wrap the coercion in a
tryCatch and give my own error. But, then were the R error translated, the
users of my package would lose the benefit of transla
directory and
run the vignette if the tests were installed.
Thanks,
Bill
-Original Message-
From: Joshua Ulrich [mailto:josh.m.ulr...@gmail.com]
Sent: Saturday, November 25, 2017 9:20 AM
To: Bill Denney
Cc: Dirk Eddelbuettel ; r-package-devel@r-project.org
Subject: Re: [R-pkg-devel
Hi Joshua and Dirk,
> On Nov 23, 2017, at 10:17, Dirk Eddelbuettel wrote:
>
>
> On 23 November 2017 at 08:07, Joshua Ulrich wrote:
> | On Wed, Nov 22, 2017 at 4:21 PM, Bill Denney wrote:
> | > When running R BUILD now (via Travis CI), I get an error that the build
>
stall, I can add --install-tests.
Is there a way to control R BUILD so that the installation includes test
installation?
Thanks,
Bill
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
dd it to their own
libraries (optionally).
Thanks,
Bill
> On Oct 6, 2017, at 13:13, David Hugh-Jones wrote:
>
> One question that comes to mind: what's the synergy? I e why are units and
> errors best handled together? I use standard errors a lot, but never
> units... I
b.loc", envir=environment(.libPaths),
c("/tmp/current", "/usr/local/lib/R/site-library",
"/usr/lib/R/site-library", "/usr/lib/R/library"))
Thanks,
Bill
P.S. Apologies if this would better fit on a
because no end user ever needs it?
If "Depends", then it leads to over-installation of the package by end
users who don't care about running tests locally. If "Suggests", then
all of the tests would fail (assuming that Dirk's suggestion is
implemented).
help!
Bill
On 7/20/2016 3:40 PM, Ben Bolker wrote:
Digging into the code (specifically by setting
options(warn=2,error=recover), I see that the warning is happening
during this call:
tmp.results <- parallel::mclapply(X = conc.dose, FUN =
pk.nca.intervals,
intervals = data$i
why would it behave differently when options(warn=1) is set rather
than the default of options(warn=0)?
Thanks,
Bill
On 7/20/2016 3:06 PM, François Michonneau wrote:
Hi Bill,
The problem is not with the warning() function but with your if()
test that triggers the warning. It probably has
Does anyone have an idea why warnings may behave differently on Windows
compared to non-Windows platforms? Is this a bug in R somewhere? (I've
not been able to make a simpler example that triggers the issue,
unfortunately.)
Thanks,
Bill
__
R-pa
57 matches
Mail list logo
