Error:Task add_kernel is not registered to build FVKernel derived objects

[ScouperLH]

Hello everyone, I am using MOOSE to calculate the heat sink of a volumetric heat source by the coldplate. The following error occurred during operation:

Framework Information:
MOOSE Version: git commit fad6e84 on 2021-12-02
LibMesh Version:
PETSc Version: 3.15.1
SLEPc Version: 3.15.1

I am not sure of the cause of the error, because my code comes from some test files. I want to simulate the process as follows: There is an S-shaped channel in a coldplate, a metal heat source is placed on the coldplate, and the parameters I have written in the input file:
https://github.com/ScouperLH/bflow2/blob/70192880af7a699d99898984b665e193a803fc3c/coldplate.i
https://github.com/ScouperLH/bflow2/blob/70192880af7a699d99898984b665e193a803fc3c/coldplate1.e
coldplate1.e

In addition, I would like to know whether MOOSE can simulate the heat sink and thermal contact process of the coldplate now?

[GiudGiud]

Hello

I had a look at your input. You are mixing finite element and finite volume kernels in the [Kernels] block.
This is not supported. If you want to use finite volume fluid flow, you need to use finite volume heat conduction as well, and place all your kernels in [FVKernels].

Or you could transition your fluid flow simulation to finite element, then you dont need to change your heat conduction kernels.

Guillaume

[GiudGiud]

There is usually no problem importing sidesets or subdomains from Cubit / Trelis.
Can you check in paraview that the sidesets and subdomains are properly assigned?

[ScouperLH]

There is usually no problem importing sidesets or subdomains from Cubit / Trelis. Can you check in paraview that the sidesets and subdomains are properly assigned?

Do you mean to view it like this? I noticed that in the results of meshgenerator, there is an overall set of left/right/top/bottom, even though I did not set them.

[GiudGiud]

Hello

Yes, these are added for the cartesian/rectilinear mesh generators.
So the results are bad when you are importing the mesh from trelis, but good with moose mesh generators?

Two things to watch out for when generating meshes in cubit to use in moose:

• make sure to imprint/merge so that the meshes are conforming
• make sure to give a side (wrt surface ...) when creating sidesets. Otherwise the normal is not defined, and sometimes points on one side of the boundary, sometimes on the other one.

Guillaume

[ScouperLH]

I tried imprint/merge and it worked.


So I tried to re-mesh the model of the previous problem, and I found that when the size of the side where the two blocks touch is different, using imprint/merge will cause the mesh to be lost, and the relevant blocks and volumes will be missing in the output file. Is this an operating error? I have associated volume/surface (wrt-surface/volumn) when setting the side set.

[ScouperLH]

I imprint/merge after generating the grid manually, this problem seems to be solved. Thank you very much!

[ScouperLH]

Hello everyone, good news!
After a marathon-like test, we can get the result. During this period, I am very grateful to the two experts @GiudGiud @lindsayad for helping me. I am deeply sorry for the bother you in the past month. Thank you again!

[lindsayad]

I'm so happy you were able to get a result! Nice work @ScouperLH. Happy to help although @GiudGiud did the lion's share

[lindsayad]

please mark whatever answer was the "most helpful" so that we can consider this discussion "answered"

[ScouperLH]

please mark whatever answer was the "most helpful" so that we can consider this discussion "answered"

It's Ok

[GiudGiud]

Glad this is working!

have a good one,
Guillaume