GUISDAP version 1.65 installation guide   If you are using GUISDAP version m160 you only need to copy the source update guisdap165.tar.Z New users should copy the test data files and some binary input files as well as the mex file sources: GUP_matfiles.tar.Z GUP_mex152sources.tar.Z GUISDAP version 1.65 contains the source files for CP1K and for ESR test experiments gup0 and gup1. Two versions of gup0 are included, the original having four 360 us pulses (experiment gup00) and the modified one having the last pulse cut (experiment gup0). To install other experiments, the corresponding tar-file needs to be copied. A list of experiments supported by GUISDAP is found here Here are the steps to make GUISDAP work ======================================= 1) put the files to the directory where you want GUISDAP directory to be created Uncompress the files and use tar to get the original files To run GUISDAP, it is then necessary to have the following directories created. Some of these may appear automatically when you expand the tar files, but unless that happens, make sure they exist anyway (/home/aft/askoh/ is my path to GUISDAP, that will be different, of course) /home/aft/askoh/guisdap/m165/ /home/aft/askoh/guisdap/m165KST/ /home/aft/askoh/guisdap/m165ESR/ /home/aft/askoh/guisdap/m165gr/ /home/aft/askoh/guisdap/exps/ /home/aft/askoh/guisdap/exps/CP1K/ /home/aft/askoh/guisdap/exps/gup0/ /home/aft/askoh/guisdap/exps/gup00/ /home/aft/askoh/guisdap/exps/gup1/ /home/aft/askoh/guisdap/matfiles/ /home/aft/askoh/guisdap/garbage/ % Only for Windows and Macintosh users, % In Unix, the temporary files are directed to $TMPDIR % if such environment variable is defined. During the installation and experiment initialization one must have write access to the experiment directories. The GUISDAP users need only read access to the GUISDAP directories except to the directory specified by variable 'path_tmp' in start_GUP.m. 2) Define the paths edit the path names in start_GUP.m so that GUISDAP is able to load and save files My path definition is the following: path_GUP='/home/aft/askoh/guisdap/'; The two other path definitions are created automatically (unless otherwise wanted): path_exps points to the experiment directories path_tmp points to a temporary disk area, if the environment variable TMPDIR exists. Otherwise (especially for Windows and Macintosh) path_tmp will point to directory guisdap/garbage. 3) Create the matlabpath - add path to xxx/guisdap/m165 to your matlabpath - add path to xxx/guisdap/m165KST to your matlabpath - add path to xxx/guisdap/m165gr to your matlabpath 4) start matlab and issue command 'fullinit' and see whether GUISDAP works 5) say 'CP1K_demo1' to see that data analysis works 6) after that you may edit fullinit.m to initialize CP1K remotes. Then run CP1K_remotedemo. 7) Test the design package by typing at the command prompt start_GUP;name_expr='gup0';name_site='L';design;init_GUP The source files for the ESR test experiments gup0 and gup1 are included in the release . gup00 is the original one, having four 360 us pulses, run in March 1996. - gup0 is the modified one, in which the last pulse is cut to 150 us. 8) If you have access to some ESR test data, you can test the analysis by first removing m165KST from the matlab path and adding m165ESR to it. 9) You can increase the executions speed by installing the mex-files (see README in the mex152sources directory). Remember to add the mex-directory into the matlab-path so that it preceded the m165 directory. Then Matlab will find the mex-files before the m-file versions. Remember to use the -V4 compatibility option when compiling the mex sources Recompilation may not be necessary, because the Matlab 4 mex-files may work as such (they work at SGI, slowly though). 10) If you wish to use EISCAT raw data files, you need Nigel Wade's integration package. The source code is available by anonymous ftp at ion.le.ac.uk. Please contact Nigel Wade for more details (nmw@ionospheric-physics.leicester.ac.uk). GUISDAP 1.65 is tested with integration package version 1.3 Happy GUPping PS. In case of error, use diary to get the output to a file and send the file to one of the following addresses: Asko Huuskonen Markku Lehtinen Juha Pirttilä Pekka Hiitola 8 January 1999 Maildrop for comments and suggestions pekka.hiitola@oulu.fi   [GUISDAP versions 1.6x] [GUISDAP versions 2.x] [Documentation] [Experiments] [giveme] [post integration]