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
{{ message }}
This repository has been archived by the owner on Nov 21, 2022. It is now read-only.
This is fine for the "general" cases, however for the specific modules for datasets, it looks cumbersome:
...
dm=WMT16TranslationDataModule( # I have to choose the WMT16 classcfg=TranslationDataConfig(
dataset_name="wmt16", # I have to pass the name of the dataset as well? why is this not the default?
...
),
tokenizer=tokenizer,
)
A solution would be to introduce a config class like below, however this adds even more lines.
馃殌 Feature
Currently, the process of creating a module looks like such:
This is fine for the "general" cases, however for the specific modules for datasets, it looks cumbersome:
A solution would be to introduce a config class like below, however this adds even more lines.
I suggest we opt to remove configs entirely, and just rely on the modules:
From my understanding, this is supported by hydra, but all
cfg
objects will be converted into parameters.The text was updated successfully, but these errors were encountered: