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

Wrong sample names in OutputPerSample #69

Open
JustinePa opened this issue Jun 26, 2024 · 5 comments
Open

Wrong sample names in OutputPerSample #69

JustinePa opened this issue Jun 26, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@JustinePa
Copy link

JustinePa commented Jun 26, 2024

Hi!

When checking "outputPerSample", for some of my samples the accession numbers are correct in the file names, but in the file itself it's another accession number. See an example below with files for ERR4914067.
This ERR number does not appear inside these files, but ERR4914068 and ERR4914071 do. "profile_ERR4914067.csv" even has 3 ERR numbers including two ERR4914068.

profile_ERR4914067.csv
Relative_Abundance_ERR4914067.csv
Richness_ERR4914067.csv
All_Cumulative_ERR4914067.csv

Additionally, ERR4614067 does not appear in the final table. Maybe it could be related to what I described above.

Thanks for your input!

@hariszaf hariszaf added the bug Something isn't working label Jun 26, 2024
@hariszaf
Copy link
Owner

Please attach your parameters.tsv file.

@JustinePa
Copy link
Author

@hariszaf
Copy link
Owner

hariszaf commented Jun 26, 2024

This is a v.2.1.4. related issue.
I am not sure whether it still applies in v.2.1.5; it is my belief it is now fixed at least for a number of gene-preprocess-clustering combinations.
@savvas-paragkamian and @cpavloud have tested v.2.1.5 in some cases, could you share any insight ?
In my tests, the files are as they are supposed to.

@JustinePa
Copy link
Author

JustinePa commented Jun 26, 2024

Do you know what might be creating this?

I am still using v.2.1.4 as I am using LifeWatch services that only have this version for now. So is there anything specific I have to look out for?

@hariszaf
Copy link
Owner

I would have to check and this is a bad time for me to work on this..
One should have to check the postAssignment module.
I will be able to do that from September.
I suggest you discuss with the LW people we you decide to work with v.2.1.5 and fix everything once.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants