http://www.noao.edu/staff/mighell/crblaster


The CRBLASTER paper has been published in the October 2010 edition of PASP:

Mighell, K. J. 2010, PASP, 122, 1236-1245




crblaster.tar.gz

Build instructions:

0) Retrieve the compressed source tar ball:

http://www.noao.edu/staff/mighell/crblaster/crblaster.tar.gz

1) Uncompress the tar ball:

gunzip crblaster.tar.gz

2) Unpack the tar ball:

tar -xvf crblaster.tar

3) Go to the crblaster directory:

cd crblaster

4) Make CFITSIO with the following command:

make cfitsio

5) Assuming that MPI is installed *and* you have access to the MPI command mpicc,
make crblaster with the following command:

make

6) You should new see an exectuable file called

crblaster

in the directory, by typing the following command:

ls -l crblaster

If the executable is *not* there, an error like the following should appear:

ls: crblaster: No such file or directory

7) If you have made it this far, it is likely that you have successfully built CRBLASTER.

But let us make sure...

********** VALIDATION INSTRUCTIONS **********

Let us check and see if the compiled program gives expected results.

Please do the following 4 validation checks:

1) CRBLASTER reads an input FITS image called

in.fits

and writes an output FITS file called

out.fits

Type the following commands:

cp images/in_750x750.fits in.fits

./crblaster

When done, compare the output file (out.fits) with the gold standard in the images directory:

diff out.fits images/out_750x750_1x1.fits

If no differences are found, then your CRBLASTER is validated with this image!

The input and output FITS files may be viewed with any FITS image display.
I recommend ds9 from the Smithsonian Astrophysical Observatory which is
currently available at the following website:

http://hea-www.harvard.edu/RD/ds9/

2) Assuming that you have the MPI run command mpirun,
execute CRBLASTER on 2 processors by typing the following commands:

rm out.fits

mpirun -np 2 ./crblaster 1 1 2

If CRBLASTER gave you this error:

CFITSIO: failed to create new file (already exists?):
CFITSIO: out.fits

it means that you did not delete the existing out.fits file (which is required).

When done, compare the output file with the gold standard in the images directory:

diff out.fits images/out_750x750_1x2.fits

If no differences are found, then your CRBLASTER is validated with this image!

By the way, this command partitioned the input image into 2 horizontal subimages of equal area.

3) Execute CRBLASTER on 2 processors by typing the following commands:

rm out.fits

mpirun -np 2 ./crblaster 1 2 1

When done, compare the output file with the gold standard in the images directory:

diff out.fits images/out_750x750_2x1.fits

If no differences are found, then your CRBLASTER is validated with this image!

By the way, this command partitioned the input image into 2 vertical subimages of equal area.

4) Finally, execute CRBLASTER on 4 processors by typing the following commands:

rm out.fits

mpirun -np 4 ./crblaster 1 2 2

If it crashed, then you might have erroneously typed

mpirun -np 2 ./crblaster 1 2 2

which tells CRBLASTER that you are using 2 processors (-np 2)
but you want to use 4 subimages: ./crblaster 1 2 2

NOTA BENE: *** CRBLASTER uses one process(or) per subimage ****

When CRBLASTER is done, compare the output file with the gold standard in the images directory:

diff out.fits images/out_750x750_2x2.fits

If no differences are found, then your CRBLASTER is validated with this image!

By the way, this command partitioned the input image into 4 square subimages of equal area.

If you have found no differences with all of these gold standards,
then you have successfully validated your CRBLASTER exectuable!



03/23/2011@14:08MST