Hi Hani,
The command you showed works fine on my MacBook Pro. However I am on an Intel
Mac. I see that your R is (arm64), so there’s probably some issues trying to
attach across compatibility layers.
Does your debugging specifically require C level debugging, and also M1 Macs?
I’d see how far
Just for completeness, all this is well documented:
CSV files:
By default there is no column name for a column of row names. If
‘col.names = NA’ and ‘row.names = TRUE’ a blank column name is
added, which is the convention used for CSV files to be read by
spreadsheets.
Dear Gabriel,
On 2021-07-01 6:29 p.m., Gabriel Becker wrote:
On Thu, Jul 1, 2021 at 1:46 PM Stephen Ellison
wrote:
Please run the reproducible example provided.
When you do, you will see that write.csv writes an unnecessary empty
header field ("") over the row names column. This makes the
On Thu, Jul 1, 2021 at 1:46 PM Stephen Ellison
wrote:
>
> Please run the reproducible example provided.
> When you do, you will see that write.csv writes an unnecessary empty
> header field ("") over the row names column. This makes the number of
> header fields equal to the number of columns
On 01/07/2021 3:11 p.m., Dirk Eddelbuettel wrote:
On 1 July 2021 at 20:00, Lluís Revilla wrote:
| I have a question related to changing maintainers.
| What happens when the old/current maintainer does not respond to
| emails or other methods of contact?
| Would the new maintainer need to wait
> the "unhelpful" column are the row names. They are considered an
> important part of a data frame and therefore the default (row.names =
> TRUE) is to not lose them (as there is no way back once you do). If you don't
> want to preserve the row names you can simply set row.names=FALSE.
Please
On 1 July 2021 at 20:00, Lluís Revilla wrote:
| I have a question related to changing maintainers.
| What happens when the old/current maintainer does not respond to
| emails or other methods of contact?
| Would the new maintainer need to wait until the package is removed
| from CRAN to submit
Thanks Uwe for answering,
I have a question related to changing maintainers.
What happens when the old/current maintainer does not respond to
emails or other methods of contact?
Would the new maintainer need to wait until the package is removed
from CRAN to submit it again?
Best,
Lluís
PS: Not
Hi All,
I'm trying to use the lldb debugger to debug some R code, but keep getting
the following error:
(base) R -d lldb
(lldb) target create "/Library/Frameworks/R.framework/Resources/bin/exec/R"
Current executable set to
'/Library/Frameworks/R.framework/Resources/bin/exec/R' (arm64).
(lldb) run
Yes, that would be a sensible way, I think.
Laurent
From: Fabricio de Almeida
Sent: 01 July 2021 19:42
To: Laurent Gatto; bioc-devel@r-project.org
Subject: RE: Question on copyright in Bioc vignette
Hi, Laurent.
Thank you for your suggestion. How would
Hi, Laurent.
Thank you for your suggestion. How would you mention that the vignette is
licensed under CC-BY? A section named "License" at the bottom of the vignette?
Best,
=
Fabrício de Almeida Silva
Undergraduate degree in Biological Sciences (UENF)
MSc. candidate
Dear Fabrício,
As far as I know, there's no explicit license on the documentation of a
package, and I'm not sure the the package/software licence applies to
documentation. I would explicitly mention that the figure (and possibly the
vignette) is released under a CC-BY (or any alternative) to
Hi, all.
I am writing a vignette for a package I plan to submit next week, and I would
like to include a figure explaining the package's algorithm. However, I would
also like to include this figure in the paper that describes the package. Does
anyone know if including the same figure in the
Hi Ben,
Please activate your account at
https://git.bioconductor.org/BiocCredentials/account_activation. Once you do
that, you can add SSH keys and gain access to your package.
Best,
Nitesh Turaga
Scientist II, Department of Data Science,
Bioconductor Core Team Member
Dana Farber Cancer
Both ways are fine with us, but the auto confirmation request will be
sent out in any case.
Best,
Uwe Ligges
On 01.07.2021 17:57, rmendelss gmail wrote:
Hi Uwe:
Is what you described the preferred way to change maintainers (I have just
taken over another package), or would you prefer
Hi Uwe:
Is what you described the preferred way to change maintainers (I have just
taken over another package), or would you prefer receiving an email from the
old maintainer before the submission?
Thanks,
-Roy
> On Jul 1, 2021, at 8:38 AM, Uwe Ligges
> wrote:
>
>
>
> On 01.07.2021
On 01.07.2021 16:10, Javier García Chamorro wrote:
Hi there, I have recently uploaded the first version of my R package to
CRAN. As it is part of my final degree project, I need to change the
maintainer to my supervisor, now that I have finished the project.
I changed in the DESCRIPTION file
That works for me. Thanks.
Mike
On Thu, Jul 1, 2021 at 2:07 PM Nitesh Turaga wrote:
>
> Hi
>
> Please try again. You should not see this error anymore.
>
> This was a mistake on our end.
>
> Best,
>
> Nitesh
>
>
>
> Nitesh Turaga
> Scientist II, Department of Data Science,
> Bioconductor Core
Hi there, I have recently uploaded the first version of my R package to
CRAN. As it is part of my final degree project, I need to change the
maintainer to my supervisor, now that I have finished the project.
I changed in the DESCRIPTION file the proper data to do so, but when
receiving back the
Dear Bioc,
For some reason my github public key isn’t working with the BioC git (see
comment). I'm just trying to push some fixes to my package under review.
Here is the command I'm running:
git remote -v
origin g...@github.com:benstory/mitoClone2 (fetch)
origin
Hi all,
In the last build report of my submission (
https://github.com/Bioconductor/Contributions/issues/2168 ) there is the
following warning to solve for Windows system
*Warning: file 'spatialDE/configure' did not have execute permissions:
corrected*
but I'm not sure how to fix it because in my
Hi
Please try again. You should not see this error anymore.
This was a mistake on our end.
Best,
Nitesh
Nitesh Turaga
Scientist II, Department of Data Science,
Bioconductor Core Team Member
Dana Farber Cancer Institute
> On Jul 1, 2021, at 1:49 AM, Michael Love wrote:
>
> I'm getting a
Thanks!
So what would be the prescribed way of assigning elements to a CPLXSXP if I
needed to?
One way I see is to do what most of the code inside the interpreter does
and grab the vector's data pointer:
COMPLEX(sexp)[index] = value;
COMPLEX0(sexp)[index] = value;
This will materialize
Thanks Johannes,
I was aware of the modules package (it was not suitable for my needs
unfortunately), but I did not know about box… somehow I managed to completely
miss it in my search (embarrassing, really).
My own package offers similar functionality to box, but is designed to closely
> In the end, I wrote a package that implements lightweight python-like
> modules for R and that has really improved my workflow. I hope to publish
> this package later this year after I have cleaned it up a bit.
Hi, are you aware of the previous work in this direction
Taras,
> That was my original plan as well, but managing and deploying dozens
> of little packages that are all under active development is a
> nightmare even with devtools. Just too much overhead, not to mention
> that coming up with names that would not have namespace conflicts was
> getting
Hi all,
I'm trying to debug some source code in my package, but whenever I try
anything on the command line that begins with "R", e.g.
R -d gdb -f buggy.R
I get the error message, "R: command not found". It's not recognizing any R
commands and I'm stumped as to why. What am I missing here? I'm
My new submission potools failed on Solaris:
https://www.r-project.org/nosvn/R.check/r-patched-solaris-x86/potools-00check.html
Likely reason is that one or more of the SystemRequirements are missing (I
put gettext as a catchall in the DESCRIPTION but more specifically it needs
msgfmt, msgmerge,
Stephen,
I am sure one can find a lot of small issues and inconsistencies with R and
it’s standard library. It has to support a lot of legacy cruft and the design
process — especially in the early days — focused on getting things done rather
than delivering a standard library of immaculate
Hi Greg,
That was my original plan as well, but managing and deploying dozens of little
packages that are all under active development is a nightmare even with
devtools. Just too much overhead, not to mention that coming up with names that
would not have namespace conflicts was getting silly.
> Ben Bolker
> on Wed, 30 Jun 2021 20:23:27 -0400 writes:
>A colleague recently submitted a paper to JSS and was
> advised to address the following warning which occurs when
> their package
> (https://CRAN.R-project.org/package=pcoxtime) is loaded:
> Warning
31 matches
Mail list logo
