We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With scene renders, I can provide an image prefix like image_prefix: "./filename_%06d" and at step 5 will be exported filename_000005.png.
image_prefix: "./filename_%06d"
filename_000005.png
How can I do similar for extracts to HDF5? e.g. if i give it path: "./filename_%06d" the resulting output file is literally called filename_%06d.root.
path: "./filename_%06d"
filename_%06d.root
The text was updated successfully, but these errors were encountered:
Good suggestion, we will see if we can use the same strategy we used for images and add an option to support this for extracts.
Sorry, something went wrong.
Thanks @cyrush , in the meantime is there a way i can intercept the name of the extract outputs and change it to append a time step?
conduit::Node exec_info; ascent_instance.info(exec_info);
Will report details about the extract after you call execute.
That said, the root file will have the directory name baked in so changing could unlink the info needed to load the file set.
You can set the exact name, or also strip out the cycle using extract options -- I'll admit we need better docs for this.
Thanks, I think I'll just make a directory with the cycle and move the extracts there instead of tinkering with the extract internals.
No branches or pull requests
With scene renders, I can provide an image prefix like
image_prefix: "./filename_%06d"
and at step 5 will be exportedfilename_000005.png
.How can I do similar for extracts to HDF5? e.g. if i give it
path: "./filename_%06d"
the resulting output file is literally calledfilename_%06d.root
.The text was updated successfully, but these errors were encountered: