On Feb 4, 8:47 am, Rad <
rad.b...@arl.army.mil> wrote:
> Teo,
>
> It is still not printing the pressure/stress tensor. I pulled out a
rad,
please check the files that are created. stress is by default
written to file and not to the regular output.
> copy of cp2k from the cvs respository (not the nightly build) and
> compiled it for the run. When will the nightly build with the updated
> version be available?
why don't you create your own nightly builds? or on-demand builds?
just create a small script and have it executed through cron.
here is what i run (manually) to update and compile on my desktop.
executables for production are then copied over from the exe/
directory (after testing them ok).
#!/bin/sh
PATH=${HOME}/bin:${PATH}
export PATH
cvs update -d
pushd makefiles
make ARCH=Linux-x86-64-intel popt
make ARCH=Linux-x86-64-intel sopt
make ARCH=Linux-x86-64-intel ssgl
make ARCH=Linux-x86-64-g95 sopt
make ARCH=Linux-x86-64-g95 ssgl
make ARCH=Linux-x86-64-g95 sdbg
make ARCH=Linux-x86-64-intel leap2fist
make ARCH=Linux-x86-64-intel fes
popd
test exe/Linux-x86-64-intel/cp2k.popt -nt ChangeLog && perl ./tools/
cvs2cl.pl -b
> Is there a way I can quickly look at the code (for specifice code
> changes) to make sure that I am working with the correct version that
a very useful tool to follow the changes in a cvs archive is 'cvsps'.
it creates "changesets" from cvs commits and you can easily generate
diffs for those changesets. very useful to see what people are doing.
cheers,
axel.