Add chimera app #609

jginternational · 2019-07-01T20:24:13Z

Not ready yet
Missing JSON files

jginternational · 2019-07-01T20:30:50Z

Chimera_Case.gid.zip

adityaghantasala · 2019-07-02T05:34:01Z

@jginternational The zip file , is it the same case as Ruben posted on the other thread ?
And is it going to be a example case or something similar ?

adityaghantasala · 2019-07-02T05:43:23Z

Also I checked the interface, looks good. Thank you very much for your efforts. One minor thing I noticed is that the case is always 2D. There should also be an option to have 3D too.

jginternational · 2019-07-02T07:39:51Z

Hi @adityaghantasala
The zip is the same case Ruben posted (maybe the condition values are not the same) and it can be the given example.

I'll activate the 3D also.

rubenzorrilla · 2019-07-03T11:17:19Z

Can we add this cross section example as predefined example in the GUI?

adityaghantasala · 2019-07-03T11:43:07Z

yes we can ... !

rubenzorrilla · 2019-07-03T14:01:09Z

yes we can ... !

I'll try to create it.

…cs/GiDInterface into add-chimera-app

adityaghantasala · 2019-10-15T12:34:23Z

@rubenzorrilla ... How can I help here to continue with finishing the problem type. From the last commits, there is minor change in the JSON format. I will attach the JSON here by the end of the day. Niw JSON is similar to the Mesh motion solver.

rubenzorrilla · 2019-10-22T08:00:53Z

@rubenzorrilla ... How can I help here to continue with finishing the problem type. From the last commits, there is minor change in the JSON format. I will attach the JSON here by the end of the day. Niw JSON is similar to the Mesh motion solver.

Hi! I think that in the last iteration we had some problems with the writing. Could you please attach an example compatible with the latest version of your branch (including the json you mentioned above).

Thanks!!

adityaghantasala · 2019-10-25T11:46:38Z

Hi guys
Here are the examples which can also go in to problem types. Inside you will also find the json files in their newest format. Do let me know if they are easy to realize with the problemtype.

examples_for_chimera_problem_type.tar.gz

adityaghantasala · 2020-01-10T16:13:01Z

      "chimera_settings":{
         "chimera_echo_level":2,
         "reformulate_chimera_every_step":true,
         "chimera_parts":[
            [
               {
                  "model_part_name":"FluidModelPart.Parts_background_surface",
                  "overlap_distance":0.7,
                  "model_import_settings":{
                     "input_type":"mdpa",
                     "input_filename":"sep_meshes/chimera_background"
                  }
               }
            ],
            [
               {
                  "model_part_name":"FluidModelPart.Parts_patch_surface",
                  "overlap_distance":0.7,
                  "model_import_settings":{
                     "input_type":"mdpa",
                     "input_filename":"sep_meshes/chimera_patch_for_embedded"
                  }
               }
            ]
         ],
         "internal_parts_for_chimera":[
         ]
      }

jginternational · 2020-01-14T15:29:56Z

Hi @adityaghantasala
in the json:

"chimera_parts":[
        [
           {
              "model_part_name":"FluidModelPart.Parts_background_surface",
              "overlap_distance":0.7,
              "model_import_settings":{
                 "input_type":"mdpa",
                 "input_filename":"sep_meshes/chimera_background"
              }
           }
        ],
        [
           {
              "model_part_name":"FluidModelPart.Parts_patch_surface",
              "overlap_distance":0.7,
              "model_import_settings":{
                 "input_type":"mdpa",
                 "input_filename":"sep_meshes/chimera_patch_for_embedded"
              }
           }
        ]
     ]

Do you need this nested list structure? It's a list of lists of patches. Wouldn't it be better something like:

"chimera_parts":[
{
    "model_part_name":"FluidModelPart.Parts_background_surface",
    "overlap_distance":0.7,
    "model_import_settings":{
        "input_type":"mdpa",
        "input_filename":"sep_meshes/chimera_background"
    }
} ,
{
    "model_part_name":"FluidModelPart.Parts_patch_surface",
    "overlap_distance":0.7,
    "model_import_settings":{
        "input_type":"mdpa",
        "input_filename":"sep_meshes/chimera_patch_for_embedded"
    }
}
]

In addition, I can place the submodelpart name of the internal boundaries in each patch

jginternational · 2020-01-14T16:04:12Z

