FireCloud is now powered by Terra! -- STARTING MAY 1st, 2019 THIS WEBPAGE WILL NO LONGER BE UPDATED.
From now on, please visit the Terra Help Center for documentation, tutorials, roadmap and feature announcements.
Want to talk to a human? Email the helpdesk, post feature requests or chat with peers in the community forum.



November 14, 2018

  1. The FireCloud UI now has links in a few additional places for improved usability:
    • when viewing the list of method configurations in a workspace, the name of the referenced method is now a link.
    • when viewing a single method configuration in a workspace, the snapshot id now links to the referenced method.
    • when viewing a submission, the method configuration name is now a link.
  2. The API to get call-level metadata for a workflow now supports query parameters to control which fields should be returned in the response. This is particularly useful for querying specific data about a workflow where the full response is otherwise very large. Cromwell has offered this functionality for multiple releases but it has not been exposed via the FireCloud API. See the Swagger documentation for specifics.
  3. The login process now eliminates an unnecessary Ajax request for the Terms of Service content allowing for a slight incremental performance improvement during login.

November 1, 2018

  1. The workflow timing diagram in the Monitor tab of the Workspaces has been updated for stability. Additionally, where the diagram previously displayed “myworkflow.mycall” for each row, it now displays “mycall” to save space.
  2. The “all_broad_users” is now a managed group.
  3. The link for the set in the Data tab now works for types that are not part of the FireCloud model.
  4. Leo now does not allow deletion of a cluster while in the “Creating” status.
  5. To offer continued platform security, FireCloud will now require users to actively accept FireCloud’s Terms of Service prior to using the platform. The Terms of Service will be displayed once a user logs into FireCloud. Users will be unable to work on FireCloud until the Terms of Service have been accepted.

Return to top

Thu 1 Nov 2018
Comment on this article


- Recent posts



- Follow us on Twitter

FireCloud

@BroadFireCloud

RT @TerraBioApp: Terra #OpenScience Contest -- You be the judge! Over the past month we ran a contest in which four teams created workspace…
26 Jun 19
FireCloud project resources are affected by this GCP outage as well. https://t.co/rbhB2MMJd7
2 Jun 19
RT @jklemm: Also available on @BroadFireCloud where it was leveraged to process all of the RNA-Seq data from TCGA and GTEx through STAR-fus…
29 May 19
RT @TerraBioApp: Do you have a pet workflow or a favorite notebook? Have you thought about sharing them with the world, but keep pushing it…
18 May 19
RT @jklemm: Great meeting this week with #NCICloud and Data Commons Framework teams discussing cancer research priorities for #NCICommons.…
15 May 19

- Our favorite tweets from others

See the theme? Green! https://t.co/cfHQK2cmrU
24 Jul 19
I will be introducing Terra to aspiring bioinformatics researchers later this month. I discovered FireCloud (predec… https://t.co/CcBXL5Nl09
2 May 19
Pipelines API is used by a number of popular tools, such as Firecloud/Terra from @broadinstitute. @BroadFireCloudhttps://t.co/z06kx9PRBg
11 Apr 19
The macaque genome isn't finished so it has over 200K contigs. I call them the Rhesus pieces.
15 Mar 19

See more of our favorite tweets...