Development Procedure

This page outlines the basic steps one should take when adding a new development to the AstroBEAR code.

Test Your Changes

First, you'll want the newest revision of AstroBEAR. You could either make a new repository via hg clone or pull the newest changeset into your current repository:

hg clone ssh://<username>@clover.pas.rochester.edu//data/repositories/scrambler_devel astrobear

OR

hg pull ssh://<username>@clover.pas.rochester.edu//data/repositories/scrambler_devel

Then make any desired or necessary changes, and compile your problem. Now run it, and check the output. If it still works, then you will want to commit these changes to your local repository. If you added new files that you want to be included you will need to do hg add before hg ci:

hg add <filename(s)>
hg ci -m "comments"

If it did not work, you will have to go back and check everything you have changed, fix it, recompile, rerun, and recheck. If everything works and you have committed your changes, it is time to test the rest of the code with the test suite.

Run the Test Suite

This part needs to be run in bluehive. First, you will want to clone or pull your local changeset into bluehive. Next, you run the buildtests script from your astrobear directory:

./buildtests.s

Make sure the tests completed successfully by looking in the out directory: scratch/afrank_group If the tests were successful, you can push your changeset into the development repository:

hg push ssh://<username>@clover.pas.rochester.edu//data/repositories/scrambler_devel

If the tests were not successful, you will have to begin a debugging procedure.

Summary