FeatureFloodCount

[Rahim-Habibi]

Hi all,

I ma using "FeatureFloodCount" as postprocessor in my model. but i am confused regarding the variable type because when i am calling main variable as arguement it works however when i am calling auxvariable the run stops by "Bad Termiantion" :
calling main variable:

 [./flood_count]
   type = FeatureFloodCount
   variable = temperature
   compute_var_to_feature_map = true
   threshold = 2.9e6
   execute_on = 'timestep_end'
  [../]

calling aux-variable:

  [./flood_count]
   type = FeatureFloodCount
   variable = stress_excess
   compute_var_to_feature_map = true
   threshold = 2.9e6
   execute_on = 'timestep_end'
  [../] 

Here is the log

*** Warning, This code is deprecated and will be removed in future versions:
Please update your main.C to adapt new main function in MOOSE framework, see'test/src/main.C in MOOSE as an example of moose::main()'. 


�[33m
*** Warning, This code is deprecated and will be removed in future versions:
/export/dump/rahim/sensivity/tiger_files/tpv-new-mesh-well.i:44.5: The 'Modules/TensorMechanics/Master' syntax is deprecated. Please use 'Physics/SolidMechanics/QuasiStatic' instead.�[39m


�[33m
*** Warning, This code is deprecated and will be removed in future versions:
/export/dump/rahim/sensivity/tiger_files/tpv-new-mesh-well.i:45.7: The 'Modules/TensorMechanics/Master' syntax is deprecated. Please use 'Physics/SolidMechanics/QuasiStatic' instead.�[39m

Setting Up..
�[36mThe following total 1 aux variables:
  Coulomb_Stress
are added for automatic output by MaterialOutputAction.�[39m

Finished Setting Up                                                                      [�[33m 24.82 s�[39m] [�[33m  363 MB�[39m]
Framework Information:
MOOSE Version:           git commit fd18d88b46 on 2024-07-08
LibMesh Version:         
PETSc Version:           3.20.3
SLEPc Version:           3.20.1
Current Time:            Thu Nov 21 14:22:47 2024
Executable Timestamp:    Tue Jul  9 10:49:32 2024

Checkpoint:
  Wall Time Interval:      Every 3600.000000 s
  User Checkpoint:         Disabled
  # Checkpoints Kept:      2
  Execute On:              TIMESTEP_END 

Parallelism:
  Num Processors:          50
  Num Threads:             1

Mesh: 
  Parallel Type:           replicated
  Mesh Dimension:          3
  Spatial Dimension:       3
  Nodes:                   
    Total:                 33461
    Local:                 851
    Min/Max/Avg:           449/871/669
  Elems:                   
    Total:                 209895
    Local:                 4208
    Min/Max/Avg:           4030/4292/4197
  Num Subdomains:          15
  Num Partitions:          50
  Partitioner:             metis

Nonlinear System:
  Num DOFs:                167305
  Num Local DOFs:          4255
  Variables:               { "disp_x" "disp_y" "disp_z" "pressure" "temperature" } 
  Finite Element Types:    "LAGRANGE" 
  Approximation Orders:    "FIRST" 

Auxiliary System:
  Num DOFs:                371606
  Num Local DOFs:          8392
  Variables:               { "p0" "dP" "T0" "dT" } { "stress_excess" "invCritNucArea" "normal_stress" 
                             } "Coulomb_Stress" 
  Finite Element Types:    "LAGRANGE" "MONOMIAL" "MONOMIAL" 
  Approximation Orders:    "FIRST" "CONSTANT" "CONSTANT" 

Execution Information:
  Executioner:             Transient
  TimeStepper:             IterationAdaptiveDT
  TimeIntegrator:          ImplicitEuler
  Solver Mode:             NEWTON
  PETSc Preconditioner:    asm 
  MOOSE Preconditioner:    SMP

�[31mLEGACY MODES ENABLED:�[39m
 This application uses the legacy material output option: material properties are output only on TIMESTEP_END, not INITIAL. To remove this message, set 'use_legacy_material_output' to false in this application. If there are gold output files that contain material property output for which output occurs on INITIAL, then these will generate diffs due to zero values being stored, and these tests should be re-golded.
�[39m
�[31mLEGACY MODES ENABLED:�[39m
 This application uses the legacy initial residual evaluation behavior. The legacy behavior performs an often times redundant residual evaluation before the solution modifying objects are executed prior to the initial (0th nonlinear iteration) residual evaluation. The new behavior skips that redundant residual evaluation unless the parameter Executioner/use_pre_smo_residual is set to true. To remove this message and enable the new behavior, set the parameter 'use_legacy_initial_residual_evaluation_behavior' to false in *App.C. Some tests that rely on the side effects of the legacy behavior may fail/diff and should be re-golded.
�[39m
Currently Executing
  Performing Initial Setup
    Finished Building SemiLocalElemMap                                                   [�[33m  7.06 s�[39m] [�[33m  451 MB�[39m]
  Finished Performing Initial Setup                                                      [�[33m 12.39 s�[39m] [�[33m  451 MB�[39m]

Time Step 0, time = -172800

Postprocessor Values:
+----------------+----------------+----------------+----------------+-------------------+
| time           | dt             | flood_count    | max_area       | max_stress_excess |
+----------------+----------------+----------------+----------------+-------------------+
|  -1.728000e+05 |   0.000000e+00 |   0.000000e+00 |   0.000000e+00 |      0.000000e+00 |
+----------------+----------------+----------------+----------------+-------------------+


Time Step 1, time = -86400, dt = 86400
Pre-SMO residual: 1.38818e+14

Performing automatic scaling calculation

 0 Nonlinear |R| = �[32m5.165964e+00�[39m
 1 Nonlinear |R| = �[32m1.171421e-02�[39m
 2 Nonlinear |R| = �[32m3.137700e-04�[39m
 3 Nonlinear |R| = �[32m1.161997e-05�[39m
 4 Nonlinear |R| = �[32m2.076078e-07�[39m
�[32m Solve Converged!�[39m
  Finished Solving                                                                       [�[33m 15.68 s�[39m] [�[33m  511 MB�[39m]

===================================================================================
=   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
=   PID 52079 RUNNING AT heisenbug
=   EXIT CODE: 9
=   CLEANING UP REMAINING PROCESSES
=   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault (signal 11)
This typically refers to a problem with your application.
Please see the FAQ page for debugging suggestions

[GiudGiud]

Hello

I tried for a bit but I cannot reproduce the seg fault you hit.
Do you mind sharing your whole input and the mesh (if it's required to hit this problem)?

Guillaume

[Rahim-Habibi]

Hi @GiudGiud
I can not share whole input and mesh file unfortunately, but i can share the blocks related to the issue.
auxvariable
[./stress_excess]
family = MONOMIAL
order = CONSTANT
block = 'fault_left fault_right fault_mid fault_bottom fault_top '
[../]
auxkernel
[./stress_excess_ker]
type = MaterialRealAux
property = Coulomb_Stress
variable = 'stress_excess'
execute_on = 'TIMESTEP_END'
block = 'fault_left fault_right fault_mid fault_bottom fault_top'
[../]
[./flood_count]
type = FeatureFloodCount
variable = stress_excess
compute_var_to_feature_map = true
threshold = 1
execute_on = 'timestep_end'
[../]

when i comment out the "flood_count" block in input file, the model runs as expected.

Thanks in advance

[GiudGiud]

please try block-restricting the feartureFloodCount using the same restriction as the auxvariable

[Rahim-Habibi]

Thanks @GiudGiud
I got the following error:
*** ERROR ***
i:841.5: unused parameter 'UserObjects/flood_count/block'

[GiudGiud]

alright. can you try not block-restricting the variable then? I m wondering if that's the problem. I did not have any issue using an auxvariable on my input