You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the benchmark execution, rootbench generates CSV files and other artifacts. At the moment, the path where these files are being saved is not configurable. Would it be a good idea to add an option allowing to choose where to save these files? One of the use cases I can see for this feature would be running rootbench in a Singularity container. Singularity usually uses a read-only filesystem, so it would be great to be able to bind-mount some writable directory to the container and save all of the generated files to this directory.
The text was updated successfully, but these errors were encountered:
Currently we configure the csv writing part here. We could add a configuration variable which defaults to the current place and if specified to set the new location.
During the benchmark execution, rootbench generates CSV files and other artifacts. At the moment, the path where these files are being saved is not configurable. Would it be a good idea to add an option allowing to choose where to save these files? One of the use cases I can see for this feature would be running rootbench in a Singularity container. Singularity usually uses a read-only filesystem, so it would be great to be able to bind-mount some writable directory to the container and save all of the generated files to this directory.
The text was updated successfully, but these errors were encountered: