Installing the Standard Fortran Release

The first task is to elect one person at your site to be the local software librarian, whose job it is to install new versions of SNOMAN. If you are the only person at your site to be working on this then congratulations; you just got the job!

The version n_nnnn (e.g. 5_0185) of SNOMAN lives on:-

surf.sno.laurentian.ca

in directory:-

/usr/local/snomanftp/snoman/tar/n_nnnn.tar.gz

A valid login name and password will be sent to any member of SNO who asks, just send email to:-

n.west1@physics.oxford.ac.uk

That directory also contains:-

starter_kit.tar.gz

Start by taking a copy of that, unwinding the tar file and reading:-

starter_kit/tools/install.doc

Please note:-

The tools to build and support a local copy of the SNO database are NOT provided as part of the SNOMAN release.

To get the database support software, contact:-

Bruce Cleveland (bclevela@surf.sno.laurentian.ca)

Note that you must have at least version 99, and preferably 2000, of CERNlib before attempting to install the database. A stripped down version of the database is available at:-

snoguest@surf.sno.laurentian.ca:snoman/tar/dbs_lite.tar.gz

which is suitable for laptop development work. See the README file it contains for instructions.

If you want to use the C++ extension (see section 3.1.2) additional external libraries will be needed.

SNOMAN comes complete with a set of tools that should work on all supported platforms. There is no obligation on the part of the local librarian to use them if they would prefer to develop their own, in which case the tools can be used for guidance. In this case the librarian should provide his/her own versions of the following:-

install_snoman.scr   Pass code through EXTRACT,                                                    compile and link.   


compile_snoman.scr 		 Compile SNOMAN and create library.  


link_snoman.scr 		 Create SNOMAN.EXE.                  


link_snolib.scr 		 Link user code against the library. 


update_library.scr 		 Update library if necessary.        

The following environmental variables are essential if using the standard tools, and even if not, confer benefit, so should be defined for your group of users:-

SNO_ROOT    The directory path to the snoman directory 


e.g. /user/smith                           


SNO_SNOMAN_VER 		  The current version e.g. "2_07"           


SNO_TOOLS 		  The directory holding tools including EXTRACT 


e.g. /user/smith/snoman/tools/exe

After having linked and run the program you may wish to increase or decrease the size of the dynamic memory. To change this, edit the file:-

define_memory_size.for

and update as required. Then recompile it, update the library and rebuild SNOMAN. Note: it is no longer necessary to recompile the entire source. You may find that linking fails because the program is too large, if so reduce the size of the dynamic memory.

If you switch on array index checking you should be aware that ZEBRA plays trick to allow it to gain access at execution time to user supplied COMMONs and that index checking may give spurious errors if turned on in ZEBRA.