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

Inquiry about monitoring the trajectory of attach-pull-release method. #209

Open
bowensha-tudelft opened this issue Jan 2, 2025 · 8 comments

Comments

@bowensha-tudelft
Copy link

As the title mentions, I cannot find any trajectory generated by paprika. I hope I can see the trajectory of the process so that I can be sure that the method is correctly implemented. Could you please tell me where I can look into for more details?

@jset231
Copy link

jset231 commented Jan 2, 2025

@bowensha-tudelft Can you give us more info on your code to run the simulations with paprika. Are you using Amber or OpenMM? When you say there is no trajectory, do you mean no files are generated?

@bowensha-tudelft
Copy link
Author

@bowensha-tudelft Can you give us more info on your code to run the simulations with paprika. Are you using Amber or OpenMM? When you say there is no trajectory, do you mean no files are generated?

I am using AMBER. There are some files in complex/ and windows/. But I do not have any idea about which one contains information of trajectory.

@jset231
Copy link

jset231 commented Jan 2, 2025

@bowensha-tudelft in those folders there should be subfolders like a000, a001 for the attach phase and p000, p001 for the pull phase. These folders will contain all of the trajectories (if AMBER ran properly). Can you find these in the directory?

@bowensha-tudelft
Copy link
Author

@bowensha-tudelft in those folders there should be subfolders like a000, a001 for the attach phase and p000, p001 for the pull phase. These folders will contain all of the trajectories (if AMBER ran properly). Can you find these in the directory?

image

Yes, I can find them. Above are files in it.

@jset231
Copy link

jset231 commented Jan 2, 2025

Awesome. The *.nc files are the AMBER trajectories you can load into a visualization software like VMD.

@bowensha-tudelft
Copy link
Author

Awesome. The *.nc files are the AMBER trajectories you can load into a visualization software like VMD.

Thank you so much! AMBER is really new to me. Your suggestions are strongly useful.

@bowensha-tudelft
Copy link
Author

Awesome. The *.nc files are the AMBER trajectories you can load into a visualization software like VMD.

Sorry, @jset231 . I am confused with loading the trajectory. Below is what I did.

File - New Molecule - Filename: bcd-hex-dum.prmtop
Load Data Into Molecule - Filename: production.nc & Determine file type: AMBER Coordinates

Nothing shows on my VMD windows but VMD gives this message:

image

@jaketanderson
Copy link
Collaborator

@bowensha-tudelft if you provide the specific prmtop and nc files here, I can try opening them on my own VMD. That could help us narrow the issue down to VMD plugin issues or issues with the files themselves.

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

3 participants