Systems Code Modules: (by LCC) There are 2 main steps of the systems code: input files with user-specified parameters are called (fixed parameters) Physics – “inpar” and (scanned parameters). The plasmas that remain satisfy the power and “inpar2” particle balance and are described by 55 parameters. This output file becomes the input file for the engineering module. is the name of the code that computes “sysplas_PC.F” these parameters and is a look-up table that gives the calculation of the radiative “corona” cooling rates and other relevant parameters of impurities in the plasma. at this step, are 4 different modules, each with a different blanket Engineering – design. COE is also calculated here. These modules are very similar with only slight differences between them. benchmark model with new (Aug 2009) costing accounts ARIES-AT – dual-coolant lead-lithium blanket without manifold DCLL – with manifold (not used often) DCLL_M – next-step version with a silicon-carbide blanket SiC – 2. Engineering: are required to run the engineering module. They are called by the certain subroutines during the engineering module: called by geometry.cpp, contains constants and assumptions of the magnets – called by costingaccount.cpp, input parameters that are used to define costing accounts – and COE called by designpoint.cpp, constants provided by Rene Raffray, very similar between – SiC and DCLL blankets called by aries.cpp, contains the output database from the physics module consisting of – 55 plasma parameters is unique only to the DCLL case and includes a detailed inboard, outboard and divertor – build of the blanket. This is read by the Aries.cpp program are 5 subroutines of code in the engineering module under the main program “Aries.cpp”: main program – does unit costing analysis with specific material costs – goes through detailed costing for every account – also be known as flow,” computes powers, heat fluxes, pumping, CD, etc – “power computes the geometries of the machine, as well as magnets – makes output parts under – “/OutputParts” And 5 corresponding header files. These call various lines in the appropriate .cpp code: Cost.h, CostingAccount.h, DesignPoint.h, Geometry.h, Part.h
Systems Code Modules: (by LCC) There are 2 main steps of the systems code: Physics – input files with user-specified parameters are called “inpar” (fixed parameters) and “inpar2” (scanned parameters). The plasmas that remain satisfy the power and particle balance and are described by 55 parameters. This output file becomes the input file for the engineering module. “sysplas_PC.F” is the name of the code that computes these parameters and “corona” is a look-up table that gives the calculation of the radiative cooling rates and other relevant parameters of impurities in the plasma. Engineering – at this step, are 4 different modules, each with a different blanket design. COE is also calculated here. These modules are very similar with only slight differences between them. ARIES-AT – benchmark model with new (Aug 2009) costing accounts DCLL – dual-coolant lead-lithium blanket without manifold DCLL_M – with manifold (not used often) SiC – next-step version with a silicon-carbide blanket 2. Engineering: are required to run the engineering module. They are called by the certain subroutines during the engineering module: – called by geometry.cpp, contains constants and assumptions of the magnets – called by costingaccount.cpp, input parameters that are used to define costing accounts and COE – called by designpoint.cpp, constants provided by Rene Raffray, very similar between SiC and DCLL blankets – called by aries.cpp, contains the output database from the physics module consisting of 55 plasma parameters – is unique only to the DCLL case and includes a detailed inboard, outboard and divertor build of the blanket. This is read by the Aries.cpp program are 5 subroutines of code in the engineering module under the main program “Aries.cpp”: – main program – does unit costing analysis with specific material costs – goes through detailed costing for every account – also be known as “power flow,” computes powers, heat fluxes, pumping, CD, etc – computes the geometries of the machine, as well as magnets – makes output parts under “/OutputParts” And 5 corresponding header files. These call various lines in the appropriate .cpp code: Cost.h, CostingAccount.h, DesignPoint.h, Geometry.h, Part.h
ASC_Flow_of_Calculations%20don't%20use.docx