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
Today the save parameter of EvalAlgorithmInterface.evaluate() is just a boolean.
From hunting around I found that the output path is taken either from an environment variable or else a default under /tmp... And that it should also be overrideable by setting the obviously-supposed-to-be-private property eval_algo._eval_results_path.
IMO it's harder and less obvious than it should be for a developer using the library to save results in a folder they want. It'd be much easier if we could support eval_algo.evaluate(save="my/cool/folder") and ideally automatically create the provided folder if it doesn't already exist?
The text was updated successfully, but these errors were encountered:
Thanks for bringing this up @athewsey! What you said seems to make absolute sense. We will take another look at this decision, why it was done this way, and if there isn't one, we will update it soon.
Today the
save
parameter ofEvalAlgorithmInterface.evaluate()
is just a boolean.From hunting around I found that the output path is taken either from an environment variable or else a default under /tmp... And that it should also be overrideable by setting the obviously-supposed-to-be-private property
eval_algo._eval_results_path
.IMO it's harder and less obvious than it should be for a developer using the library to save results in a folder they want. It'd be much easier if we could support
eval_algo.evaluate(save="my/cool/folder")
and ideally automatically create the provided folder if it doesn't already exist?The text was updated successfully, but these errors were encountered: