Open HenryYihengXu opened 4 years ago
Hmm....it is designed to be very frugal w.r.t. to log files and I see only two from macsio itself there macsio-log.log
and macsio-timings.log
. All the other .silo
files are data files probably run in file-per-processor mode. Changing command-line arguments regarding -parallel_file_mode MIF
affects this. Or, for those plugins that support single-shared-file like HDF5
plugin, using -parallel_file_mode SIF
.
Am I miss-understanding your question?
Sorry for the unclear part. What I wanted to say are those .silo
files. By command-line arguments, is there a way to put them into another directory instead of the current directory? They make the current directory kinda messy
Ok, yeah, I get you. Currently, we don't support that. We should probably operate that way by default and maybe provide a CL arg. to override it.
I've modified the issue heading to reflect the desired enhancement.
Hi just want to check how's this issue going now. I want to run Macsio with Burst Buffers on Summit. I can write or read files in the burst buffer directory, but I cannot directly cd
into the burst buffer directory. Therefore, if I want macsio to do I/O in that directory, I need to pass the directory to Macsio.
Macsio generates a large number of log files. Is it possible to redirect those files to another directory in the command line?