Ok, in this branch, you can test this example
test_chimera.gid.zip

Notice that we have 2 patches created:
-The first one has 2 internal boundaries and the second one 1

3 mdpa files are generated:

1 for the fluid
2 for the patches (One for each patch)

Chimera settings are:

"chimera_settings"            : {
            "chimera_echo_level"             : 1,
            "reformulate_chimera_every_step" : true,
            "chimera_parts"                  : [[{
                "model_part_name"            : "FluidModelPart.Patch_2",
                "overlap_distance"           : 0.7,
                "model_import_settings"      : {
                    "input_type"     : "mdpa",
                    "input_filename" : "Patch_2"
                },
                "internal_parts_for_chimera" : ["FluidModelPart.ChimeraInternalBoundary2D_Cross_2"]
            }],[{
                "model_part_name"            : "FluidModelPart.Patch_1",
                "overlap_distance"           : 0.8,
                "model_import_settings"      : {
                    "input_type"     : "mdpa",
                    "input_filename" : "Patch_1"
                },
                "internal_parts_for_chimera" : ["FluidModelPart.ChimeraInternalBoundary2D_Cross_1_A","FluidModelPart.ChimeraInternalBoundary2D_Cross_1_B"]
            }]]
        }

adityaghantasala · 2020-01-14T16:20:54Z

Awesome @jginternational thank you very much. I will test this tomorrow as I need to change some parts of the code to take care of the internal boundary parts.

adityaghantasala · 2020-01-15T10:14:58Z

@jginternational There are theree small issues :

The MainKratos.py is somehow outdated.
It the problemtype is not outputting the FluidMaterials.json
The Background is not being written in the "chimera_parts" of the "chimera_settings".

jginternational · 2020-01-15T17:37:38Z

@adityaghantasala

@jginternational There are theree small issues :

The MainKratos.py is somehow outdated.

Done.

It the problemtype is not outputting the FluidMaterials.json

Done

The Background is not being written in the "chimera_parts" of the "chimera_settings".

Would it be possible to assume that the background part is the one in volume_model_part_name? As far as I understand the background model part is always unique. Besides I find it easier from the user perspective as it would require to only specify the patches.

adityaghantasala · 2020-01-21T10:17:44Z

@jginternational good suggestion, I will see how I can do that and will get back to you.

jginternational · 2022-02-10T18:13:48Z

@adityaghantasala @KratosMultiphysics/chimera

The current Gui in this branch generates this example, that does not run. I don't know how to follow

chimera.gid.zip

Error message:

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Traceback (most recent call last)::String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
 
  File "C:\Users\garat\Desktop\chimera.gid\MainKratos.py", line 32, in <module>
    simulation.Run()
  File "E:\Deploy_Kratos\KratosMultiphysics\analysis_stage.py", line 47, in Run
    self.Initialize()
  File "E:\Deploy_Kratos\KratosMultiphysics\analysis_stage.py", line 93, in Initialize
    self._GetSolver().Initialize()
  File "E:\Deploy_Kratos\KratosMultiphysics\ChimeraApplication\navier_stokes_solver_vmsmonolithic_chimera.py", line 
47, in Initialize
    super(NavierStokesSolverMonolithicChimera,self).Initialize()
  File "E:\Deploy_Kratos\KratosMultiphysics\FluidDynamicsApplication\navier_stokes_solver_vmsmonolithic.py", line 324, 
in Initialize
    solution_strategy.Initialize()
RuntimeError: Error: The following errors occured in a parallel region!
Thread #7 caught exception: Error: In initialization of Element QSVMS #10340: No CONSTITUTIVE_LAW defined for property 
0.


in E:/PROYECTOS/KRATOS/Kratos/applications/FluidDynamicsApplication/custom_elements/fluid_element.cpp:88:FluidElement<c
lass QSVMSData<2,3,0> >::Initialize
   E:/PROYECTOS/KRATOS/Kratos/applications/FluidDynamicsApplication/custom_elements/fluid_element.cpp:100:FluidElement<
class QSVMSData<2,3,0> >::Initialize
Thread #6 caught exception: Error: In initialization of Element QSVMS #10181: No CONSTITUTIVE_LAW defined for property 
0.


