* Make system messages optional
Also use the `maybe_insert_system_message` in dpo setting
* add `auto_insert_empty_system_msg` flag
* add `auto_insert_empty_system_msg`
* add auto_insert_empty_system_msg
* Update src/alignment/configs.py
Co-authored-by: lewtun <lewis.c.tunstall@gmail.com>
* make style
---------
Co-authored-by: lewtun <lewis.c.tunstall@gmail.com>
* add check before inserting system message
* change in-place for consistency
* fix unit test
---------
Co-authored-by: Nathan Azrak <nazrak@atlassian.com>
* Update data.py
The docs state that the `shuffle` parameter in `mix_datasets` from `data.py` controls `Whether to shuffle the training data`, but then in the code if `shuffle` is set to `True` it also shuffles the test data. This small change makes the functionality consistent with the docstring. (If you instead want to keep the functionality the same, then we should update the docstring).
* Update data.py
Reverted to the original code structure but updated the docstring.
* Update docstring in `get_dataset` and `mix_datasets`
Updated docstrings to reflect the fact that `shuffle` being set to `True` leads to shuffling of both the training and testing/validation data.
Bram Vanroy