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

Inferring expected files from sample names is just awful #93

Closed
ressy opened this issue Aug 26, 2020 · 0 comments · Fixed by #94
Closed

Inferring expected files from sample names is just awful #93

ressy opened this issue Aug 26, 2020 · 0 comments · Fixed by #94
Labels
enhancement New feature or request
Milestone

Comments

@ressy
Copy link
Member

ressy commented Aug 26, 2020

Since there isn't a straightforward mapping of sample names to file names, different Illumina programs do that name conversion differently, and duplicate sample names are allowed, we need to switch to using sample numbers and existing files on disk rather than trying to figure out what the files should be named. This can be done internally in the illumina package to start with, with minimal visible changes, before switching the project metadata to be sample-number-based. This change is a first step toward addressing #50.

@ressy ressy added the enhancement New feature or request label Aug 26, 2020
@ressy ressy added this to the Version 0.0.4 milestone Aug 26, 2020
ressy added a commit that referenced this issue Aug 26, 2020
New expected behaior: sample_files_for_num is gone and only
sample_paths_for_num should be used instead; missing filenames are
missing in sample_paths_from_num output rather than present but
nonexistent on disk; filename are loaded only during refresh() rather
than in the filename functions.
ressy added a commit that referenced this issue Aug 26, 2020
Switch from predicting filenames from sample sheet information to
parsing it from the fastq.gz files actually on disk.  The information is
loaded during refresh() rather than in the filename functions.
@ressy ressy closed this as completed in #94 Aug 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant