-
Notifications
You must be signed in to change notification settings - Fork 9
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
how to use DESSO to my own data? #1
Comments
Hi Yaoyong, Based on your email and this github issue, I would like to clarify more details as follows: (2) We have the trained models for the 690 ChIP-seq datasets. However, each model is trained specifically for each dataset, so it may not very make sense to identify motifs from your own data by using predict.py. My suggestion is to train a new CNN model for a new dataset then make predictions. Feel free to let me know if you might have any other concerns. Thanks. |
Dear DESSO Developers, thank you very much for the rapid and comprehensive responses to my question. I am looking forward to the codes which I can use to apply DESSO to our own ChIP-seq data. Best regards, Yaoyong |
@Wang-Cankun Cankun, have you finished the code test? |
Hi @yaoyong02 @Wang-Cankun finishes the code test and provides the tutorial for how to apply DESSO to your own ChIP-seq data. Please let as know if you might need additional help. Thanks. |
Dear DESSO Developers,
my name is Yaoyong Li. I have been reading your paper about DESSO and have also downloaded the software. Your method looks promising. I would like to apply it to our ChIP-seq data. However, I am not sure how I can apply the software to my own data, because I could see any option for the user's own data as some input in either train.py or predict.py, two main python scripts in DESSO. In another word, I suppose that the input should be a list of DNA sequences obtained from the peaks of my ChIP-seq data, and I wonder how I could give the list of DNA sequence to the software.
Best regards,
Yaoyong
The text was updated successfully, but these errors were encountered: