Multiple Silo cycles without suffix about conduit HOT 3 OPEN

Hi @ibaned -- our usual use cases leverage a set of files per time step. (Each timestep is an independent set)

We will need to think a bit about how the root file can create the indexing metadata for multiple cycles. I assume a goal would be to have the time series be easily used in viz tools? I am not sure they will present the data in an intuitive way right now.

We can experiment to see what is the best path in early dec.

from conduit.

Hi @ibaned. This is possible already, with a couple caveats. The other option you will want to include is opts["mesh_name"] = "mymeshname";. You can put whatever name you like there (so the cycle number could go there). The silo writer will prepend that name to the multimesh, multivar, and multimaterial names. It will also place information for domains inside of a directory with that name. Therefore, the only place where information might be clobbered in ensuing writes would be the cycle and time that live inside the root file. I wonder how easy it would be to work with a database stored in this way in a tool like VisIt? I expect you would get a giant list of meshes, and VisIt wouldn't be able to interpret that as a timeseries.

from conduit.

@ibaned @cyrush Can we close this issue?

from conduit.