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

Doubt in fluid domain visualization #156

Open
NM1293 opened this issue Mar 25, 2024 · 0 comments
Open

Doubt in fluid domain visualization #156

NM1293 opened this issue Mar 25, 2024 · 0 comments

Comments

@NM1293
Copy link

NM1293 commented Mar 25, 2024

Hello,

I am attempting to execute the code for fluid visualization available at https://flow.byu.edu/FLOWUnsteady/examples/rotorhover-fdom/.

Previously, I followed the "variable fidelity" tutorial https://flow.byu.edu/FLOWUnsteady/examples/rotorhover-aero/, utilizing mid-low fidelity, with the intention of utilizing these outcomes to conduct the fluid domain visualization.

However, I have encountered some uncertainties regarding the fluid visualization code. Upon examining the results obtained from the execution of the "variable fidelity" tutorial, I discovered numerous files labeled "rotorhover-example_pfield.TIMESTEP.h5/.xmf" and "rotorhover-example_staticpfield.TIMESTEP.h5/.xmf", where TIMESTEP indicates the associated time step. Hence, if my understanding is correct, the variables "pfield_prefix" and "staticpfield_prefix" in the "fluid domain" code should correspondingly be set to "rotorhover-example_pfield" and "rotorhover-example_staticpfield", while the variable "nums" should be equivalent to the total number of time steps of the simulation for which I wish to visualize the fluid domain, minus 1.

Upon completion, I only obtain a single .h5 and a single .xmf file.

Is this correct?

Should I be able to open these files with ParaView? I attempted to do so, but encountered difficulties in visualization.

The code I am using is attached.

Thank you for your assistance.
fluid_domain.txt

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

No branches or pull requests

1 participant