feat: Dataset#category

[tristan-f-r]

• Depends on test: dataset #326

This is a short PR that just adds the Dataset#category parameter and parses it/stores it without usage, as I want to make sure that we agree on category over categories: the latter, while more general, seems biologically useless.

[read-the-docs-community]

Documentation build overview

📚 spras | 🛠️ Build #29861638 | 📁 Comparing 965f87c against latest (6e8cc04)

🔍 Preview build

Show files changed (8 files in total): 📝 5 modified | ➕ 0 added | ➖ 3 deleted

File	Status
genindex.html	📝 modified
htcondor.html	➖ deleted
index.html	📝 modified
py-modindex.html	📝 modified
contributing/patching.html	➖ deleted
fordevs/modules.html	📝 modified
fordevs/spras.config.html	➖ deleted
fordevs/spras.html	📝 modified

[ntalluri]

Could you update the config files so we can what the use of category label would look like? Also is a user now required to add a dataset category to each dataset they put in a config?

[tristan-f-r]

The Optional tag in the schema means that category would be optional.

[tristan-f-r]

Could you update the config files so we can what the use of category label would look like?

I'll avoid this in the main config.yaml until we have sample data for a new dataset. I'll add accompanying documentation once we have some way to have runs only run on specific dataset categories.

[agitter]

I'm missing what we want to support with this category attribute. We want to list many datasets in a single config file and then somewhere else say only run on datasets where category=X? That was part of #309, but I'm not seeing the advantages of doing that all within a single config file.

[tristan-f-r]

This would be useful for cross-dataset-category analysis (i.e. unified statistics that check how well algorithms do on certain dataset categories than other categories). This is currently no longer useful for parameter tuning.