You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am testing the Honeybadger package and we have mapping to an assembly that has chromosome names without the "chr" so I modified setGexpMats to not add on "chr" to the chrom names and then tested running:
It failed and I found that the chrs parameter is not passed to the the function again at the recursion step, same thing for all params that are not default in the original call to the function. This is the part where it fails:
Another comment - I need to run the package on a secure server with no internet access, so it would be preferred to be able to pass a data frame with gene annotation instead of the mart object. I made my own function that takes the gos data.frame instead of the mart.obj as input and at the same time changed the chromosome names. Which led me to this new problem...
The text was updated successfully, but these errors were encountered:
Please provide the error messages returned by these failed functions. Otherwise, it is very difficult for me to understand what problems you are referring to.
Hello,
I am testing the Honeybadger package and we have mapping to an assembly that has chromosome names without the "chr" so I modified
setGexpMats
to not add on "chr" to the chrom names and then tested running:hb$calcGexpCnvBoundaries(init=TRUE, verbose=FALSE, chrs=as.character(1:22))
It failed and I found that the
chrs
parameter is not passed to the the function again at the recursion step, same thing for all params that are not default in the original call to the function. This is the part where it fails:Another comment - I need to run the package on a secure server with no internet access, so it would be preferred to be able to pass a data frame with gene annotation instead of the mart object. I made my own function that takes the gos data.frame instead of the mart.obj as input and at the same time changed the chromosome names. Which led me to this new problem...
The text was updated successfully, but these errors were encountered: