-
Notifications
You must be signed in to change notification settings - Fork 19
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
Request for guidance on running ISiCLE locally without Cascade and obtaining NMR chemical shifts #7
Comments
I second this. It would be great if you could provide some documentation on how to obtain the chemical shifts using ISiCLE. |
I also hope for this please. The examples seem very out of date and it is otherwise unclear how to use this package to obtain NMR chemical shifts |
Thank you all for your interest in ISiCLE. As you've intuited, the NMR workflow from Yesiltepe et al. was the first ISiCLE prototype, which indeed was tailored to our institutional computing resource Cascade. We have since created a CCS workflow that is resource-agnostic, but the NMR code was not updated. More recently, we have been working on "ISiCLE 2.0", a much improved Python API and collection of workflows that will unify all currently supported property prediction functionality (NMR, CCS, and infrared). This version, while very much in a beta state, currently resides on the master branch. Our resident NMR workflow expert will be providing the necessary updates to make the latest NMR workflow more accessible. I believe is almost ready to push to GitHub. Your patience is appreciated! |
Hi all, thanks for your patience. I have updated our ReadTheDocs with a how-to on shift calculations https://isicle.readthedocs.io/en/latest/user_guide/NMR.html. If you're interested in a a couple small molecules this should be enough for you to run via jupyter notebook or python script on your local machine. I've also added workflows for automating the process, both on your local machine or on your slurm scheduler. Pull the new changes from the github and find them at workflows/shielding/nextflow-*. These require NextFlow which must be installed separately but its fairly simple to do. https://www.nextflow.io/docs/latest/getstarted.html Let us know if you have more questions! |
Hi @amyjystad , Thanks a lot for updating and the instructions. When I try to run the NMR notebook with a given molecule I am getting the following error, could you kindly let me know what is going wrong here?
|
Per the last line RuntimeError, the output file either could not be found or is empty. Check to see if the file exists at all by opening up |
I investigated the dimethylglycine.out file and found it to be empty. Additionally, I checked the crest --help command in the isicle conda environment, and it seems that CREST is installed correctly:
I've performed the following steps to troubleshoot the issue:
However, despite these efforts, the problem persists. The dimethylglycine.out file remains empty. Please advise on further steps for resolution. |
Hi Zaid, thanks for the additional information. We are working on trying to reproduce your error and will get back to you as soon as we can. |
I am seeking assistance in using ISiCLE on a local server without relying on Cascade and obtaining NMR chemical shifts directly. My goal is to provide molecular structures to ISiCLE and retrieve the corresponding chemical shifts. While exploring the examples folder, I noticed the following comment in the nmr_chemical_shifts.py file:
Convert to shifts
TODO: implement shielding to shifts conversion
I have the following queries and requests:
Running ISiCLE Locally: I would like guidance on how to use ISiCLE on a local server without needing to utilize Cascade. This would involve bypassing the Cascade credentials prompt and resolving the host name error mentioned in my previous issue.
Obtaining NMR Chemical Shifts: Could you please provide instructions or tutorials on how to use ISiCLE to obtain NMR chemical shifts directly from molecular structures? If possible, I would appreciate guidance on how to do it.
The text was updated successfully, but these errors were encountered: