appdeTMe (1158396)
Текст из файла
11
Keldysh Institute for Applied Mathematics
Russian Academy of Sciences
Advanced parallel program development environment
(APPDE)
Technical manual
(Installation guide)
December, 1999
Contents
1 DVM-system installation under Windows95/NT 3
1.1 System installation 3
1.2 DVM-system verification 5
1.3 Demonstration program run 5
1.4 Problems arising during DVM-system installation 6
1.4.1 Device is not ready 6
1.4.2 Not enough memory for environment variables 6
2 DVM-system installation under UNIX 7
2.1 System installation 7
2.2 DVM-system verification 9
2.3 Demonstration program run 9
2.4 DVM-program run on several workstations 10
3 NORMA-compiler installation under Windows95/98/NT 10
3.1 NORMA-compiler installation 10
3.2 NORMA-compiler verification 11
4 NORMA-compiler installation under UNIX 11
4.1 NORMA-compiler installation 11
4.2 NORMA-compiler verification 11
1DVM-system installation under Windows95/NT
1.1System installation
DVM-system requirements:
-
operation system Windows95/NT;
-
Microsoft Visual C++ 5.0 version and later (4.0 version can be used with some restrictions, see below);
-
Microsoft Fortran PS 4.0 or Digital Fortran 5.0 and later. (For programs in Fortran-DVM language);
-
MPICHWIN - MPI message passing library for Windows95/NT;
-
WINZIP – standard Windows utility to unpack files.
To install DVM-system the following steps should be done:
-
Select or create a directory for MPI library (for example, MPICHWIN), copy to it and unpack mpichwin.zip.
As a result the following folders and files will be created:
| include\ | - include-files; |
For the installation of new version of DVM-system this step can be skipped (if not stated otherwise in the instruction).
-
Select or create a directory for given (NNN-th) version of DVM system (for example, DVM_NNN);
-
Copy to it required files from the following list
dvm_sys.tar.gz
dvmUSRrhtm.tar.gz
dvmSYSrhtm.tar.gz
dvmUSRehtm.tar.gz
dvmSYSehtm.tar.gz- DVM-system;
- user documentation in Russian;
- system documentation in Russian;
- user documentation in English;
- system documentation in English. -
Unpack dvm_sys.tar.gz file.
As a result the following folders and files will be created:
| dvm_sys | ||
| cdvm\ | - C-DVM converter | |
| driver\ | - DVM-system tools | |
| examples\ | - demonstration programs | |
| fdvm\ | - Fortran-DVM converter | |
| pppa\ | - DVM-program performance analizer | |
| predictor\ | - DVM-program performance predictor | |
| rts\ | - DVM-program support system | |
| copyright | - copyright information | |
| dvmclean* | - programs to delete intermediate files | |
| dvmcleanall* | - DVM-system uninstall programs | |
| dvminstall* | - DVM-system uninstall programs | |
| makefile* | - installation and uninstallation support system files |
-
Unpack one or several documentation files; and as result, additional directory dvm_sys\doc will appear.
-
In dvminstall.bat file:
-
correct SETVARSVC variable, which define the full name of the program setting environment variables for С (С++) similary to the example, given in the file;
-
to work with Fortran-DVM programs correct SETVARSFTN variable, which define the full name of the program setting environment variables for Fortran;
-
the parameters for above programs can be defined in ARGSETVARSVC and ARGSETVARSFTN variables respectively;
-
if you do not need Fortran you should comment out SETVARSFTN и ARGSETVARSFTN settings;
-
correct the parameters specifying required compilers (variables CC, CXX, FORT, LINKER, MAKE) and MPICH library version (variables MPI_HOME, MPI_LIB, MPI_INC).
Note 1. If neither SETVARSVC nor SETVARSFTN is defined, the paths to the programs are taken from autoexec.bat.
Note 2. Predictor requires C++ compiler of standard ISO/IEC14882 “Standard for the C++ programming language”, ratified in August 1998. For example compilers Microsoft Visual C 5.0 and later, GNU C++ 2.8.1 version and later etc. Predictor can not be used with Microsoft Visual 4.0 compiler, you can exclude predictor by commenting out three lines in dvm_sys\makefile.win:
@cd predictor.
@$ (MAKE) ………….all
@cd ..
If you need predictor you can use DVM-system delivered as a set of libraries and executable files.
Attention!!! DVM-system 3.04 and later versions require MPI library renewing (see 1.).
-
In the directory dvm_sys run command:
dvminstall.bat
On successful execution message:
“DVM-system is successfully installed”
will be output and the following folders will be created in dvm_sys
directory:
| bin\ | - DVM-system executable files; |
| lib\ | - support system library; |
On errors examine logfile.txt files appeared in \src subdirectories of rts, cdvm, fdvm, driver, pppa, predictor directories.
-
DVM-system is ready for use!
Now the user should copy all files from directory dvm_sys/user to his own directory with DVM programs.
1.2DVM-system verification
To verify correctness of DVM system installation it is recommended to run standard test procedures for two variants of Jacobi program in C-DVM (jac1.cdv) and Fortran-DVM languages (jac.fdv) (if Fortran was installed). You should run
alltest.bat
from dvm_sys\demo directory.
This command will do the following:
-
starts standard testing procedure which execute both programs in different debugging modes (see below);
-
compares results of the program execution with standard results supplied with the system in files jacc_res.win, jacf_res.win;
-
starts predictor (of DVM-program performance) for jac1.cdv and compares the predicted results with standard results supplied with the system in file prd_res.win;
Names of each steps and results of comparison are displayed for the user at screen. After successful execution of each step the user can interrupt (Ctrl+C) or continue (any key) the test execution. In case of error the test will stop.
On successful execution of all the steps the user will see the message:
… end of testing DVM …
It means that DVM-system has been installed correctly and either demonstration or user programs can be executed.
If results are not identical to standard at any step it is necessary to check correctness of performing all steps of the instruction. Detailed information about DVM-program startup modes, used by test procedures and all diagnostics messages are in the following documents:
-
"Debugging DVM-program. User guide";
-
“C-DVM compiler. User guide”;
-
“Fortran-DVM compiler. User guide”.
1.3Demonstration program run
Directory dvm_sys\demo contains set of C-DVM and Fortran-DVM programs that show capabilities of DVM-system. In the directory the user can also find batch files:
| alldemo.bat | that start up the standard procedure of all C-DVM and Fortran-DVM demonstration program testing; |
| allсdemo.bat | that start up the standard procedure of C-DVM demonstration program testing. |
By default demonstration program execution results are saved in demo.1 and democ.1 files respectively. After execution the user can compare the results of demonstration program execution on user computer system with standard results from demo_res.win and democ_res.win in the same directory. Comparison can be made by command:
fc demo.1 demo_res.win
fc demoс.1 demoс_res.win
On successful execution each of demonstration program output into demo.1 and democ.1 files special message.
If case of demonstration program execution error:
-
demonstration program output into screen:
-
errors of standard testing procedure execution errors (during testing process);
-
!!!ERROR!!! of test<имя_теста> after testing completion;
-
the prompt is displayed and the user can interrupt (Ctrl+C) or continue (any key) the demonstration program execution;
-
one or several of the following files will be created:
| <program name>.edb | - dynamic control error; |
In this case and if DVM-system verification finished successfully before that (point 1.2) the user should ask for system programmer support.
1.4Problems arising during DVM-system installation
1.4.1Device is not ready
If during installation after the message:
Setting environment for Micrsoft Visual C++ tools
you see the message:
Device is not ready: disk <name of CD_ROM>
it means that Microsoft Visual C++ attempt to read CD_ROM. In file:
…\Program Files\DevStudio\VC\bin\vcvars32.bat
user should comment out or delete the string:
set vcsource=D:\DEVSTUDIO
and start up DVM-system installation once more.
1.4.2Not enough memory for environment variables
It is possible that during the first installation or while executing DVM-program you will see the following message:
« Not enough memory for environment variables»
There are three ways to increase the memory (2304 –is minimal memory size for DVM-system environment variables):
-
in file config.sys you can correct the string:
Shell=command.com /E:2304 /P
and then restart your computer;
-
if you use Far Manager to run your program, set window properties as follows:
Properties Memory Initial environment = 2304
and restart Far Manager
(after restarting computer Far Manager saves these properties);
-
if you run any .bat-file from Explorer , set window properties as follows:
PropertiesMemoryInitial environment = 2304
The first method is preferable as it is sufficient to do only once.
2DVM-system installation under UNIX
2.1System installation
DVM-system requirements:
-
any UNIX- like operating system;
-
cc compiler;
-
f77 compiler;
-
c++ compiler;
-
compiler gcc (c++) - version 2.8.1 and later;
-
MPICH library;
-
make utility;
-
ar utility;
-
gunzip, tar utility to unpack files.
To install DVM-system the following steps should be done.
-
Select or create a directory for given (NNN-th) version of DVM system (for example, DVM_NNN)
-
Copy to it required files from the following list
dvm_sys.tar.gz
dvmUSRrhtm.tar.gz
dvmSYSrhtm.tar.gz
dvmUSRehtm.tar.gz
dvmSYSehtm.tar.gz- DVM-system;
- user documentation in Russian;
- system documentation in Russian;
- user documentation in English;
- system documentation in English. -
Unpack dvm_sys.tar.gz file. For example run:
gunzip -c dvm_sys.tar | tar xf -
As a result the following folders and files will be created:
| dvm_sys | ||
| cdvm\ | - C-DVM converter | |
| driver\ | - DVM-system tools | |
| examples\ | - demonstration programs | |
| fdvm\ | - Fortran-DVM converter | |
| pppa\ | - DVM-program performance analizer | |
| predictor\ | - DVM-program performance predictor | |
| rts\ | - DVM-program support system | |
| copyright | - copyright information | |
| dvmclean* | - programs to delete intermediate files | |
| dvmcleanall* | - DVM-system uninstall programs | |
| dvminstall* | - DVM-system uninstall programs | |
| makefile* | - installation and uninstallation support system files |
-
Similary unpack one or several documentation files; and as result, additional directory dvm_sys\doc will appear.
-
In dvminstall file:
-
correct parameters specifying required compilers (variables CC, CXX, FORT) and MPICH library version (variables MPI_HOME, MPI_LIB, MPI_INC).
-
assign to the platform variable platform name from the list in the string:
### set platform (SGI_ws, MVS1000_m, MVS1000_r, GNU ...)
then CC, CXX, FORT variables will be corrected for each platform in accordance with examples from dvminstall file.
-
In the directory dvm_sys run command:
dvminstall
On successful execution message:
“DVM-system is successfully installed”
Характеристики
Тип файла документ
Документы такого типа открываются такими программами, как Microsoft Office Word на компьютерах Windows, Apple Pages на компьютерах Mac, Open Office - бесплатная альтернатива на различных платформах, в том числе Linux. Наиболее простым и современным решением будут Google документы, так как открываются онлайн без скачивания прямо в браузере на любой платформе. Существуют российские качественные аналоги, например от Яндекса.
Будьте внимательны на мобильных устройствах, так как там используются упрощённый функционал даже в официальном приложении от Microsoft, поэтому для просмотра скачивайте PDF-версию. А если нужно редактировать файл, то используйте оригинальный файл.
Файлы такого типа обычно разбиты на страницы, а текст может быть форматированным (жирный, курсив, выбор шрифта, таблицы и т.п.), а также в него можно добавлять изображения. Формат идеально подходит для рефератов, докладов и РПЗ курсовых проектов, которые необходимо распечатать. Кстати перед печатью также сохраняйте файл в PDF, так как принтер может начудить со шрифтами.















