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

All RU (relative usage) values are 1 #7

Open
matdoering opened this issue Jul 29, 2021 · 1 comment
Open

All RU (relative usage) values are 1 #7

matdoering opened this issue Jul 29, 2021 · 1 comment

Comments

@matdoering
Copy link

Running the recommended workflow with STAR, all RU values end up being 1 using custom data. Implementing the transcriptome re-alignment in addition to the genome alignment unfortunately didn't change things.

Investigating the source code, I found that the reason for RU's being 1 is that there is only always a single segment:

write_output_cp_left(o3, gene, this_seg, n=nsamples, ind=ind, ru=1)

Any ideas on how to fix that?

@matdoering
Copy link
Author

matdoering commented Aug 17, 2021

Setting the param --winsize of mountainclimberCP to a lower value (e.g. 10) seems to help but that leads to other issues, namely:

Traceback (most recent call last):
  File "/mountainClimberCP.py", line 1396, in <module>
    main(sys.argv[1:])
  File "/mountainClimberCP.py", line 1113, in main
    peak_inds_ttest_opt = param2cpopt[(denoise_winsize_opt, amp_thresh_opt, peak_min_dist_opt)].tolist()
KeyError: (10, 0.15, 50)

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

1 participant