Hi I had the following error while checking the package
https://github.com/xyang2uchicago/BioTIP
> base::assign(".ptime", proc.time(), pos = "CheckExEnv")
> ### Name: getCluster_methods
> ### Title: Clustering Network Nodes
> ### Aliases: getCluster_methods
>
> ### ** Examples
>
> test = list('st
Hi Aditya,
It feels that a coercion method from BSgenome to GRanges should rather
be defined in the BSgenome package itself. Patch/PR welcome on GitHub.
More generally speaking, coercion methods should be defined in a place
that is "as close as possible" to the "from" or "to" classes rather tha
Hi
I am having the following warnings and not sure what to update.
Warning in rgl.init(initValue, onlyNULL) :
RGL: GLX extension missing on server
Warning: 'rgl_init' failed, running with rgl.useNULL = TRUE
The package github link is here : https://github.com/xyang2uchicago/BioTIP
Zhezhen
Dear all,
Could the package name be changed after released?
I have a package which has been in Bioconductor for more than one year. We
want to publish a paper about it recently. My advisor wants to use a new
name which can better reflect the objective of the package.
Thanks for any help!
Best,
L
Thanks a lot for the info! So from my understanding we dont use any
trimming or editing function from ImageMagick directly. I think this is
rather knitr based since we just include png files in the vignette.
I guess it was an hickup since now the error is gone over night.
Best regards,
Christian
Hi Simon,
I take this back actually. I think the best way forward is just undo the code
changes, and add a new version number to it ( 1.9.3) and push.
Step 1,
Since your version 1.9.2 is already on Bioconductor, first sync your
GitHub with that version.
Step 2,
Undo the code
Hi Simon,
Bioconductor's git system doesn't allow force push (This is a feature) . It
only allows a force push by administrators (Bioconductor Core team). Please
send me a link to your GitHub repo which is at 1.9.0, and I will sync it for
you.
I've updated the link where the instructions are
Begin forwarded message:
From: ni41435_ca
mailto:nitesh.tur...@roswellpark.org>>
Subject: Re: Update InterMineR maintainer
Date: September 10, 2019 at 8:08:40 AM EDT
To: Rachel Lyne mailto:rac...@intermine.org>>
Lower case 'i' vs upper case in the package name 'I'.
It's a typo. "Git" is cas
Forwarding to Bioc-devel for issue tracking.
Begin forwarded message:
From: Rachel Lyne mailto:rac...@intermine.org>>
Subject: Re: Update InterMineR maintainer
Date: September 10, 2019 at 8:03:55 AM EDT
To: "Turaga, Nitesh"
mailto:nitesh.tur...@roswellpark.org>>
git remote -v:
origin
g.
Hi,
this is the way described in [1].
Cheers,
S
On 10.09.19 13:51, Neumann, Steffen wrote:
Hi,
that's not the git way to do it. Your previous commit is already
out in the open, if you git reset, that would be dangling in the air.
I really love this decision tree:
https://sethrobertson.githu
Hi,
that's not the git way to do it. Your previous commit is already
out in the open, if you git reset, that would be dangling in the air.
I really love this decision tree:
https://sethrobertson.github.io/GitFixUm/fixup.html
which in your case will get you probably to
https://sethrobertson.gi
Hi all,
following our previous TensorFlow discussion, I am trying to reset to a
previous commit and get rid of the TF changes in the meantime.Resetting
back to the last working commit [1] that doesn't use TF gives me this
error though:
$ git reset --hard 4e267949562a0b38b16495892c4ef4c0dcf7b6f3
12 matches
Mail list logo
