Not only do the things that you mention do that, but also things like salads :(. Trying to lose weight with IBS can be a PITA
238 karma · joined April 28, 2012
Not only do the things that you mention do that, but also things like salads :(. Trying to lose weight with IBS can be a PITA
edit: Nevermind I found a few. When I looked for this a few years ago I just kept hitting dead ends.
I kind of wish I could find a good way to make Fortran and C play nicely together. (There are some compiler dependent peculiarities that I have encountered that make it difficult.)
Fortran's intrisics and file handling capabilities make it indispensable in the work I do.... So it is really a love hate relationship.
After reading the comments on C and the difficulties the author had in the compilation process.... All I can say is Garbage in garbage out. I have worked in the HPC enviornment for a number of years using both Fortrash and C. The errors the author encountered would have been avoided by someone with any experience developing large softwares. I learned these things after working on my first project and now they barely, if at all, factor into my development time. Make sure you build and keep a dependency graph while you are developing and this becomes a non issue.
Equation 7 bears a striking resemblance to what you would get if you started with a Liouville vonNeumann equation and tried to solve it in time. Infact all of the equations seem to follow this path.
See for example the books: 1) Charge and energy transfer dynamics in Molecular systems by Volkhard May and Oliver Kuhn (chapter 2)
2) Chemical Dynamics in Condensed Phases by Abraham NItzan.
I find it a bit surprising to not see these in the reference material. Everything in this paper screams Liouville von-Neuman equation.
I do think they can add more complexity in other areas hough.
Also performance of fortran code is quite dependent on the compiler and compiler options. Somethng that was not well described.
http://unriskinsight.blogspot.co.at/2014/05/the-f-word-of-pr...
I can quantify a little slow with a specific research experience. This isn't the case for all uses of Quantum Espresso, etc....
When I run an HSE or PBE0 calculation on 192 atoms it takes just over 2 weeks of computation time using quantum espresso. When my co-worker did it in vasp using the same computing systems it took just a couple of days. I don't really know the reason for this.
From time to time things like this creep up.
One of the quirks you should be aware of an enforce in all runs where this is relevant is you need to set
wf_collect=.true.
if you do not then each subsequent run will require the same number of processors in the same configuration each time the program is run.
http://www.quantum-espresso.org/wp-content/uploads/Doc/INPUT...
I can tell you that it tends to be a little slow compared to some other codes such as VASP, and it does tend to take up a good deal more disk space. It has a few other quirks but it is a great program. Also its wavefunctions can be exported to XML files.
If you are looking anytime soon for people with computational physics/chemistry specific knowledge I may be looking for work soon.