You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could save that in the pepatac/examples/test_project/ folder as, for example, test_config_refgenie2.yaml. Then from the parent pepatac/ direcotry run as: looper run examples/test_project/test_config_refgenie2.yaml. Be aware that in the current released version the prealignments flag is now prealignment_names due to the fact that the pipeline no longer explicitly requires refgenie, although that is still our recommended usage.
For mouse data, yes the mouse_chrM2x genome is the mitochondrial equivalent. We don't currently have a standard mouse repeat or satellite genome hosted on refgenie. If you had something local you wished to use in this context, we could walk you through the process of building a refgenie asset locally to represent the "mouse_repeats" type genome that you could then include.
Hi,
Previous version of PEPATAC pipeline denoted both rCRSd and human_repeats as prealignments.
prealignments
:['rCRSd', 'human_repeats']
as we can see from the following example.
http://pepatac.databio.org/en/latest/files/examples/tutorial/results_pipeline/tutorial2/PEPATAC_log.txt
However, the tutorial of the latest version only notes about rCRSd as shown here.
http://pepatac.databio.org/en/latest/run-container/
What should I do with human repeats?
I would appreciate it if you could let me know:
Example code to pull from refgenie.
How to designate human repeats when running pepatac.py.
Also, I would appreciate it if you could clarify what would be the mm10 counterpart for rCRSd and human_repeats.
(Is mouse_chrm2x sufficient?)
Finally, pypline version of example code is 0.9.6.
I think it would be helpful to every one if you could renew or also upload the example for Pipeline version: 0.10.0.
http://pepatac.databio.org/en/latest/files/examples/tutorial/results_pipeline/tutorial2/PEPATAC_log.txt
I'm a fan of this pipeline and I really appreciate your help.
Best regards,
Hiroyuki
The text was updated successfully, but these errors were encountered: