Skip to content

Provide vector valued function for initialization#126

Closed
BenjaminRodenberg wants to merge 2 commits intodevelopfrom
BenjaminRueth-patch-1
Closed

Provide vector valued function for initialization#126
BenjaminRodenberg wants to merge 2 commits intodevelopfrom
BenjaminRueth-patch-1

Conversation

@BenjaminRodenberg
Copy link
Copy Markdown
Contributor

@BenjaminRodenberg BenjaminRodenberg commented Dec 9, 2020

I explain the bug here: 41b1a46#commitcomment-44959091

Copy link
Copy Markdown
Member

@IshaanDesai IshaanDesai left a comment

Choose a reason for hiding this comment

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

The changes made are correct but there is another conflict elsewhere regarding passing a vector valued function to the adapter.

@IshaanDesai
Copy link
Copy Markdown
Member

In the time loop, only the y-component of the flux is provided to the write_data() function.

# Dirichlet problem obtains flux from solution and sends flux on boundary to Neumann problem
determine_heat_flux(V_g, u_np1, k, fluxes)
fluxes_y = fluxes.sub(1)  # only exchange y component of flux.
precice.write_data(fluxes_y)

This entity is detected as a scalar entity by the adapter. This is a problem because the original function related to the flux is defined on a VectorFunctionSpace V_g.

@BenjaminRodenberg
Copy link
Copy Markdown
Contributor Author

I just realized that OpenFOAM requires a scalar quantity. So the current approach is fine (at least for develop), if we don't want to change the OpenFOAM-side.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants