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

CITE-seq R1 length issue #194

Open
Rimanpreet1 opened this issue Aug 28, 2024 · 11 comments
Open

CITE-seq R1 length issue #194

Rimanpreet1 opened this issue Aug 28, 2024 · 11 comments

Comments

@Rimanpreet1
Copy link

Hi,
I am trying to analyse raw 10X genomics sequence data on it, using the following code on HPC cluster but it is keep giving me an error and it seems it stops
-R1 SC98_R1_001.fastq.gz
-R2 SC98R2_001.fastq.gz
-t tags.csv
-cbf 1
-cbl 16
-umif 17
-umil 26
-cells 6000

error "[WARNING] Read1 length is 150bp but you are using 26bp for Cell and UMI barcodes combined.
This might lead to wrong cell attribution and skewed umi counts."
could you please help me with this

@Hoohm
Copy link
Owner

Hoohm commented Aug 28, 2024

Hello @Rimanpreet1
this is just a warning, you can ignore it.
You say it stops, what's the error you get?

@Rimanpreet1
Copy link
Author

Rimanpreet1 commented Aug 28, 2024 via email

@Rimanpreet1
Copy link
Author

Rimanpreet1 commented Aug 29, 2024 via email

@Hoohm
Copy link
Owner

Hoohm commented Aug 29, 2024

I think screenshots don't follow if you answer by email. Could you post them directly in the issue or copy paste the text?

@Rimanpreet1
Copy link
Author

Rimanpreet1 commented Sep 2, 2024 via email

@Hoohm
Copy link
Owner

Hoohm commented Sep 5, 2024

It might be a memory limitation issue. Can you show me the command you used to run it?

@Rimanpreet1
Copy link
Author

Rimanpreet1 commented Sep 5, 2024 via email

@Hoohm
Copy link
Owner

Hoohm commented Sep 11, 2024

How many reads are there?

The main way you can change the amount of memory used is by reducing the number of threads. But you might be reaching the maximum memory per thread.

I'm not really sure.

Could you try to test out a beta branch? It's completely rewritten in polars and is using the lazy API, it might solve your memory issue.

beta branch

@Rimanpreet1
Copy link
Author

Rimanpreet1 commented Sep 18, 2024 via email

@Rimanpreet1
Copy link
Author

Rimanpreet1 commented Sep 18, 2024 via email

@Hoohm
Copy link
Owner

Hoohm commented Sep 20, 2024

Something is weird.

Can you try to run only 1M reads?
Maybe it's a temp path issue, CSC needs to write data to disk, maybe it doesn't have access on the cluster?

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

2 participants