Oh wow, I didn't know you could put a DataFrame into a single column of
another DataFrame. That actually solves a problem for me too (I don't
intend to expose nested DataFrames to the users though).
On 6/17/15 7:23 PM, Martin Morgan wrote:
On 06/17/2015 11:41 AM, davide risso wrote:
Dear list
On 06/17/2015 11:41 AM, davide risso wrote:
Dear list,
I'm creating an R package to store RNA-seq data of a somewhat large project
in which I'm involved.
One of the initial goals is to compare different pre-processing pipelines,
hence I have multiple expression matrices corresponding to the sam
Hi Michael,
On 06/17/2015 12:35 AM, Michael Love wrote:
Background:
With previous approaches that I would recommend to users for building
txdb along the way of making count tables, it was desirable that the
GTF release information would *automatically* be passed into the
metadata of the rowRang
Dear list,
I'm creating an R package to store RNA-seq data of a somewhat large project
in which I'm involved.
One of the initial goals is to compare different pre-processing pipelines,
hence I have multiple expression matrices corresponding to the same samples.
The SummarizedExperiment class seem
I have (in the past couple of minutes) added a more detailed description to
all of the GitHub pages. If you have URL or BugReports fields in your
package DESCRIPTION those are used to provide links to the project page and
bug tracker if they are available, see Roberts
https://github.com/Bioconduct
Why not write your own *readme.md* file for the package and put the link
there? There is nothing stopping the maintainer from having a README file
in the package. Although it does not show up on the Bioconductor page, it
shows up nicely on Github:
My package:
https://github.com/Bioconductor-mirro
It would be cool if we could somehow get the equivalent of the
bioconductor package page to show up as the "readme" on the github
page. Or at least, if there could be a very obvious link from the
mirror repository to the maintainer repository, without having to
click through to the Bioconductor pac
Dear Dan,
I update my package GOSemSim(https://github.com/GuangchuangYu/GOSemSim),
with the following steps:
1. delete the git-svn-bridge
1. bash /path/to/update_remotes.sh
2. git checkout devel
3. git checkout master
4. git merge devel
All was fine without any error.
But when I follow the in
Background:
With previous approaches that I would recommend to users for building
txdb along the way of making count tables, it was desirable that the
GTF release information would *automatically* be passed into the
metadata of the rowRanges of the SummarizedExperiment.
for example, in parathyroi
