Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project organization #9

Open
k8hertweck opened this issue Mar 18, 2021 · 1 comment
Open

Project organization #9

k8hertweck opened this issue Mar 18, 2021 · 1 comment

Comments

@k8hertweck
Copy link
Contributor

Data in /shared/biodata/example_data

What are recommendations for:

  • primary data storage? with SR? copy to own folders?
  • large intermediate data files (SAM, BAM, etc)?

What type of directory structure to model for pre-processed files?

@k8hertweck
Copy link
Contributor Author

k8hertweck commented Mar 29, 2021

Primary (raw) data storage: fastq

  • stays in original location (path) as shared by SR
  • read-only
  • unaligned -> project name (user/pool) -> gzipped sample, per read and sample
  • create variable to reference?
  • group permissions determined by lab

Reference data: shared biodata

  • genomic data
  • indexes

Metadata:

Output: files sent to scratch, instructions to copy to home (default on rhino) or fast?

  • one directory per sample, including alignment file and logs

  • raw_data_qc

  • trimmed_data

  • trimmed_data_qc

  • mapped_reads (BAM): retain alignment, renaming file to view in IGV (and logs)

  • mapped_qc, across all samples, plots and samtools output

  • counts files: individual (richly annotated), and combined (fewer annotations)

Suggested structure from HBC:

rnaseq
├── logs
├── meta
├── raw_data
├── results
└── scripts

Structure used by Data Carpentry, modified for RNAseq:

  • dc_workshop
    • data
      • untrimmed_fastq
      • trimmed_fastq
    • results
      • sam
      • bam
      • counts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant