-
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
Atom trajectories 'blow up' at times #31
Comments
ajkerr0
referenced
this issue
Jun 16, 2016
Make the necessary changes for 'correct' displacement calculations, which were addressed in #30. The problem was in the integration. Keep the new code in 'greens_func.py' while the old method is kept in 'greens_func_old.py'. Add functionality to plot the displacements of every atom simultaneously. Delete 'elementwise_gf.py' as that existed to test the construction of arrays by doing so element-wise which ended up not being the problem in the end.
The spikes seem to be very localized in time when you look at longer time ranges, different parameters such as driving frequency, etc. |
ajkerr0
changed the title
Atom trajectories 'blow up' at large times
Atom trajectories 'blow up' at times
Jun 16, 2016
The 'blow up' nature of the solutions seem to go away (or at least some of them) if you increase the resolution/sample size of the integrals. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In particular when 6 member chain is driven at the end by a cosine force of angular frequency 1.5: the displacements get huge around 200 time units. There are also amplitudes near 100 time units that don't seem to be present in Dr. Mullen's plots, an indication that things are to blow up at later t?
Maybe this is an indication that my calculation isn't totally correct (seems to be closer to correct than before). Maybe this frequency is a resonant frequency that moves the chain large distances since the chain isn't 'tied down'? Could try adding a small potential to one of the inner atoms.
The text was updated successfully, but these errors were encountered: