Good day,
The problem is simply caused by an incorrectly typed file path. The error
message isn't clear about this and describes some temporary file name (based on
today's date and time) which is confusing. Perhaps the importFusionData
function could be made more robust by checking for the file
Hi Dario,
I am the maintainer of chimera package
thank for the info I am going to check which is the problem in
importFusionData.
There is only one example of data import, because of limits in package size.
An other example can be retrieved from:
download.file("http://sourceforge.net/projects/oc
On 11/06/2016 06:10 PM, Ioannis Vardaxis wrote:
Hi,
For the references I just used @references \insertRef{key}{pkg}, and
although it shows up in the ??pkg::function help, I get an error in
biocCheck
it's not enough to say that you got an error, because there are many
possible errors. What err
Hi,
For the references I just used @references \insertRef{key}{pkg}, and
although it shows up in the ??pkg::function help, I get an error in
biocCheck
For the vignettes, my vignette is generated without any errors. What I get
as en error in Rcheck is that: “From R version >=3.2 vignettes is requi
On 11/06/2016 04:54 PM, Ioannis Vardaxis wrote:
Thanks for the answer,
I have some other questions about BiocCheck.
First I get the following warning:
* This is a software package, checking vignette directories...
* ERROR: 'vignettes' directory!
I have my vignettes directory in the inst/d
Thanks for the answer,
I have some other questions about BiocCheck.
First I get the following warning:
* This is a software package, checking vignette directories...
* ERROR: 'vignettes' directory!
I have my vignettes directory in the inst/doc/vignettes. If I change the
directory and place
Good day,
The examples section of importFusionData is almost entirely commented out, so
it's unclear whether it works. Since a lot of the package code is never run by
R CMD check and the test coverage is 0%, it's plausibly a package development
issue.
-
Dari
