Is your feature request related to a problem? Please describe
Cellranger modules that rename the files check that the filenames are identical except for R1/R2. Public data can often have non-standard naming, e.g. from SRA. The only way to work around this is to rename the source files, which can be untenable, particularly with large files in cloud storage.
Describe the solution you'd like
I propose a new boolean flag (default false) that, when set, skips this check. This maintains the validation logic which presumably keeps the user from mismatching files, but allows flexibility for non-standard data that should actually circumvent the logic.
Describe alternatives you've considered
The only way to work around this is to rename the source files, which can be untenable, particularly with large files in cloud storage. You can skip renaming (for cellranger multi, not for cellranger count), but this causes issue downstream with cellranger.
Additional context
No response
Is your feature request related to a problem? Please describe
Cellranger modules that rename the files check that the filenames are identical except for R1/R2. Public data can often have non-standard naming, e.g. from SRA. The only way to work around this is to rename the source files, which can be untenable, particularly with large files in cloud storage.
Describe the solution you'd like
I propose a new boolean flag (default false) that, when set, skips this check. This maintains the validation logic which presumably keeps the user from mismatching files, but allows flexibility for non-standard data that should actually circumvent the logic.
Describe alternatives you've considered
The only way to work around this is to rename the source files, which can be untenable, particularly with large files in cloud storage. You can skip renaming (for cellranger multi, not for cellranger count), but this causes issue downstream with cellranger.
Additional context
No response