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

resizes output vector to better handle vectors #3835

Open
wants to merge 7 commits into
base: devel
Choose a base branch
from

Conversation

andcarl1364
Copy link

enhances MeshFunction to better handle vector variables which in turn helps general field transfers work with vectors as well

resolves: #3714
see also: #26084, #26045

This solves problems found when using MOOSE in tandem with libmesh due
to MOOSE’s implementation treating names as the “first-class” identifier

Resolves: libMesh#3489
enhances MeshFunction to better handle vector variables
which in turn helps general field transfers work with vectors as well

resolves: libMesh#3714
see also: #26084, #26045
enhances MeshFunction to better handle vector variables
which in turn helps general field transfers work with vectors as well

 resolves: libMesh#3714
see also: #26084, #26045
@roystgnr
Copy link
Member

What does this do?

_new_resize gets initialized to 0, then I don't see it ever being used again.

vec_dim, n_vector_vars, and n_scalar_vars get calculated (somewhat confusingly, but that's an existing problem with the overlapping terminology for scalar-valued-functions vs discrete-per-system-scalars) ... and then I don't see them ever being used again?

@andcarl1364
Copy link
Author

my file didn't save correctly, let me do it again

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

Successfully merging this pull request may close these issues.

Enhance MeshFunction to handle vector variables
3 participants