-
Notifications
You must be signed in to change notification settings - Fork 4
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
Pytorch requirement #10
Comments
Can you remove such restriction? I couldn't install the older version of the Pytorch. |
Hi @maohub2008 , sorry for this issue. I will update the code soon. |
Thanks. I manually removed the restrictions from your source code. It worked well. I am using Pytorch 2.3.1 and CUDA 12.0. There are no compatibility issues. Just some suggestions. Your method is a great tool. Since I am new to the bioinformatics world, more explanation in your tutorial will be very helpful for new birds like me. That will help the adoption of your CEFCON greatly. For example, on the R code portion: If you can explain temp_R_dir and how to set it up on the user's computer, that will be very helpful. You also didn't set the values for start_cluster and end_cluster in your sample code. Thanks. |
In your sample code, you mentioned that "Here, we directly use the trajectory information obtained from Beeline, and then call the R script in python to obtain differential expression information of genes along each trajectory." But in your code, I didn't see the Beeline was used. Can you explain it more? That will be very helpful, potentially in your tutorial too. Thanks. |
We used Beeline's benchmarking datasets, including the provided trajectory information, and we didn't call beeline's interface. Thank you very much for your suggestions, I submitted some updates including the addition of new help information, I will be refining more help information! For the current help on how to use it please refer to the jupyter notebook files. |
The pytorch >1.13.1 <2.0 is no longer available for downloading. I couldn't install the v0.1.0. Do you still have such restriction for your version 2.0?
The text was updated successfully, but these errors were encountered: