I am building a R package, and I am facing an issue caused (as far as I
understand) by the fact that some functions out of my package rely on two
fuctions having the same name and coming from 2 different packages:
pROC::roc
spatstat::roc
When checking the package via devtools::check(), I get th
Does your package import or depend on 'GmAMisc'? This package appears
to Depend on both spatstat and pROC.
Alternatively you have imported both packages in your NAMESPACE.
If neither of these clues help, could you post your DESCRIPTION and
NAMESPACE files? Probably all we'd need.
On 6 August 2
El mar., 7 ago. 2018 a las 9:32, Gianmarco Alberti
() escribió:
>
> I am building a R package, and I am facing an issue caused (as far as I
> understand) by the fact that some functions out of my package rely on two
> fuctions having the same name and coming from 2 different packages:
>
> pROC::r
... and even if you are importing from several packages, you should
import selective via importFrom directoves.
If you need two functions with identical names, import at most one of
them and rather use pkg::foo syntax to access them.
Best,
Uwe Ligges
On 07.08.2018 10:14, Iñaki Úcar wrote
Probably discussed already, but what is the difference between using “::” and
“ImportFrom”? I usually use ImportFrom and “::” just to make clear, where the
function is coming from - is this a problem?
Rainer
> On 7 Aug 2018, at 11:14, Uwe Ligges wrote:
>
> ... and even if you are importing f
Thanks indeed for the clarification.
I eventually managed to solve the issue. By the way, I have moved of the
packages my package relies on to the Imports section.
I have checked my package and it returned no error nor note nor warning.
I have submitted it to CRAN.
Thanks for your prompt feedbac
On 05/08/2018 4:21 PM, Gianmarco Alberti wrote:
I am building a R package, and I am facing an issue caused (as far as I
understand) by the fact that some functions out of my package rely on two
fuctions having the same name and coming from 2 different packages:
pROC::roc
spatstat::roc
As Iñ
This is very useful - didn’t know that.
Thanks
Rainer
> On 7 Aug 2018, at 13:11, Duncan Murdoch wrote:
>
> On 05/08/2018 4:21 PM, Gianmarco Alberti wrote:
>> I am building a R package, and I am facing an issue caused (as far as I
>> understand) by the fact that some functions out of my packa
@Duncan:
Extremely interesting...thanks.
Gm
**
Dr Gianmarco Alberti (PhD)
(currently)
Research Support Officer II
Department of Classics and Archaeology
Faculty of Arts
University of Malta
(starting from 3rd September 2018)
Lecturer in Spatial Forensics
Depa
In my package I open handles to temporary files from c++, handles to
them are returned to R through vptr objects. The files are deleted then
the corresponding R-object is deleted and the garbage collector runs:
a <- lvec(10, "integer")
rm(a)
Then when the garbage collector runs the file is
Why not add functionality that allows to delete object + runs cleanup code?
Best,
Uwe Ligges
On 07.08.2018 14:26, Jan van der Laan wrote:
In my package I open handles to temporary files from c++, handles to
them are returned to R through vptr objects. The files are deleted then
the corres
I am new to CRAN submissions and need assistance.
I received this set of error messages previously. I removed all these hidden
files before resubmitting my package. They are back.
Question #1 How do I prevent this this?
PJO:Desktop PJO$ tar -zcvf Basic.tar.gz Basic
Found the following hidden fil
Copy this output into a file called .Rbuildignore at the top of the directory:
> .DS_Store
> .RData
> .Rhistory
> ._*
> .gitignore
> .travis.yml
> R/.DS_Store
> R/._*
> data/.DS_Store
> data/.Rapp.history
> man/.Rapp.history
> vignettes/._*
> vignettes/.gitignore
> .Rproj.user
> .gi
On 7 August 2018 at 16:27, Ossenbruggen, Paul wrote:
| I am new to CRAN submissions and need assistance.
|
| I received this set of error messages previously. I removed all these hidden
files before resubmitting my package. They are back.
| Question #1 How do I prevent this this?
1. (Optional)
Hello,
I believe the missed spelled words are false/positives, but I am new to R
package development and uncertain if these Notes are will cause rejection:
Possibly mis-spelled words in DESCRIPTION:
cartools (3:8)
Unknown, possibly mis-spelled, fields in DESCRIPTION:
‘Remotes'
The follo
On 07.08.2018 20:07, Ossenbruggen, Paul wrote:
Hello,
I believe the missed spelled words are false/positives, but I am new to R
package development and uncertain if these Notes are will cause rejection:
Possibly mis-spelled words in DESCRIPTION:
cartools (3:8)
Software names (only) s
On my mail client the two “quotes” are not matching. One appears vertical and
the other slightly slanting.
Sent from my iPhone (which could mean I’m seeing an artifact arising in
Cupertino. )
David
> On Aug 7, 2018, at 11:11 AM, Uwe Ligges
> wrote:
>
>
>
>> On 07.08.2018 20:07, Ossenbrug
On 07/08/2018 12:27 PM, Ossenbruggen, Paul wrote:
I am new to CRAN submissions and need assistance.
I received this set of error messages previously. I removed all these hidden
files before resubmitting my package. They are back.
Question #1 How do I prevent this this?
PJO:Desktop PJO$ tar -zc
18 matches
Mail list logo
