tRIBS can generate a dynamic spatial output file—where the file records for each Voronoi cell state and flux variables. These output are useful on many levels—but their usefulness depends on the frequency of output, where increased frequency leads to increased usefulness. But the challenge is that even a short, 1 year simulation with hourly output would produce 8760 *.dyn files. These are text files, so can be large and consume a lot of storage, and the shear volumes can make opening and accessing the data a complete headache. I suggest we create some function that can operate during a tRIBS simulation to continously "clean" the results folder of these files. Cleaning will entail read the data in and storing it in some sort of data base—perhaps SQlite?
tRIBS can generate a dynamic spatial output file—where the file records for each Voronoi cell state and flux variables. These output are useful on many levels—but their usefulness depends on the frequency of output, where increased frequency leads to increased usefulness. But the challenge is that even a short, 1 year simulation with hourly output would produce 8760 *.dyn files. These are text files, so can be large and consume a lot of storage, and the shear volumes can make opening and accessing the data a complete headache. I suggest we create some function that can operate during a tRIBS simulation to continously "clean" the results folder of these files. Cleaning will entail read the data in and storing it in some sort of data base—perhaps SQlite?