-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Add support for declaring sidesets in input file that do not exist initially #27913
Open
5 tasks done
Labels
Comments
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
Jun 17, 2024
inputs that dont exist at the beginning of the simulation refs idaholab#27913
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
Jun 17, 2024
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
Jun 17, 2024
inputs that dont exist at the beginning of the simulation refs idaholab#27913
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
Jun 17, 2024
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
Jun 17, 2024
inputs that dont exist at the beginning of the simulation refs idaholab#27913
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
Jun 17, 2024
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
Jun 18, 2024
inputs that dont exist at the beginning of the simulation refs idaholab#27913
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
Jun 18, 2024
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
Jun 18, 2024
inputs that dont exist at the beginning of the simulation refs idaholab#27913
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
Jun 18, 2024
grunerjmeier
pushed a commit
to grunerjmeier/moose
that referenced
this issue
Jun 20, 2024
inputs that dont exist at the beginning of the simulation refs idaholab#27913
grunerjmeier
pushed a commit
to grunerjmeier/moose
that referenced
this issue
Jun 20, 2024
abanki1
pushed a commit
to abanki1/moose
that referenced
this issue
Jul 11, 2024
inputs that dont exist at the beginning of the simulation refs idaholab#27913
abanki1
pushed a commit
to abanki1/moose
that referenced
this issue
Jul 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Reason
See discussion below.
The input errors because the sideset does not exist at t=0, but will exist later in the simulation
Design
Same as add-subdomain-id parameter in MooseMesh
A parameter, then simple logic adding the sideset id to the list of sideset ids and boundary ids
Impact
Facilitate simulations with changing meshes
Discussed in #27857
Originally posted by Traiwit June 10, 2024
Check these boxes if you have followed the posting rules.
Question
Hi guys,
I have 3 questions RE:
ElementSubdomainModifier
(more specificallyCoupledVarThresholdElementSubdomainModifier
)First question, how do I make BC wait for the boundary to be generated? lets say i'm generating a boundary at every time step
but during the initialization, it just gives this error
I tried to ignore the checks, but still doesnt work
Question2: if I call
CoupledVarThresholdElementSubdomainModifier
twice in 1 input file, the surface/side generated is overwritten the previous one, for example if I do thisonly
moving_boundary_wedge
will be produced in the mesh, how to overcome this problem? as later on, i might want to generate surface at the top of the mesh for surface recharge and stuff as well as the drain surfaceLast question, this is probs the most headache one
I have modified ElementSubdomainModifier, so that it only produces surface(s) based on the variable, (i dont want anything to do with Subdomain whatsoever). I'm not so good with C++ so I mostly just commented out lines that related to subdomain
now I have a problem, the surface I generated is almost perfect, but it still generated artificial surfaces inside the main surface, I dig deep enough to realise that this 'inside surface' is caused by the parallelisation? the more mpi cores > the more inside surfaces
compare to the one I want (pre-made, not generated)
below is my modified ElementSubdomainModifier.C could you help me to improve this?
or should I make another function that remove the surfaces inside any surface (scan all directions, etc)?
if I'm not mistaken @hugary1995 is the one who created this class, right?
I'm also tagging: @GiudGiud since you know the general framework pretty well.
Thank you very much!
Kind regards,
Trai
The text was updated successfully, but these errors were encountered: