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

legacy vtk extract issues #1368

Open
cyrush opened this issue Aug 23, 2024 · 1 comment
Open

legacy vtk extract issues #1368

cyrush opened this issue Aug 23, 2024 · 1 comment
Labels

Comments

@cyrush
Copy link
Member

cyrush commented Aug 23, 2024

  • check if fields are written as well as the mesh data
  • filenames need to use cycle, or some other counter option to avoid overwriting
@cyrush cyrush added the bug label Aug 23, 2024
@indra098124
Copy link

if I am looking at the right place, I can see that the basename used to generated directory for vtk file uses a fixed name

// we create
    // file: basename.visit
    // directory: basename + "_vtk_files"
    // files: basename + "_vtk_files/basename_%08d.vtk"

    std::string output_base = params()["path"].as_string();
    
    std::string output_files_dir  = output_base + "_vtk_files";
    std::string output_visit_file = output_base + ".visit";

https://github.com/Alpine-DAV/ascent/blob/develop/src/libs/ascent/runtimes/flow_filters/ascent_runtime_vtkh_filters.cpp

I also see that fields are written in the vtk file but only those fields which are referenced in the acent_actions. In the same ascent action I have some scenes which reference to fields, my vtk output depends on them instead of having all fields.

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

No branches or pull requests

2 participants