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
Placeholder issue for dataset as configs as mentioned in #15
Also related to #45
Why?
It will be easier to have reproducible datasets. For example, I can share a config with another person, she/he can create the same dataset using just the config file.
No need to write lengthy python scripts/notebooks to generate data. The most frequent use case for this package is probably generate a diverse dataset with all sorts of models. Writing a script from scratch to generate a dataset is tedious.
Proof of Concept
Let's do a small pilot experiment to show if we can achieve the following.
Can we fully define a dataset with a pinned package version and a config file, e.g., yaml?
Placeholder issue for dataset as configs as mentioned in #15
Also related to #45
Why?
Proof of Concept
Let's do a small pilot experiment to show if we can achieve the following.
Experiment: #47
The text was updated successfully, but these errors were encountered: