3. Operands#

3.1. Operand TYPE_COEUR#

Name of the type of heart to be treated.

The case “TEST” represents a fictional core with five fuel assemblies, arranged in a cross.

The case “MONO” represents an assembly alone (i.e. a fictional mono-assembly core, without taking into account contact with the tank internals) at « hot core » temperature.

The case “MONO_FROID” represents an assembly alone (i.e. a fictional mono-assembly core, without taking into account contact with the tank internals) at ambient temperature.

The “LIGNEXXX” cases (with XXX =”900”, “1300”, or” N4 “) represent a row calculation for each tier design.

Refer to the reference documentation [R7.06.01], in particular for everything concerning the loads and the various references used.

3.2. Operand NB_ASSEMBLAGE#

In the case of a “LIGNEXXX” core (with XXX =”900”, “1300” or “N4”), this keyword allows you to specify the length of the line.

3.3. Operand TABLE_N#

Table (in DAMAC format) containing assembly information (position, design and deformation mainly).

For a “DEFORMATION” calculation, this is the composition of the core of the simulated cycle. For a “LAME” calculation, this is DAMAC from which we want to calculate the water blades. For a “ETAT_INITIAL” calculation, this is the DAMAC that we want to reproduce.

3.4. Operand MAILLAGE_N#

Mesh matching the core description: The design of the assemblies in the mesh should match the design provided in “TABLE_N”.

3.5. Operand FLUENCE_CYCLE#

« Fixed » fluency to take into account the initial irradiation of the assemblies: the initial irradiation of each assembly is taken equal to \(N\) times” FLUENCE_CYCLE “with \(N\) the number of past cycles of the assembly, given in” TABLE_N “.

With a value of FLUENCE_CYCLE =0, all the assemblies will therefore have zero initial irradiation.

Note: this keyword is not taken into account for a DEFORMATION calculation with RESU_INIT, because in this case the initial irradiation of each assembly comes from the result given in RESU_INIT.

3.6. Operand TYPE_DEFORMATION#

Allows you to choose whether to take kinematics into account. The only option available is” RIGI_GEOM “which corresponds to a calculation in PETIT with option RIGI_GEOM =” OUI”.

3.7. Operand DEFORMATION#

Keyword factor that specifies that macro-control is used here to calculate the deformations of fuel assemblies in core configuration.

3.7.1. Operand RESU_INIT#

Possibility of giving a result in initial condition. This keyword is useful in the case of carrying out several irradiation cycles.

3.7.2. Operand UNITE_THYC#

Logical unit in which the file THYC is given as input to CALC_MAC3COEUR containing axial and transverse hydraulic loads.

3.7.3. Operand TEMP_IMPO#

Constant temperature value. Activates the simple expansion calculation of the reactor (without contacts/friction or hydraulic loads).

3.7.4. Operand NIVE_FLUENCE#

Value of the fluence received by the assemblies during the cycle (in \({10}^{24}\mathit{neutrons}/{m}^{2}\)).

3.7.5. Operand MAINTIEN_GRILLE#

Allows you to activate the option to block the grids

3.7.6. Operand TYPE_MAINTIEN#

For multi-assembly core cases (different from “MONO” or “MONO_FROID”), this keyword is optional and only allows the value “DEPL_PSC” (by default) explained below. The holding force is then generated by the displacement imposed by the Upper Heart Plate (PSC) on the holding system of each assembly. The value of this displacement is entered in the geometric data file (datg) of each of the hearts in question.

In the case of mono-assembly (“MONO” or “MONO_FROID”), the keyword TYPE_MAINTIEN is mandatory, with no value by default, and can take the values” DEPL_PSC “or” FORCE “:

“DEPL_PSC”: the maintenance effort is then generated by a displacement imposed as described above; in this case the FORCE_MAINTIEN keyword is not expected;
“FORCE”: the holding force is then introduced by a fixed imposed force whose value is given by the keyword FORCE_MAINTIEN. This option makes it possible to faithfully reproduce the experimental tests, which are used in particular to recalibrate the model.

3.7.7. Operand FORCE_MAINTIEN#

In the case of mono-assembly (“MONO” or “MONO_FROID”), this keyword makes it possible to provide the value (in Newtons) of the holding force in the case TYPE_MAINTIEN =” FORCE “.

3.7.8. Operand ARCHIMEDE#

In the case of mono-assembly, the ARCHIMEDEest keyword is mandatory, has no default value, and can take the values” OUI “or” NON “. This keyword allows you to choose whether the Archimedes thrust is activated or not.

For cases of multi-assembly cores (different from “MONO” or “MONO_FROID”), this keyword is optional and only allows the value “OUI” (value by default): the Archimedes thrust is always activated.

3.8. Operand LAME#

Keyword factor that specifies that macro-control is used here to determine the layers of water from a core composed of deformed assemblies. For an « end of cycle » water slide calculation (EOC in English), all you need to do is provide the DAMAC measured in “TABLE_N”. For a « start of cycle » water blade calculation (BOC in English), you must provide a DAMAC « reconstituted » from the known DAMAC and the core plane; this DAMAC « reconstituted » is at the user’s expense, and must be provided in “TABLE_N”. Hydraulic forces are taken into account by the load defined in “UNITE_THYC”.

3.8.1. Operand UNITE_THYC#

Logical unit in which the file THYC is given as input to CALC_MAC3COEUR containing axial and transverse hydraulic loads.

3.8.2. Operands COEF_MULT_THV and COEF_MULT_THT#

Multiplicative coefficients for axial and transverse hydraulic loads.

3.9. Operand ETAT_INITIAL#

Keyword factor that specifies that the macro-control is used here to reconstitute the mechanical state based on the observation of deformations at the end of the cycle: this mechanical state can then be used as the initial state in a subsequent calculation.

3.9.1. Operand UNITE_THYC#

Same use as in § 3.8.1

3.9.2. Operand NIVE_FLUENCE#

Same use as in § 3.7.4.

3.9.3. Operand TYPE_MAINTIEN#

Same use as in § 3.7.6 in the case other than “MONO”.

3.9.4. Operand ARCHIMEDE#

Same use as in § 3.7.8 in the case other than “MONO”.

3.10. Operand RESU_DEF#

In the case of the use of the operand “LAME”, the result is provided on the mesh initially deformed by the deformation data (Cf. [R7.06.01] for the details of this operation): the displacements provided by the result concept are therefore to be understood as the displacement relative to this deformed mesh and as the displacement relative to the mesh provided with the « right » assemblies. In practice, it is therefore complicated to use such movements. CALC_MAC3COEUR/LAME therefore proposes the operand “RESU_DEF” which makes it possible to retrieve a result concept that contains the displacement on the initial undeformed mesh, which makes it possible to easily post-process the movements.

On the other hand, for post-treatments such as « water slides », the results provided by the CALC_MAC3COEUR result concept are perfectly usable.

The recommendation with a water blade calculation is therefore to proceed as follows:

RESU ** = CALC_MAC3COEUR (

[…]

RESU_DEF = CO (“RESUDEPL”),

LAME =_F (

[…]

)

)

# post-treatment of water slides on RESU

POST_MAC3COEUR (

RESULTAT = RESU,

[…]

LAME =_F (

[…]

),

)

# post-processing of movements on RESUDEPL

POST_MAC3COEUR (

RESULTAT = RESUDEPL,

[…]

DEFORMATION =_F (

[…]

),

)