diff --git a/.gitignore b/.gitignore index dc638be..8c9a810 100644 --- a/.gitignore +++ b/.gitignore @@ -8,3 +8,6 @@ spell_check_results.tsv .RData .httr-oauth docker/git_token.txt +.Rproj.user +.Rbuildignore +*.Rproj diff --git a/docs/404.html b/docs/404.html index 7344bb5..439fbab 100644 --- a/docs/404.html +++ b/docs/404.html @@ -22,7 +22,7 @@ - + @@ -87,7 +87,10 @@
  • What are CoFests!?
    • -
  • Organizer Guide
    • +
  • Organizer Guide +
  • Topics
  • 1 Scalable ML and Data Science
  • 2 Polygenic Risk Score Analysis
    • diff --git a/docs/About.md b/docs/About.md index b2678c6..e270251 100644 --- a/docs/About.md +++ b/docs/About.md @@ -53,7 +53,7 @@ These credits are based on our [course contributors table guidelines](https://gi ## collate en_US.UTF-8 ## ctype en_US.UTF-8 ## tz Etc/UTC -## date 2024-09-17 +## date 2024-09-18 ## pandoc 3.1.1 @ /usr/local/bin/ (via rmarkdown) ## ## ─ Packages ─────────────────────────────────────────────────────────────────── diff --git a/docs/about-the-authors.html b/docs/about-the-authors.html index 822e7af..38ed90b 100644 --- a/docs/about-the-authors.html +++ b/docs/about-the-authors.html @@ -22,7 +22,7 @@ - + @@ -87,7 +87,10 @@
  • What are CoFests!?
    • -
  • Organizer Guide
    • +
  • Organizer Guide +
  • Topics
  • 1 Scalable ML and Data Science
  • 2 Polygenic Risk Score Analysis
    • @@ -272,7 +275,7 @@

    About the Authors + @@ -87,7 +87,10 @@
  • What are CoFests!?
    • -
  • Organizer Guide
    • +
  • Organizer Guide +
  • Topics
  • 1 Scalable ML and Data Science
  • 2 Polygenic Risk Score Analysis
    • @@ -131,7 +134,7 @@

    What are CoFests!?

    diff --git a/docs/index.md b/docs/index.md index 7576672..466b69e 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1,6 +1,6 @@ --- title: "AnVIL CoFests! 2024" -date: "September 17, 2024" +date: "September 18, 2024" site: bookdown::bookdown_site documentclass: book bibliography: book.bib @@ -15,7 +15,7 @@ favicon: assets/AnVIL_style/anvil_favicon.ico CollaborationFests!, also known as **CoFests!** (and sometimes as "hackathons"), are collaborative work events where we expand and improve the AnVIL community and the AnVIL ecosystem. Sometimes these gatherings are focused on AnVIL, and sometimes they are part of larger communities. -* *Modified from https://galaxyproject.org/events/cofests* +* *Modified from * ## What's in a name: CollaborationFests! and Hackathons {- .unlisted} diff --git a/docs/organizer-guide.html b/docs/organizer-guide.html index a76d3fe..560d63c 100644 --- a/docs/organizer-guide.html +++ b/docs/organizer-guide.html @@ -22,7 +22,7 @@ - + @@ -87,7 +87,10 @@
  • What are CoFests!?
    • -
  • Organizer Guide
    • +
  • Organizer Guide +
  • Topics
  • 1 Scalable ML and Data Science
  • 2 Polygenic Risk Score Analysis
    • @@ -139,31 +142,105 @@

    Organizer Guide

    CoFests! Goals

      -
    • Build community
      • -
    • Develop high interest topics
      • -
    • Open science
      • +
    • Build an inclusive community that is supportive of newcomers
      • +
    • Contribute to open science
      • +
    • Produce a final product that accomplishes one of the following for a topic +
        +
      • Makes useful forward progress
        • +
      • Identifies opportunities and boundaries or limitations
        • +

    Logistics

    -
    -
    -

    Example Schedule

    +
  • 3 Parallel tracks, 5+ hours across Nov 12/13
      -
    • Problem statement (short demo)
      • -
    • Brainstorming
      • -
    • Onboarding
      • -
    • Work-regroup, work-regroup
      • -
    • Report out
      • +
    • Scalable Machine Learning and Data Science
      • +
    • Polygenic Risk Score Analysis
      • +
    • Wrap a Tool (+ Intro AnVIL/WDL)
      • +
    • +
  • Scientific Lead and AnVIL Outreach co-Lead for support
    • +
  • We expect 4-10 participants per track
    • +

    Prior to the CoFests, the scientific and AnVIL Outreach co-Leads will work together to enumerate some ideas for final products and post them publicly in this book.

    +
    +

    The AnVIL Outreach co-Lead will help add content to this guide, onboard newer AnVIL users to the platform, and provide guidance on the final product / report out.

    +
    +
    +
    +

    Final Product / Report Out

    +

    The final product of CoFests doesn’t need to be code! These Collaboration Fests can support story-boarding future work or development of documentation or training materials. If it’s something that will help the community and make progress on an AnVIL associated topic and there’s sufficient interest, the idea is game! As Galaxy phrased it for their CoFests:

    +
    +

    [The goal of collaboration fests is to expand the ecosystem] Not just the code, but the whole ecosystem. That includes training, tools, best practice workflows, documentation, test cases, translations, infrastructure, and yes, even code.

    +
    +
    +

    It helps us a lot if you can fill out some basic Report Out details. At the end of Day 2, your track will share a final report during the CoFest Recap Session!

    +
    +
    +
    +

    Example Schedule for a Track

    +
    +

    Day 1 (2.5 hours)

    + ++++ + + + + + + + + + + + + + + + + + + + + + + + + +
    TaskTime & Lead
    Problem statement. Provide background info on the track’s overall topic and may include a brief summary of the pre-worked collaboration ideas.20-30 minutes (Scientific Lead)
    Brainstorming. What project will the track tackle? Focus on understanding the participant backgrounds and skills and matching those with track ideas and actionable tasks to accomplish the goal.15-30 minutes (Both)
    Onboarding. Handle billing accounts and other logistics necessary to accomplish the work.30-60 minutes (AnVIL Outreach co-Lead)
    Work-regroup, work-regroup. Formal collaboration work time left before dinner. (Groups may choose to work together informally after dinner too)30-60 minutes (N/A)
    +
    +
    +

    Day 2 (3 hours)

    + ++++ + + + + + + + + + + + + + + + + +
    TaskTime & Lead
    Work-regroup, work-regroup. Formal collaboration work time (with a coffee break).2-2.5 hours (N/A)
    Construct a “report out”. The report out may be a Google doc, Google slides, a GitHub repository, a website, an OTTR book, etc.30-60 minutes (AnVIL Outreach co-Lead)
    + diff --git a/docs/organizer-guide.md b/docs/organizer-guide.md index 6f5e8c4..2009d68 100644 --- a/docs/organizer-guide.md +++ b/docs/organizer-guide.md @@ -7,20 +7,51 @@ This event is a key event for professionals in the genomics community interested ## CoFests! Goals {- .unlisted} -- Build community -- Develop high interest topics -- Open science +- Build an inclusive community that is supportive of newcomers +- Contribute to [open science](https://en.wikipedia.org/wiki/Open_science) +- Produce a final product that accomplishes one of the following for a topic + - Makes useful forward progress + - Identifies opportunities and boundaries or limitations ## Logistics {- .unlisted} -- Parallel tracks, 5+ hours across Nov 12/13 -- Scientific Lead and Co-Lead -- ~4-10 participants per topic +- 3 Parallel tracks, 5+ hours across Nov 12/13 + - Scalable Machine Learning and Data Science + - Polygenic Risk Score Analysis + - Wrap a Tool (+ Intro AnVIL/WDL) +- Scientific Lead and AnVIL Outreach co-Lead for support +- We expect 4-10 participants per track -## Example Schedule {- .unlisted} +Prior to the CoFests, the scientific and AnVIL Outreach co-Leads will work together to enumerate some ideas for final products and post them publicly in this book. -- Problem statement (short demo) -- Brainstorming -- Onboarding -- Work-regroup, work-regroup -- Report out +::: {.notice} +The AnVIL Outreach co-Lead will help add content to this guide, onboard newer AnVIL users to the platform, and provide guidance on the final product / report out. +::: + +## Final Product / Report Out {-} + +The final product of CoFests doesn't need to be code! These Collaboration Fests can support story-boarding future work or development of documentation or training materials. If it's something that will help the community and make progress on an AnVIL associated topic and there's sufficient interest, the idea is game! [As Galaxy phrased it for their CoFests:](https://galaxyproject.org/events/gcc2023/cofest/#goals) + +> [The goal of collaboration fests is to expand the ecosystem] Not just the code, but the whole ecosystem. That includes training, tools, best practice workflows, documentation, test cases, translations, infrastructure, and yes, even code. + +::: {.notice} +It helps us a lot if you can fill out some basic [Report Out details](https://docs.google.com/document/d/1wLK88p_tY6L-a8IF5dIe7gmDlJC1RxeU8_pm1ClU2IE/edit?usp=sharing). At the end of Day 2, your track will **share a final report during the CoFest Recap Session**! +::: + +## Example Schedule for a Track {- .unlisted} + +### Day 1 (2.5 hours) {-} + +| Task | Time & Lead | +|:-------------------------:|:-----------:| +| **Problem statement.** Provide background info on the track's overall topic and may include a brief summary of the pre-worked collaboration ideas. | 20-30 minutes (Scientific Lead) | +| **Brainstorming.** What project will the track tackle? Focus on understanding the participant backgrounds and skills and matching those with track ideas and actionable tasks to accomplish the goal. | 15-30 minutes (Both) | +| **Onboarding.** Handle billing accounts and other logistics necessary to accomplish the work. | 30-60 minutes (AnVIL Outreach co-Lead) | +| **Work-regroup, work-regroup.** Formal collaboration work time left before dinner. (Groups may choose to work together informally after dinner too) | 30-60 minutes (N/A) | + +### Day 2 (3 hours) {-} + +| Task | Time & Lead | +|:-------------------------:|:------------| +| **Work-regroup, work-regroup.** Formal collaboration work time (with a coffee break). | 2-2.5 hours (N/A) | +| **Construct a "report out".** The report out may be a Google doc, Google slides, a GitHub repository, [a website](https://github.com/jhudsl/OTTR_Template_Website), an [OTTR book](https://github.com/jhudsl/OTTR_Template), etc. | 30-60 minutes (AnVIL Outreach co-Lead) | diff --git a/docs/polygenic-risk-score-analysis.html b/docs/polygenic-risk-score-analysis.html index cc05b70..cd3b03c 100644 --- a/docs/polygenic-risk-score-analysis.html +++ b/docs/polygenic-risk-score-analysis.html @@ -22,7 +22,7 @@ - + @@ -87,7 +87,10 @@
  • What are CoFests!?
    • -
  • Organizer Guide
    • +
  • Organizer Guide +
  • Topics
  • 1 Scalable ML and Data Science
  • 2 Polygenic Risk Score Analysis
    • diff --git a/docs/references.html b/docs/references.html index 31d7861..c8d5f46 100644 --- a/docs/references.html +++ b/docs/references.html @@ -22,7 +22,7 @@ - + @@ -87,7 +87,10 @@
  • What are CoFests!?
    • -
  • Organizer Guide
    • +
  • Organizer Guide +
  • Topics
  • 1 Scalable ML and Data Science
  • 2 Polygenic Risk Score Analysis
    • diff --git a/docs/scalable-ml-and-data-science.html b/docs/scalable-ml-and-data-science.html index 66f0fe8..3826415 100644 --- a/docs/scalable-ml-and-data-science.html +++ b/docs/scalable-ml-and-data-science.html @@ -22,7 +22,7 @@ - + @@ -87,7 +87,10 @@
  • What are CoFests!?
    • -
  • Organizer Guide
    • +
  • Organizer Guide +
  • Topics
  • 1 Scalable ML and Data Science
  • 2 Polygenic Risk Score Analysis
    • diff --git a/docs/search_index.json b/docs/search_index.json index 3eb3540..f251898 100644 --- a/docs/search_index.json +++ b/docs/search_index.json @@ -1 +1 @@ -[["index.html", "AnVIL CoFests! 2024 What are CoFests!? What’s in a name: CollaborationFests! and Hackathons AnVIL Collection", " AnVIL CoFests! 2024 September 17, 2024 What are CoFests!? CollaborationFests!, also known as CoFests! (and sometimes as “hackathons”), are collaborative work events where we expand and improve the AnVIL community and the AnVIL ecosystem. Sometimes these gatherings are focused on AnVIL, and sometimes they are part of larger communities. Modified from https://galaxyproject.org/events/cofests What’s in a name: CollaborationFests! and Hackathons We collaborate. AnVIL collaborative events are emphatically called CollaborationFests! rather than Hackathons. Putting Collaboration in the name emphasizes what the events are about for us, and Fest communicates that they are fun events (which they are). “Hackathon” implies an emphasis on code. CoFests! are about contributing and learning how to contribute to all aspects of AnVIL, including training material, community infrastructure, documentation, unit tests, bug reports, and yes, even code. First and foremost AnVIL CoFests! are about growing the community of future contributors. Idea inspiration from [GCC2024][GCC2018] Reporting inspiration from [BioC2018][BioC2020][BioC2023] AnVIL Collection Please check out our full collection of AnVIL and related resources: https://hutchdatascience.org/AnVIL_Collection/ "],["organizer-guide.html", "Organizer Guide CoFests! Goals Logistics Example Schedule", " Organizer Guide The inaugural AnVIL Community Conference 2024 CoFests! will take place on November 12-13, 2024 in Cold Spring Harbor, NY. This event is a key event for professionals in the genomics community interested in biomedical and genomic cloud computing and takes place immediately before the sixth meeting on Biological Data Science. https://anvilproject.org/events/anvil2024-community-conference CoFests! Goals Build community Develop high interest topics Open science Logistics Parallel tracks, 5+ hours across Nov 12/13 Scientific Lead and Co-Lead ~4-10 participants per topic Example Schedule Problem statement (short demo) Brainstorming Onboarding Work-regroup, work-regroup Report out "],["scalable-ml-and-data-science.html", "Chapter 1 Scalable ML and Data Science", " Chapter 1 Scalable ML and Data Science "],["polygenic-risk-score-analysis.html", "Chapter 2 Polygenic Risk Score Analysis", " Chapter 2 Polygenic Risk Score Analysis "],["wrap-a-tool-with-wdl.html", "Chapter 3 Wrap a Tool with WDL", " Chapter 3 Wrap a Tool with WDL "],["about-the-authors.html", "About the Authors", " About the Authors These credits are based on our course contributors table guidelines.     Credits Names Pedagogy Lead Content Instructor(s) FirstName LastName Lecturer(s) (include chapter name/link in parentheses if only for specific chapters) - make new line if more than one chapter involved Delivered the course in some way - video or audio Content Author(s) (include chapter name/link in parentheses if only for specific chapters) - make new line if more than one chapter involved If any other authors besides lead instructor Content Contributor(s) (include section name/link in parentheses) - make new line if more than one section involved Wrote less than a chapter AnVIL instructions: Katherine Cox, Ava Hoffman, Elizabeth Humphries Content Editor(s)/Reviewer(s) Checked your content Content Director(s) Helped guide the content direction Content Consultants (include chapter name/link in parentheses or word “General”) - make new line if more than one chapter involved Gave high level advice on content AnVIL instructions: Allie Cliffe Acknowledgments Gave small assistance to content but not to the level of consulting Production Content Publisher(s) Helped with publishing platform Content Publishing Reviewer(s) Reviewed overall content and aesthetics on publishing platform Technical Course Publishing Engineer(s) Helped with the code for the technical aspects related to the specific course generation Template Publishing Engineers Candace Savonen, Carrie Wright Publishing Maintenance Engineer Candace Savonen Technical Publishing Stylists Carrie Wright, Candace Savonen Package Developers (ottrpal) John Muschelli, Candace Savonen, Carrie Wright Art and Design Illustrator(s) Created graphics for the course Figure Artist(s) Created figures/plots for course Videographer(s) Filmed videos Videography Editor(s) Edited film Audiographer(s) Recorded audio Audiography Editor(s) Edited audio recordings Funding Funder(s) Institution/individual who funded course including grant number Funding Staff Staff members who help with funding   ## ─ Session info ─────────────────────────────────────────────────────────────── ## setting value ## version R version 4.3.2 (2023-10-31) ## os Ubuntu 22.04.4 LTS ## system x86_64, linux-gnu ## ui X11 ## language (EN) ## collate en_US.UTF-8 ## ctype en_US.UTF-8 ## tz Etc/UTC ## date 2024-09-17 ## pandoc 3.1.1 @ /usr/local/bin/ (via rmarkdown) ## ## ─ Packages ─────────────────────────────────────────────────────────────────── ## package * version date (UTC) lib source ## bookdown 0.39.1 2024-06-11 [1] Github (rstudio/bookdown@f244cf1) ## bslib 0.6.1 2023-11-28 [1] RSPM (R 4.3.0) ## cachem 1.0.8 2023-05-01 [1] RSPM (R 4.3.0) ## cli 3.6.2 2023-12-11 [1] RSPM (R 4.3.0) ## devtools 2.4.5 2022-10-11 [1] RSPM (R 4.3.0) ## digest 0.6.34 2024-01-11 [1] RSPM (R 4.3.0) ## ellipsis 0.3.2 2021-04-29 [1] RSPM (R 4.3.0) ## evaluate 0.23 2023-11-01 [1] RSPM (R 4.3.0) ## fastmap 1.1.1 2023-02-24 [1] RSPM (R 4.3.0) ## fs 1.6.3 2023-07-20 [1] RSPM (R 4.3.0) ## glue 1.7.0 2024-01-09 [1] RSPM (R 4.3.0) ## htmltools 0.5.7 2023-11-03 [1] RSPM (R 4.3.0) ## htmlwidgets 1.6.4 2023-12-06 [1] RSPM (R 4.3.0) ## httpuv 1.6.14 2024-01-26 [1] RSPM (R 4.3.0) ## jquerylib 0.1.4 2021-04-26 [1] RSPM (R 4.3.0) ## jsonlite 1.8.8 2023-12-04 [1] RSPM (R 4.3.0) ## knitr 1.47.3 2024-06-11 [1] Github (yihui/knitr@e1edd34) ## later 1.3.2 2023-12-06 [1] RSPM (R 4.3.0) ## lifecycle 1.0.4 2023-11-07 [1] RSPM (R 4.3.0) ## magrittr 2.0.3 2022-03-30 [1] RSPM (R 4.3.0) ## memoise 2.0.1 2021-11-26 [1] RSPM (R 4.3.0) ## mime 0.12 2021-09-28 [1] RSPM (R 4.3.0) ## miniUI 0.1.1.1 2018-05-18 [1] RSPM (R 4.3.0) ## pkgbuild 1.4.3 2023-12-10 [1] RSPM (R 4.3.0) ## pkgload 1.3.4 2024-01-16 [1] RSPM (R 4.3.0) ## profvis 0.3.8 2023-05-02 [1] RSPM (R 4.3.0) ## promises 1.2.1 2023-08-10 [1] RSPM (R 4.3.0) ## purrr 1.0.2 2023-08-10 [1] RSPM (R 4.3.0) ## R6 2.5.1 2021-08-19 [1] RSPM (R 4.3.0) ## Rcpp 1.0.12 2024-01-09 [1] RSPM (R 4.3.0) ## remotes 2.4.2.1 2023-07-18 [1] RSPM (R 4.3.0) ## rlang 1.1.4 2024-06-04 [1] CRAN (R 4.3.2) ## rmarkdown 2.27.1 2024-06-11 [1] Github (rstudio/rmarkdown@e1c93a9) ## sass 0.4.8 2023-12-06 [1] RSPM (R 4.3.0) ## sessioninfo 1.2.2 2021-12-06 [1] RSPM (R 4.3.0) ## shiny 1.8.0 2023-11-17 [1] RSPM (R 4.3.0) ## stringi 1.8.3 2023-12-11 [1] RSPM (R 4.3.0) ## stringr 1.5.1 2023-11-14 [1] RSPM (R 4.3.0) ## urlchecker 1.0.1 2021-11-30 [1] RSPM (R 4.3.0) ## usethis 2.2.3 2024-02-19 [1] RSPM (R 4.3.0) ## vctrs 0.6.5 2023-12-01 [1] RSPM (R 4.3.0) ## xfun 0.44.4 2024-06-11 [1] Github (yihui/xfun@9da62cc) ## xtable 1.8-4 2019-04-21 [1] RSPM (R 4.3.0) ## yaml 2.3.8 2023-12-11 [1] RSPM (R 4.3.0) ## ## [1] /usr/local/lib/R/site-library ## [2] /usr/local/lib/R/library ## ## ────────────────────────────────────────────────────────────────────────────── "],["references.html", "Chapter 4 References", " Chapter 4 References "],["404.html", "Page not found", " Page not found The page you requested cannot be found (perhaps it was moved or renamed). You may want to try searching to find the page's new location, or use the table of contents to find the page you are looking for. "]] +[["index.html", "AnVIL CoFests! 2024 What are CoFests!? What’s in a name: CollaborationFests! and Hackathons AnVIL Collection", " AnVIL CoFests! 2024 September 18, 2024 What are CoFests!? CollaborationFests!, also known as CoFests! (and sometimes as “hackathons”), are collaborative work events where we expand and improve the AnVIL community and the AnVIL ecosystem. Sometimes these gatherings are focused on AnVIL, and sometimes they are part of larger communities. Modified from https://galaxyproject.org/events/cofests What’s in a name: CollaborationFests! and Hackathons We collaborate. AnVIL collaborative events are emphatically called CollaborationFests! rather than Hackathons. Putting Collaboration in the name emphasizes what the events are about for us, and Fest communicates that they are fun events (which they are). “Hackathon” implies an emphasis on code. CoFests! are about contributing and learning how to contribute to all aspects of AnVIL, including training material, community infrastructure, documentation, unit tests, bug reports, and yes, even code. First and foremost AnVIL CoFests! are about growing the community of future contributors. Idea inspiration from [GCC2024][GCC2018] Reporting inspiration from [BioC2018][BioC2020][BioC2023] AnVIL Collection Please check out our full collection of AnVIL and related resources: https://hutchdatascience.org/AnVIL_Collection/ "],["organizer-guide.html", "Organizer Guide CoFests! Goals Logistics Final Product / Report Out Example Schedule for a Track", " Organizer Guide The inaugural AnVIL Community Conference 2024 CoFests! will take place on November 12-13, 2024 in Cold Spring Harbor, NY. This event is a key event for professionals in the genomics community interested in biomedical and genomic cloud computing and takes place immediately before the sixth meeting on Biological Data Science. https://anvilproject.org/events/anvil2024-community-conference CoFests! Goals Build an inclusive community that is supportive of newcomers Contribute to open science Produce a final product that accomplishes one of the following for a topic Makes useful forward progress Identifies opportunities and boundaries or limitations Logistics 3 Parallel tracks, 5+ hours across Nov 12/13 Scalable Machine Learning and Data Science Polygenic Risk Score Analysis Wrap a Tool (+ Intro AnVIL/WDL) Scientific Lead and AnVIL Outreach co-Lead for support We expect 4-10 participants per track Prior to the CoFests, the scientific and AnVIL Outreach co-Leads will work together to enumerate some ideas for final products and post them publicly in this book. The AnVIL Outreach co-Lead will help add content to this guide, onboard newer AnVIL users to the platform, and provide guidance on the final product / report out. Final Product / Report Out The final product of CoFests doesn’t need to be code! These Collaboration Fests can support story-boarding future work or development of documentation or training materials. If it’s something that will help the community and make progress on an AnVIL associated topic and there’s sufficient interest, the idea is game! As Galaxy phrased it for their CoFests: [The goal of collaboration fests is to expand the ecosystem] Not just the code, but the whole ecosystem. That includes training, tools, best practice workflows, documentation, test cases, translations, infrastructure, and yes, even code. It helps us a lot if you can fill out some basic Report Out details. At the end of Day 2, your track will share a final report during the CoFest Recap Session! Example Schedule for a Track Day 1 (2.5 hours) Task Time & Lead Problem statement. Provide background info on the track’s overall topic and may include a brief summary of the pre-worked collaboration ideas. 20-30 minutes (Scientific Lead) Brainstorming. What project will the track tackle? Focus on understanding the participant backgrounds and skills and matching those with track ideas and actionable tasks to accomplish the goal. 15-30 minutes (Both) Onboarding. Handle billing accounts and other logistics necessary to accomplish the work. 30-60 minutes (AnVIL Outreach co-Lead) Work-regroup, work-regroup. Formal collaboration work time left before dinner. (Groups may choose to work together informally after dinner too) 30-60 minutes (N/A) Day 2 (3 hours) Task Time & Lead Work-regroup, work-regroup. Formal collaboration work time (with a coffee break). 2-2.5 hours (N/A) Construct a “report out”. The report out may be a Google doc, Google slides, a GitHub repository, a website, an OTTR book, etc. 30-60 minutes (AnVIL Outreach co-Lead) "],["scalable-ml-and-data-science.html", "Chapter 1 Scalable ML and Data Science", " Chapter 1 Scalable ML and Data Science "],["polygenic-risk-score-analysis.html", "Chapter 2 Polygenic Risk Score Analysis", " Chapter 2 Polygenic Risk Score Analysis "],["wrap-a-tool-with-wdl.html", "Chapter 3 Wrap a Tool with WDL", " Chapter 3 Wrap a Tool with WDL "],["about-the-authors.html", "About the Authors", " About the Authors These credits are based on our course contributors table guidelines.     Credits Names Pedagogy Lead Content Instructor(s) FirstName LastName Lecturer(s) (include chapter name/link in parentheses if only for specific chapters) - make new line if more than one chapter involved Delivered the course in some way - video or audio Content Author(s) (include chapter name/link in parentheses if only for specific chapters) - make new line if more than one chapter involved If any other authors besides lead instructor Content Contributor(s) (include section name/link in parentheses) - make new line if more than one section involved Wrote less than a chapter AnVIL instructions: Katherine Cox, Ava Hoffman, Elizabeth Humphries Content Editor(s)/Reviewer(s) Checked your content Content Director(s) Helped guide the content direction Content Consultants (include chapter name/link in parentheses or word “General”) - make new line if more than one chapter involved Gave high level advice on content AnVIL instructions: Allie Cliffe Acknowledgments Gave small assistance to content but not to the level of consulting Production Content Publisher(s) Helped with publishing platform Content Publishing Reviewer(s) Reviewed overall content and aesthetics on publishing platform Technical Course Publishing Engineer(s) Helped with the code for the technical aspects related to the specific course generation Template Publishing Engineers Candace Savonen, Carrie Wright Publishing Maintenance Engineer Candace Savonen Technical Publishing Stylists Carrie Wright, Candace Savonen Package Developers (ottrpal) John Muschelli, Candace Savonen, Carrie Wright Art and Design Illustrator(s) Created graphics for the course Figure Artist(s) Created figures/plots for course Videographer(s) Filmed videos Videography Editor(s) Edited film Audiographer(s) Recorded audio Audiography Editor(s) Edited audio recordings Funding Funder(s) Institution/individual who funded course including grant number Funding Staff Staff members who help with funding   ## ─ Session info ─────────────────────────────────────────────────────────────── ## setting value ## version R version 4.3.2 (2023-10-31) ## os Ubuntu 22.04.4 LTS ## system x86_64, linux-gnu ## ui X11 ## language (EN) ## collate en_US.UTF-8 ## ctype en_US.UTF-8 ## tz Etc/UTC ## date 2024-09-18 ## pandoc 3.1.1 @ /usr/local/bin/ (via rmarkdown) ## ## ─ Packages ─────────────────────────────────────────────────────────────────── ## package * version date (UTC) lib source ## bookdown 0.39.1 2024-06-11 [1] Github (rstudio/bookdown@f244cf1) ## bslib 0.6.1 2023-11-28 [1] RSPM (R 4.3.0) ## cachem 1.0.8 2023-05-01 [1] RSPM (R 4.3.0) ## cli 3.6.2 2023-12-11 [1] RSPM (R 4.3.0) ## devtools 2.4.5 2022-10-11 [1] RSPM (R 4.3.0) ## digest 0.6.34 2024-01-11 [1] RSPM (R 4.3.0) ## ellipsis 0.3.2 2021-04-29 [1] RSPM (R 4.3.0) ## evaluate 0.23 2023-11-01 [1] RSPM (R 4.3.0) ## fastmap 1.1.1 2023-02-24 [1] RSPM (R 4.3.0) ## fs 1.6.3 2023-07-20 [1] RSPM (R 4.3.0) ## glue 1.7.0 2024-01-09 [1] RSPM (R 4.3.0) ## htmltools 0.5.7 2023-11-03 [1] RSPM (R 4.3.0) ## htmlwidgets 1.6.4 2023-12-06 [1] RSPM (R 4.3.0) ## httpuv 1.6.14 2024-01-26 [1] RSPM (R 4.3.0) ## jquerylib 0.1.4 2021-04-26 [1] RSPM (R 4.3.0) ## jsonlite 1.8.8 2023-12-04 [1] RSPM (R 4.3.0) ## knitr 1.47.3 2024-06-11 [1] Github (yihui/knitr@e1edd34) ## later 1.3.2 2023-12-06 [1] RSPM (R 4.3.0) ## lifecycle 1.0.4 2023-11-07 [1] RSPM (R 4.3.0) ## magrittr 2.0.3 2022-03-30 [1] RSPM (R 4.3.0) ## memoise 2.0.1 2021-11-26 [1] RSPM (R 4.3.0) ## mime 0.12 2021-09-28 [1] RSPM (R 4.3.0) ## miniUI 0.1.1.1 2018-05-18 [1] RSPM (R 4.3.0) ## pkgbuild 1.4.3 2023-12-10 [1] RSPM (R 4.3.0) ## pkgload 1.3.4 2024-01-16 [1] RSPM (R 4.3.0) ## profvis 0.3.8 2023-05-02 [1] RSPM (R 4.3.0) ## promises 1.2.1 2023-08-10 [1] RSPM (R 4.3.0) ## purrr 1.0.2 2023-08-10 [1] RSPM (R 4.3.0) ## R6 2.5.1 2021-08-19 [1] RSPM (R 4.3.0) ## Rcpp 1.0.12 2024-01-09 [1] RSPM (R 4.3.0) ## remotes 2.4.2.1 2023-07-18 [1] RSPM (R 4.3.0) ## rlang 1.1.4 2024-06-04 [1] CRAN (R 4.3.2) ## rmarkdown 2.27.1 2024-06-11 [1] Github (rstudio/rmarkdown@e1c93a9) ## sass 0.4.8 2023-12-06 [1] RSPM (R 4.3.0) ## sessioninfo 1.2.2 2021-12-06 [1] RSPM (R 4.3.0) ## shiny 1.8.0 2023-11-17 [1] RSPM (R 4.3.0) ## stringi 1.8.3 2023-12-11 [1] RSPM (R 4.3.0) ## stringr 1.5.1 2023-11-14 [1] RSPM (R 4.3.0) ## urlchecker 1.0.1 2021-11-30 [1] RSPM (R 4.3.0) ## usethis 2.2.3 2024-02-19 [1] RSPM (R 4.3.0) ## vctrs 0.6.5 2023-12-01 [1] RSPM (R 4.3.0) ## xfun 0.44.4 2024-06-11 [1] Github (yihui/xfun@9da62cc) ## xtable 1.8-4 2019-04-21 [1] RSPM (R 4.3.0) ## yaml 2.3.8 2023-12-11 [1] RSPM (R 4.3.0) ## ## [1] /usr/local/lib/R/site-library ## [2] /usr/local/lib/R/library ## ## ────────────────────────────────────────────────────────────────────────────── "],["references.html", "Chapter 4 References", " Chapter 4 References "],["404.html", "Page not found", " Page not found The page you requested cannot be found (perhaps it was moved or renamed). You may want to try searching to find the page's new location, or use the table of contents to find the page you are looking for. "]] diff --git a/docs/wrap-a-tool-with-wdl.html b/docs/wrap-a-tool-with-wdl.html index 57e540a..a25b98c 100644 --- a/docs/wrap-a-tool-with-wdl.html +++ b/docs/wrap-a-tool-with-wdl.html @@ -22,7 +22,7 @@ - + @@ -87,7 +87,10 @@
  • What are CoFests!?
    • -
  • Organizer Guide
    • +
  • Organizer Guide +
  • Topics
  • 1 Scalable ML and Data Science
  • 2 Polygenic Risk Score Analysis
    • diff --git a/organizer-guide.Rmd b/organizer-guide.Rmd index e326936..d88947d 100644 --- a/organizer-guide.Rmd +++ b/organizer-guide.Rmd @@ -10,39 +10,45 @@ The inaugural AnVIL Community Conference (ACC) 2024 will take place on November - Makes useful forward progress - Identifies opportunities and boundaries or limitations -## Final Product {-} - -The final product of CoFests doesn't need to be code! These Collaboration Fests can support story-boarding future work or development of documentation or training materials. If it's something that will help the community and make progress on an AnVIL associated topic and there's sufficient interest, the idea is game! [As Galaxy phrased it for their CoFests:](https://galaxyproject.org/events/gcc2023/cofest/#goals) - -> [The goal of collaboration fests is to expand the ecosystem] Not just the code, but the whole ecosystem. That includes training, tools, best practice workflows, documentation, test cases, translations, infrastructure, and yes, even code. - -Prior to the CoFests, the scientific and AnVIL co-leads will work together to enumerate some ideas for final products and post them publicly in this book. - ## Logistics {- .unlisted} - 3 Parallel tracks, 5+ hours across Nov 12/13 - Scalable Machine Learning and Data Science - Polygenic Risk Score Analysis - Wrap a Tool (+ Intro AnVIL/WDL) -- Scientific Lead and AnVIL Outreach Co-Lead for support +- Scientific Lead and AnVIL Outreach co-Lead for support - We expect 4-10 participants per track -## Example Schedule for a Track {- .unlisted} +Prior to the CoFests, the scientific and AnVIL Outreach co-Leads will work together to enumerate some ideas for final products and post them publicly in this book. + +::: {.notice} +The AnVIL Outreach co-Lead will help add content to this guide, onboard newer AnVIL users to the platform, and provide guidance on the final product / report out. +::: -### Day 1 (2.5 hrs scheduled) +## Final Product / Report Out {-} + +The final product of CoFests doesn't need to be code! These Collaboration Fests can support story-boarding future work or development of documentation or training materials. If it's something that will help the community and make progress on an AnVIL associated topic and there's sufficient interest, the idea is game! [As Galaxy phrased it for their CoFests:](https://galaxyproject.org/events/gcc2023/cofest/#goals) + +> [The goal of collaboration fests is to expand the ecosystem] Not just the code, but the whole ecosystem. That includes training, tools, best practice workflows, documentation, test cases, translations, infrastructure, and yes, even code. + +::: {.notice} +It helps us a lot if you can fill out some basic [Report Out details](https://docs.google.com/document/d/1wLK88p_tY6L-a8IF5dIe7gmDlJC1RxeU8_pm1ClU2IE/edit?usp=sharing). At the end of Day 2, your track will **share a final report during the CoFest Recap Session**! +::: + +## Example Schedule for a Track {- .unlisted} -| Task | Suggested time | Lead | Description | -|:-------------------------:|:---------------|:----------------------|:------------| -| Problem statement | 20-30 minutes | Scientific Lead | Provide background info on the track's overall topic and may include a brief summary of the pre-worked collaboration ideas.| -| Brainstorming | 15-30 minutes | Both | What project will the track tackle? Focus on understanding the participant backgrounds and skills and matching those with track ideas and actionable tasks to accomplish the goal. | -| Onboarding | 30-60 minutes | AnVIL Outreach Co-lead| Handle billing accounts and other logistics necessary to accomplish the work | -| Work-regroup, work-regroup| 30-60 minutes | -- | Formal collaboration work time left before dinner. (Groups may choose to work together informally after dinner too) | +### Day 1 (2.5 hours) {-} -### Day 2 (3 hrs scheduled) +| Task | Time & Lead | +|:-------------------------:|:-----------:| +| **Problem statement.** Provide background info on the track's overall topic and may include a brief summary of the pre-worked collaboration ideas. | 20-30 minutes (Scientific Lead) | +| **Brainstorming.** What project will the track tackle? Focus on understanding the participant backgrounds and skills and matching those with track ideas and actionable tasks to accomplish the goal. | 15-30 minutes (Both) | +| **Onboarding.** Handle billing accounts and other logistics necessary to accomplish the work. | 30-60 minutes (AnVIL Outreach co-Lead) | +| **Work-regroup, work-regroup.** Formal collaboration work time left before dinner. (Groups may choose to work together informally after dinner too) | 30-60 minutes (N/A) | -| Task | Suggested time | Lead | Description | -|:-------------------------:|:---------------|:----------------------|:------------| -| Work-regroup, work-regroup| 2 - 2.5 hrs | -- | Formal collaboration work time (with a coffee break) | -| Construct a "report out" | 30 - 60 minutes| AnVIL Outreach Co-lead| The report out may be a Google doc, Google slides, a GitHub repository, [a website](https://github.com/jhudsl/OTTR_Template_Website), an [OTTR book](https://github.com/jhudsl/OTTR_Template), etc.| +### Day 2 (3 hours) {-} -End of Day 2: Share final report during the CoFest Recap Session! +| Task | Time & Lead | +|:-------------------------:|:------------| +| **Work-regroup, work-regroup.** Formal collaboration work time (with a coffee break). | 2-2.5 hours (N/A) | +| **Construct a "report out".** The report out may be a Google doc, Google slides, a GitHub repository, [a website](https://github.com/jhudsl/OTTR_Template_Website), an [OTTR book](https://github.com/jhudsl/OTTR_Template), etc. | 30-60 minutes (AnVIL Outreach co-Lead) |