Do we need a Data-to-Functionality Cookbook?

[clizbe]

I think eventually we might need a cookbook that tells users what data they need to add to gain certain functionalities.
Maybe it would start with the most basic core model, list what parameters (in ESDL and otherwise) it uses, and what they mean in Tulipa.
Then it would have options for other functionalities, and list what data is necessary to implement that functionality.

I don't think we'd do this for every functionality (obviously it's flexible) - but it would be good to know when data is missing or not being used.

Example:
Variable Temporal Resolution
Add temporal resolution in such-and-such-format in such-and-such-file
[more details]

[clizbe]

Functionality will now be explicitly defined by the user, as discussed here:
#461 (comment)

But a cookbook would still be nice so the user doesn't have to fight the validator until they get it right.

[clizbe]

But since we've decided we're doing this, I'll close this Discussion.