Giter VIP home page Giter VIP logo

r-genomics's Introduction

R Genomics

This is a repository for Data Carpentry R Genomics lessons

r-genomics's People

Contributors

alexgraehl avatar apawlik avatar benmarwick avatar earlew avatar efran avatar emhart avatar fmichonneau avatar hlapp avatar k8hertweck avatar karawoo avatar kariljordan avatar karthik avatar kwhall avatar leej3 avatar mistrm82 avatar mkuzak avatar naupaka avatar orchid00 avatar plijnzaad avatar ryanjw avatar sarahsupp avatar smcclatchy avatar tracykteal avatar wligtenberg avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

r-genomics's Issues

overall idea for R-genomics lesson

Have a metadata file with all the clones.
sample
generatin
clade strain cit run genome_size
Read in that file.
Look at it with str and summary.
Talk about factors.
Deal with NAs somehow, maybe where citrate level unknown?
Do some summary statistics with genome size.
Filter on citrate status or on generation.
Mutate unit conversion with genome size
Group by citrate status and then look at genome size as related to status
Plot average genome size by citrate status, or by generation
Could do a t-test for genome size by citrate status

Then after dplyr lesson move on working with the SNP calling data. That info is in another file.
Read in that file then join the SNP file with the metadata file with an inner_join

Read in SNP file
Look at that file
Stitch them together with inner_join
inner_join
https://cran.r-project.org/web/packages/dplyr/dplyr.pdf
https://stat545-ubc.github.io/bit001_dplyr-cheatsheet.html

Then use inspiration from Ryan's R_visualization lesson and do things with the SNP calls.

  • look at number of SNPs per clone
  • average and sd the number of SNPs for each citrate type
  • ggplot averages and sd
    exercise: how would you do this for generation number?

multivariate analysis showing how close they are to each other

Re-synchronize with upstream

I have now injected the history from R-ecology, resolved merge conflicts, and merged your development into the main Data Carpentry repo. Before continuing development in this fork, please ensure that you update from upstream. If you do this, it necessarily won't be a fast-forward. Alternatively, delete the fork and fork again for a clean start, though see below.

I see that you have open issues in your fork's tracker (#1 and #2); if these are still current, could you please move them to the main repo so we have a central place to track issues with the lesson?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.