|
|
|
|
Cloudy is under constant development, with a new build occurring almost every day. Every night a Perl script checks whether the code has been rebuilt and runs the auto test suite if it has. The source, data, and test suite are copied to the "last" directory beneath this ftp site at 9PM US East Coast time, before these tests are computed. If the test suite ran perfectly (no botched asserts or crashes) then the source, data, and test suite files are copied to the "last_good" directory on the same ftp site. If serious problems occurred then a summary of the problems are copied to the "last" directory and "last_good" is not updated. Both directories will have a file named "problems.txt", a list of all occurrences of the string PROBLEM in the test suite output, and a file named "errors.txt", which lists all serious errors (crashes or botched asserts). The file errors.txt will be empty in the "last_good" directory. The distribution files have the same format in both last and last_good. Data, source, and the test suite are in files that start with the names "data", "source", and "tsuite". The test suite is divided into two parts, the "auto", run every night, and "slow", which runs over three days. Versions with Unix end of lines are located in tar'd and g'zipped files (their names end in "tar.gz"), and versions with Windows end of lines are located in zip files. There are no instructions for setting up these versions of the code. The directions for the current gold version or most recent beta are probably valid. This page is here for two reasons. First, Cloudy is totally open source - there are no hidden or private versions of the code. This page shows where things were yesterday. Second, this is the best way to allow collaborators to access the latest version of the code (this is the real reason it is here). New! We have moved the project to a subversion repository here. It is still available by ftp. NB The code in these directories is in a totally undefined state. There may be extra print statements for debugging, physical processes may be disabled, or new trial processes introduced. It probably will not reformat your hard drive. This is not meant for the faint of heart.
|