in E:/PROYECTOS/KRATOS/Kratos/applications/FluidDynamicsApplication/custom_elements/fluid_element.cpp:88:FluidElement<c
lass QSVMSData<2,3,0> >::Initialize
   E:/PROYECTOS/KRATOS/Kratos/applications/FluidDynamicsApplication/custom_elements/fluid_element.cpp:100:FluidElement<
class QSVMSData<2,3,0> >::Initialize

philbucher · 2022-02-11T10:27:31Z

@adityaghantasala is not working at the chair any more, not sure who could solve this problem :/
@rubenzorrilla this seems like a regular fluid problem, do you have an idea?

jginternational added 6 commits June 13, 2019 17:00

Initial files for chimera app

a4ab2b9

Load the tree

69d32de

Write as fluid

87176bf

Chimera parts parameters

b04e020

Init write

087ccdb

Write a file foreach patch #597

9c99084

jginternational added new feature DO NOT MERGE YET Pull request not ready labels Jul 1, 2019

jginternational assigned rubenzorrilla Jul 1, 2019

Chimera cross example geometry

93ca2d8

rubenzorrilla assigned adityaghantasala and jginternational Jul 4, 2019

rubenzorrilla and others added 3 commits July 4, 2019 18:31

Conditions in cross example

8ef1093

Merge branch 'master' into add-chimera-app

fe60476

Merge branch 'add-chimera-app' of https://github.com/KratosMultiphysi…

b01699d

…cs/GiDInterface into add-chimera-app

rubenzorrilla mentioned this pull request Oct 15, 2019

Add SubModelPart feature #622

Open

Merge branch 'master' into add-chimera-app

0490486

Merge branch 'master' into add-chimera-app

5d4757e

Commit masivo y fuera

8dcece6

jginternational added 8 commits January 14, 2020 10:36

Write nodes in patches

8581e11

Skip submodelpart print for ChimeraInternalBoundar

3f4a058

Move to proper files

4f34a4b

typo

0680af8

Write internal boundary conditions in each file

6676106

write conditions by unique id

64c8936

Write submodelparts

f6f4c49

Patch submodelpart

3fa0bfc

Also project parameters

2c3a28c

jginternational added 2 commits January 15, 2020 18:15

Fluid materials write

5de94af

update python

1e687ca

jginternational added 4 commits March 30, 2020 11:26

Merge branch 'master' into add-chimera-app

c3612b8

Merge branch 'master' into add-chimera-app

9386f0c

bring chimera app to this century

a493359

required changes to execute

4a157d5

Merge branch 'master' into add-chimera-app

3ae89f9

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add chimera app #609

Add chimera app #609

jginternational commented Jul 1, 2019

jginternational commented Jul 1, 2019

adityaghantasala commented Jul 2, 2019

adityaghantasala commented Jul 2, 2019

jginternational commented Jul 2, 2019

rubenzorrilla commented Jul 3, 2019

adityaghantasala commented Jul 3, 2019

rubenzorrilla commented Jul 3, 2019

adityaghantasala commented Oct 15, 2019

rubenzorrilla commented Oct 22, 2019

adityaghantasala commented Oct 25, 2019

adityaghantasala commented Jan 10, 2020

jginternational commented Jan 14, 2020

jginternational commented Jan 14, 2020

adityaghantasala commented Jan 14, 2020

adityaghantasala commented Jan 15, 2020

jginternational commented Jan 15, 2020

adityaghantasala commented Jan 21, 2020

jginternational commented Feb 10, 2022

philbucher commented Feb 11, 2022

Add chimera app #609

Are you sure you want to change the base?

Add chimera app #609

Conversation

jginternational commented Jul 1, 2019

jginternational commented Jul 1, 2019

adityaghantasala commented Jul 2, 2019

adityaghantasala commented Jul 2, 2019

jginternational commented Jul 2, 2019

rubenzorrilla commented Jul 3, 2019

adityaghantasala commented Jul 3, 2019

rubenzorrilla commented Jul 3, 2019

adityaghantasala commented Oct 15, 2019

rubenzorrilla commented Oct 22, 2019

adityaghantasala commented Oct 25, 2019

adityaghantasala commented Jan 10, 2020

jginternational commented Jan 14, 2020

jginternational commented Jan 14, 2020

adityaghantasala commented Jan 14, 2020

adityaghantasala commented Jan 15, 2020

jginternational commented Jan 15, 2020

adityaghantasala commented Jan 21, 2020

jginternational commented Feb 10, 2022

philbucher commented Feb 11, 2022