remove max.csv
cgnitash opened this issue · 1 comments
cgnitash commented
There might be a good reason to have max.csv only generated by Archvists when specific Optimisers are used.
This might be a large change with ripple effects for implementation.
Thoughts?
cliff-bohm commented
Just to clarify, the current behavior is that optimizers return an MTree, and this may be a null ptr.
If it's a null ptr then the archivist knows not to make a max file. The question really is: Is a max.csv a general enough case to justify having it in Archivist. The alternative would be to design optimizers so that they output a max.csv (or other) file if it makes sense for that optimizer.