Monday, 27 April 2009

More staggered code

I am starting to add all the staggered code that we have
lying around in various sub-directories. I have just checked
in the code, written by Chris Richards, to do variational
smearing of the scalar channel.

I will first add the new code for heavy-light mesons
that is used by HPQCD. I will then add the binary readers
system that the ex-Liverpool group added to inline_spectrum.h,
because of the IO problems on one machine.

Thursday, 26 March 2009

Staggered documentation

I have made a start at documenting part of the staggered fermion code in Chroma.

Tuesday, 24 March 2009

Start of FAQ

I have started the FAQ page with some information about how to print the gauge field to the standard output.

NEWS in text

Now that I look at the Chroma source, Robert has been using the NEWS text file to report on the new developments in Chroma. This of course works, and is fine, but is not as buzz word compliant as blogging.

Richard Stallman complains when people put their data on the cloud. We need a way to keep hold of the information in this blog. I think this is possible.

Sunday, 22 March 2009

Large Nc

I have added the basic note on using Chroma with Nc <> 3 to the community documentation pages

Why we started this BLOG.

This BLOG has been created to document the development
of the Chroma lattice QCD library. In the past this type of
information was circulated using the email lists. One disadvantage
of email lists is that it is hard to find information in
your INBOX. The BLOG keeps all the information in one place.
To keep up to date with recent posts you can use the RSS feed of this BLOG.
The motivation for this BLOG was based on reading the
Scotgrid on Fire blog.

In the addition to this BLOG, there is also a wiki like area where documentation can be added. The user documentation site is hosted by google, so this should be easier to register
with. (Of course this means that google could be spying on your
work with chroma, well who knows perhaps you will get a targeted
advert about running code on the google cloud.)

Another way to keep up to date with the additional code
going into Chroma is to check the CVS commit logs. Just in case this BLOG doesn't get updated regularly.