Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FSI] Update to time stepping #868

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

jginternational
Copy link
Member

Updating FSI app to the time stepping.

It was taking the time step value for structural from the fluid app, but the user had both in the GUI.
It it has to be the same timestep for both apps, we can place it in the common section of the gui.

@jginternational
Copy link
Member Author

In addition, the app seem to be broken.

Several deprecation warnings and an error occur:

TetrahedralMeshOrientationCheck: No inverted elements found
Mesh orientation check found 720 inverted conditions.
NavierStokesSolverMonolithic: Model reading finished.
PartitionedFSIBaseSolver: Fluid fluid_positive FSI coupling interface created
[WARNING] CreateFillCommunicator: This function is deprecated, use "CreateFillCommunicatorFromGlobalParallelism" instead
PartitionedFSIBaseSolver: Coupling strategy construction finished
PartitionedFSIBaseSolver: Structure FSI coupling interface created
[WARNING] CreateFillCommunicator: This function is deprecated, use "CreateFillCommunicatorFromGlobalParallelism" instead
::[MechanicalSolver]:: : DOF's ADDED
::[ImplicitMechanicalSolver]:: : DOF's ADDED
NavierStokesSolverMonolithic: Fluid solver DOFs added correctly.
::[MeshSolverBase]:: DOFs ADDED.:
[WARNING] DEPRECATION-Warning; MappingApplication: The "MapperFactory" was moved to the Core! (used for "CreateMapper")
::[MechanicalSolver]:: : Initializing ...
[WARNING] DEPRECATION-Warning; MechanicalSolver: Using "line_search", please move it to "solving_strategy_settings" as "type"
::[MechanicalSolver]:: No linear solver was specified, using fastest available solver:
Linear-Solver-Factory: Creating "sparse_lu" as fastest available direct solver
::[MechanicalSolver]:: : Finished initialization.
Linear-Solver-Factory: Constructing a regular (non-complex) linear-solver
NavierStokesSolverMonolithic: Solver initialization finished.
Linear-Solver-Factory: Constructing a regular (non-complex) linear-solver
::[MeshSolverBase]:: Finished initialization.:
aaa: Analysis -START-
aaa: STEP =  1
aaa: TIME =  0.002
[WARNING] ResidualBasedBlockBuilderAndSolver: ATTENTION! setting the RHS to zero!
[WARNING] DEPRECATION-Warning; MappingApplication: The "Mapper" was moved to the Core! (used for "SWAP_SIGN")
PartitionedFSIBaseSolver: FSI non-linear iteration = 0 |res|/sqrt(nDOFS) = 9.005636836600007e-09
PartitionedFSIBaseSolver: FSI non-linear iteration convergence achieved in 0 iterations.
Traceback (most recent call last):
  File "C:\Users\garat\Desktop\aaa.gid\MainKratos.py", line 45, in <module>
    simulation.Run()
  File "E:\Deploy_Kratos\KratosMultiphysics\analysis_stage.py", line 48, in Run
    self.RunSolutionLoop()
  File "E:\Deploy_Kratos\KratosMultiphysics\analysis_stage.py", line 68, in RunSolutionLoop
    self.OutputSolutionStep()
  File "E:\Deploy_Kratos\KratosMultiphysics\FSIApplication\fsi_analysis.py", line 93, in OutputSolutionStep
    super(FSIAnalysis, self).OutputSolutionStep()
TypeError: super(type, obj): obj must be an instance or subtype of type
KRATOS TERMINATED WITH ERROR

Copy link
Member

@rubenzorrilla rubenzorrilla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Substepping capabilities are not implemented in Kratos yet. Ergo, time step must be the same in both apps. We decided to take the fluid app. time step as "master".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants