Closed frostedoyster closed 3 weeks ago
@DavideTisi I think so. The idea is to use train
and valid
everywhere in the code, but training
and validation
for anything user-facing (yaml/CLI)
I don't love valid
as a name, since it's not a verb/action noun like train
. I could do validate
if you want something shorter than validation
.
Given the context, valid is still clear. Many people even use val in the code
I think I would prefer val
over valid
(since it does not have a meaning on it's own), if that works for you.
Let's go for val
I don't think it's a good idea to change is_training
to is_train
because it loses some meaning (is training or is trained or ...?).
Regarding the last comment, that is not user-facing from the CLI (or related yaml files).
Okay but then I would go for ["train", "val"]
. Also, can you rebase against the main branch?
Closes #240
📚 Documentation preview 📚: https://metatrain--248.org.readthedocs.build/en/248/