Difference between revisions of "2018 PAG Hackathon"

From GMOD
Jump to: navigation, search
(Suggested Topics)
Line 10: Line 10:
 
# [http://www.internationalgenome.org/faq/what-are-cram-files/ CRAM] support for [https://github.com/GMOD/jbrowse/issues/546 JBrowse] and [https://github.com/GMOD/jbrowse/issues/926 CRAI indexes] and [https://github.com/GMOD/Apollo/issues/550 extend to  Apollo].
 
# [http://www.internationalgenome.org/faq/what-are-cram-files/ CRAM] support for [https://github.com/GMOD/jbrowse/issues/546 JBrowse] and [https://github.com/GMOD/jbrowse/issues/926 CRAI indexes] and [https://github.com/GMOD/Apollo/issues/550 extend to  Apollo].
 
# Customize BAM tracks in Apollo
 
# Customize BAM tracks in Apollo
 
+
# Updating table descriptions to generalize mage to include next-gen sequencing experiments and other possible analyses instead of microarray only
 +
# Adding a  cvalue_id field to the biomaterialprop table, as is done for the natural diversity module.  This allows the property values to also utilize a cvterm.
  
 
== Resources ==
 
== Resources ==
  
 
# [http://genomearchitect.readthedocs.io/en/latest/Apollo2Build.html Apollo dev guide]
 
# [http://genomearchitect.readthedocs.io/en/latest/Apollo2Build.html Apollo dev guide]

Revision as of 18:30, 13 December 2017

The GMOD hackathon will take place January 10-11, 2018 (a few days before PAG, but not on January 12 so as not to overlap with the Tripal user meeting). It will take place at the Town and Country Hotel in the Brittany room. The Brittany room is in the eastern edge of the property in the north/south center, off of the Regency Courtyard). We expect that topics will include JBrowse (server-side stuff and plugins), Galaxy connectivity and plugins, and Tripal plugins (this hackathon overlaps the Tripal hackathon and user meeting that runs January 11-12).

Registration is $50 which covers part of the fee for the room (where the rest is made up from the kind JBrowse folks) and lunch on the first day. Please use the Eventbrite page to register and pay.

Suggested Topics

  1. Improving the Python library for interacting with the Apollo API
  2. Adding an “Instructor” role to facilitate the usage of Apollo in an educational setting [1]
  3. Incorporating additional metadata to an organism in Apollo to facilitate integration with Galaxy Histories.
  4. CRAM support for JBrowse and CRAI indexes and extend to Apollo.
  5. Customize BAM tracks in Apollo
  6. Updating table descriptions to generalize mage to include next-gen sequencing experiments and other possible analyses instead of microarray only
  7. Adding a cvalue_id field to the biomaterialprop table, as is done for the natural diversity module. This allows the property values to also utilize a cvterm.

Resources

  1. Apollo dev guide