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

Panzer: Read source terms from a file #13684

Open
delcmo opened this issue Dec 18, 2024 · 2 comments
Open

Panzer: Read source terms from a file #13684

delcmo opened this issue Dec 18, 2024 · 2 comments

Comments

@delcmo
Copy link

delcmo commented Dec 18, 2024

Problem description

We would like to implement logic to read source terms from a file: volumetric source terms as a function of Cartesian coordinates. The application problem is the following: heat deposition is predicted by a neutronic code. The heat deposition is volume-averaged over each mesh element and then stored in a file along with the Cartesian coordinates of the center of each mesh element. The same mesh is then used in our CFD package to model flow distribution.

Questions

A few questions:

  1. What is the best approach to implement such feature? My primary thinking is to initialize a nodal variable with the source terms read from the file and then rely on the basis functions to get the source term values at quadrature point.
  2. Does Panzer have interpolation capabilities? By interpolation it could be nearest point strategy or linear interpolation for instance to initialize the source term values at the degree of freedom location.

Thanks,

Marco

@ccober6
Copy link
Contributor

ccober6 commented Dec 18, 2024

@trilinos/panzer

@rppawlo
Copy link
Contributor

rppawlo commented Dec 18, 2024

@delcmo - there is nothing in the main panzer code that supports this. All applications built on panzer do add something to read auxiliary data, but the method really depends on the source format file. I would probably read the point data and use the arbor-x tool to map the data directly onto the stk mesh. I think you can treat the source data as a point cloud with arbor-x. You could probably even map the values directly to quadrature points with arbor-x as well. Then store this data in an evaluator that can fill an mdfield with the correct values.

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

No branches or pull requests

3 participants