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.

Sign up for GitHub

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

Jump to bottom

MirTrace Report for each sample instead of multi-sample report #205

Closed
apeltzer opened this issue Dec 2, 2022 · 3 comments
Closed

MirTrace Report for each sample instead of multi-sample report #205

apeltzer opened this issue Dec 2, 2022 · 3 comments
Labels
bug Something isn't working

Comments

@apeltzer
Copy link
Member

apeltzer commented Dec 2, 2022

Description of the bug

Previous versions of smrnaseq had a single report of MirTrace that covered all samples in one report. This is not the case anymore since newer versions but should be changed back to what it was.

Command used and terminal output

No response

Relevant files

No response

System information

No response
@apeltzer apeltzer added the bug Something isn't working label Dec 2, 2022
@apeltzer apeltzer added this to the Release 2.1.1 Patch milestone Dec 2, 2022
@apeltzer
Copy link
Member Author

apeltzer commented Dec 2, 2022

image

Checked between 2.0.0 and 2.1.0 --> this is likely the reason for the current behaviour. We might have to consider to use mirtrace differently here then....?

@apeltzer
Copy link
Member Author

apeltzer commented Dec 2, 2022

Fix for mirtrace report PR opened - #211

@apeltzer
Copy link
Member Author

apeltzer commented Dec 2, 2022

Fixed in #211

@apeltzer apeltzer closed this as completed Dec 2, 2022
nschcolnicov pushed a commit that referenced this issue Oct 10, 2024
@atrigila
Merge pull request #205 from atrigila/fix_path_schema
52a1b14 
fix schema format path
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@apeltzer