Yes, VLSV also supports adaptive meshes, and we do use AMR. The file format is optimized for parallel I/O, which it does well… with a bit of a compromise on how easy it is to handle in post :).
Direct export from runtime to HTG would require rewriting the whole MPI-I/O workflow, so I doubt we would be doing that. Saving a descriptor and a file layout mapping for the HTG from runtime is feasible, though, and I’ll do likely just this in post for now. This begins to sound like the conduit descriptors, and they look very promising!
A quick try with the SetDescriptorBits indeed worked like a charm. This is very nice, I believe I can now start caching the descriptor and a mapping to the data layout.