Roswell Park Cancer Institute
Department of Biostatistics & Bioinformatics
Elm & Carlton Streets
Buffalo, New York 14263
From: Bioc-devel on behalf of Michael Love
Sent: Thursday, June 7, 2018 8:56:55 AM
To: bioc-devel
Subject: [Bioc-devel] w
rk 14263
From: Shepherd, Lori
Sent: Thursday, June 7, 2018 12:12:39 PM
To: Michael Love; bioc-devel
Subject: Re: [Bioc-devel] workflows are missing from landing pages
Sorry the announcement got delayed. We were making updates to the views and
website code that displays the landi
It seems like the vignettes are not showing up here:
https://bioconductor.org/packages/release/workflows/
https://bioconductor.org/packages/release/workflows/html/rnaseqGene.html
https://bioconductor.org/packages/release/workflows/html/RnaSeqGeneEdgeRQL.html
t; > transition over to the new release just as done for software packages -
>> >
>> > The workflow are built monday, wednesday, and friday and the new landing
>> > pages will reflect when the package is propagated like the other types of
>> > packages.
>>
nformatics
> Elm & Carlton Streets
> Buffalo, New York 14263
> From: Bioc-devel <bioc-devel-boun...@r-project.org> on behalf of
> Aaron Lun <a...@wehi.edu.au>
> Sent: Sunday, April 1, 2018 2:17:09 PM
> To: Hervé Pagès; bioc-devel@r-project.org
> Subject: Re:
hepherd
> >
> > Bioconductor Core Team
> >
> > Roswell Park Cancer Institute
> >
> > Department of Biostatistics & Bioinformatics
> >
> > Elm & Carlton Streets
> >
> > Buffalo, New York 14263
> >
> >
nductor Core Team
>
> Roswell Park Cancer Institute
>
> Department of Biostatistics & Bioinformatics
>
> Elm & Carlton Streets
>
> Buffalo, New York 14263
>
>
> From: Bioc-devel <bioc-devel-boun...@r-project.org> on behalf
, April 1, 2018 2:17:09 PM
To: Herv� Pag�s; bioc-devel@r-project.org
Subject: Re: [Bioc-devel] Workflows are now in git (and other Important
workflow-related changes)
Thanks everybody, this is much appreciated.
On that note, will the compiled workflows shown at:
https://www.bioconducto
Thanks everybody, this is much appreciated.
On that note, will the compiled workflows shown at:
https://www.bioconductor.org/help/workflows/
... be updated to reflect changes in the git repositories for the
workflows?
Or will the workflow page just directly link to the landing page for
each
Thank you, Lori, Valerie, Andrzej, Nitesh and Hervé, this is great
news! This should help further rationalize the authoring and maintenance
of workflows.
--
I'm sure many have also seen the call to submit workflows to the
Bioconductor gateway on F1000Research
To the authors/maintainers of the workflows:
Following the svn-to-git migration of the software and data experiment
packages last summer, we've completed the migration of the workflow
packages.
The canonical location for the workflow source code now is
git.bioconductor.org
Please use your git
Hello,
The workflow builder has been updated to use Bioconductor 3.6 in preparation
for the release. Please monitor any workflows you may maintain and debug
accordingly.
Also, new workflows will now be submitted to Bioconductor in the form of a
package as documented:
Susan
I’m giving my reply via the Bioconductor mailing list to also include the
others, both for input from the core team, and for information of other
workflow authors.
The preferred approach is to host a live version of the workflow on
http://www.bioconductor.org/help/workflows/ - with the
gt;> To: "Aaron Lun" <a...@wehi.edu.au>
>> Cc: "bioc-devel" <bioc-devel@r-project.org>
>> Sent: Sunday, February 28, 2016 5:59:41 AM
>> Subject: Re: [Bioc-devel] workflows running Bioc-devel
>> +1
>>
>> I'm also interested in having t
t;
> To: "Aaron Lun" <a...@wehi.edu.au>
> Cc: "bioc-devel" <bioc-devel@r-project.org>
> Sent: Sunday, February 28, 2016 5:59:41 AM
> Subject: Re: [Bioc-devel] workflows running Bioc-devel
> +1
>
> I'm also interested in having the option of devel / release wor
+1
I'm also interested in having the option of devel / release workflow
branches for the reasons Aaron mentions.
I develop software and workflow in tandem but currently there is a
disconnect in showing publicly how software changes will impact a workflow.
[[alternative HTML version
Sorry if I have overlooked something… referring to
http://www.bioconductor.org/developers/how-to/workflows Is there a standardized
way to manage
- dependencies
- versions
In principle, these could be automagically computed (?), but would still have
to be exposed to workflow users using an
- Original Message -
From: Wolfgang Huber whu...@embl.de
To: bioc-devel@r-project.org
Sent: Monday, September 29, 2014 12:24:54 PM
Subject: [Bioc-devel] Workflows
Sorry if I have overlooked something… referring to
http://www.bioconductor.org/developers/how-to/workflows
GMT+2, Dan Tenenbaum
dtene...@fhcrc.org ha scritto:
- Original Message -
From: Wolfgang Huber whu...@embl.de
To: bioc-devel@r-project.org
Sent: Monday, September 29, 2014 12:24:54 PM
Subject: [Bioc-devel] Workflows
Sorry if I have overlooked something… referring to
http
- Original Message -
From: Wolfgang Huber whu...@embl.de
To: Dan Tenenbaum dtene...@fhcrc.org
Cc: bioc-devel@r-project.org
Sent: Monday, September 29, 2014 12:35:18 PM
Subject: Re: [Bioc-devel] Workflows
Dear Dan
Thanks. What is the recommended procedure for people wanting
20 matches
Mail list logo
