Please read the notes below before installing the patches.
1. A rudimentary deskew correction patch to the program 'roi' in roi_pac. Copy the routines to $ROI_PAC/roi, go to your build (compilation) directory, and type 'make'. You might need to go through 'make clean', 'make' . Then copy the program roi to your $INT_BIN (cp roi $INT_BIN/.).
2. Code to run MAI with ROI_PAC: each of the routines in the archive is either new or intended to replace the ROI_PAC routine with the same name. The 'installer' script is intended to copy the relevant files, and will attempt to compile the code if the relevant makefiles are accessible (assuming you compiled ROI_PAC more or less manually; usually not the case, so read on).
You will need to compile the roi deskew correction – follow directions in 1 above.
The easiest way to compile the thing is to go to ROI_PAC's compilation directory (one of the compilations that finished successfully, say $ROI_PAC/multibuild-******-****/gfortran64-g/), and there:
mkdir roi_mai
cp -rf roi/* roi_mai/.
cd roi_mai
Edit the Makefile to change the end of the relevant paths (say srcdir and VPATH) from /roi to /roi_mai
make
cp roi $ROI_PAC/roi_mai /roi_mai
- Problems: if make complains about not finding second.Po, make sure the .deps directory is present (ls -la roi_mai/.deps/second.Po), if not – copy it manually. (cp -r ../roi/.deps .). then make again.
Another problem is *.o files in either the build directory ($ROI_PAC/multibuild-******-****/<compilation name>) or the $ROI_PAC/roi directory. \rm *.o, then go back to the build directory and 'make' again.
If the fortran routines don't compile, add the flag -ffixed-line-length-none and try again. The full compilation commands for then are:
gfortran -ffixed-line-length-none diffigram.f -o diffigram
gfortran -ffixed-line-length-none translate.f norm.f dot.f -o translate
(though translation should be more precise using roi_pac's make_los.pl, but I haven't got to automate that one yet).
Thanks to Matt Pritchard, Christelle Wautier and Andy Hooper for testing and comments. Please e-mail me (nbechor at chandler.mit.edu) with bugs/corrections and improvements you might have.