Full Insert 3D Model

In this test case we will simulate a full insert.

1. Running the case

As the CAD generation is time consuming, the mesh is provided but will eventually need to be partitionned. However if you ever want to rebuild the CAD and Mesh you will find detailled instructions bellow. Otherwise you can directly skip these sections.

To run this example on MSO4SC portal see this section.

1.1. Create the geometry:

salome -t $HIFIMAGNET/HIFIMAGNET_Cmd.py args:--cfg=HL-31.yaml
salome -t $HIFIMAGNET/HIFIMAGNET_Cmd.py args:--cfg=HL-31.yaml,--air

Beware that creating the geometry from scratch may take a long time. For a 14 Helices insert it takes at least 4 days…​

1.2. Generate the mesh

salome -t $HIFIMAGNET//HIFIMAGNET_Cmd.py args:--insert=HL-31.yaml,--air,--mesh[,--groupCoolingChannels]

1.3. Partitionning the mesh:

gmsh -3 -bin HL-31.med -o HL-31.msh
feelpp_mesh_partitioner --ifile HL-31.msh [--ofile HL-31_p32] --part 32  --nochdir

1.4. Running the model (here couplecartmodel):

mpirun -np 32 feelpp_hfm_coupledcartmodel_3DP1N1 --config-file HL-31.cfg

2. Data files

2.1. Geometry files

  • HL-31.yaml

  • HL-31_Hn.yaml with n=1,..14

  • Ring-HnH(n+11).yaml with n=1,..,13

  • inner.yaml

  • outer.yaml

Definition of the helical cut per helix:

  • HL-31_Hn_cut_salome.dat with n=1,..14

2.2. Mesh files

  • HL-31_meshdata.yaml

2.3. Simulation cfg file

  • HL-31.cfg

2.4. Model files

  • HL-31_thermoelec.json

  • HL-31_magcart.json

  • HL-31_elasticity.json

2.5. Materials files

Materials are stored in a dedicated repository Materials

3. Outputs

  • some metrics

4. Notes

the executables must be in the path or should be prefixed with appropriate directories.

For instance on Lncmi server:

FEELPP_MESH_APPS_DIR=$FEELPP_BUILD_DIR/applications/mesh/
HIFIMAGNET_APPS_DIR=~/feelpp_build/new_Json/research/hifimagnet/applications
HIFIMAGNET=/opt/SALOME-8.3.0-DB9.5/INSTALL/HIFIMAGNET/bin/salome

The coupledcart model is in $HIFIMAGNET_APPS_DIR/CoupledCartModel/