Closed PhilipMay closed 1 month ago
Would also appreciate this feature (and obviously someone thought of this already, given the existence of VERSION). 👍
Hi! Yep, we'll need to add the mechanism again - we had removed it to simplify the code, and because we did not want to fix any task version while still being in alpha.
@clefourrier do you want me to suggest a PR or do you want to implement it?
If you have the time to open a PR I'd be grateful! You'll need to add a default version argument to the TaskConfig, and edit the task_table.jsonl to set "version" to 0 there for all tasks, and edit your own to pass it to 1.
If you have the time to open a PR I'd be grateful! You'll need to add a default version argument to the TaskConfig, and edit the task_table.jsonl to set "version" to 0 there for all tasks, and edit your own to pass it to 1.
I started here: #181
This is done with PR #181. Closing...
The
LightevalTask
class has a VERSION. This is not configurable and fixed to 0. See:https://github.com/huggingface/lighteval/blob/11b48333b46ecd464cc3979de66038c87717e8d6/src/lighteval/tasks/lighteval_task.py#L166
I think in the results table the version number is also displayed. See:
If I slightly change the task or the prompt (e.g. #171 ) - it would be nice to increase the version number. Should this be changed / added?