Problems in KORSAR are defined and solved in a flexible topology architecture. This topology allows calculation of different reactor plant configurations with no need to recompile the code on different computers.
Input data are coded with the DLC language (Data Language for Codes) specially designed for KORSAR.
The KORSAR input file, kordat, is a text file written as program in DLC language according to user defined problem nodalization. The file contains a set of procedures for describing connections between elements and single-valuedness conditions for each nodalization element. The procedures are grouped as follows:
- Layout – setting of connections between nodalization elements;
- Data – setting of nodalization element specification data;
- Output – generation of output list (for recording to the result file);
- Event – modeling of control algorithms, assignment of disturbances, and declaration of parameters by varying combinations of values typical for each element. The user is provided with a wide set of built-in functions and statements for programing complicated calculation and parameter control algorithms.
The KORSAR code has a capability to terminate a problem, record the problem states to korsav state saving file, and restart from any state record. The record mode is selected by the user in the input file.
Calculation output is recorded in binary form to korres file. A service program, kutil2.exe utility, is provided in the code for presenting results in text from (parameter tables). It is also used for obtaining reference data and supplemental information. Settings for the utility are made in text form in DLC in the utility input file, kutdat.
The KORSAR code operates as follows. Type kordat in text editor. The kordat file is used to make settings for korsar.exe. program. After the problem is started, the program looks for syntactic and semantic errors. The korsar.exe program prints problem listing and error messages to the korlis listing file that is generated each time the program starts. If no errors are detected, the problem solution starts and the user requested output is written to korres result file.
After korsar.exe program execution is completed, the kutil2.exe utility is activated to extract simulation output from korres file and present it in text form in kutlis listing file. The utility is set in kutdat text file where names of result files with output data can be selected. The amount of data presented in kutlis cannot be larger than the amount of data in korres.
Problem restart form any state record in korsav file is determined by the record number in kordat file. The list of state records can be viewed using kutil2.exe. utility.
The nwsp_dat file with tabular data of water and steam properties is generated once during the code installation and used further without changes .
- KORSAR/V3 Code – User Manual. – NITI, 2019.