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
In distilabel v1.0.0 we included the task TextGeneration and at the last moment we decided to include support for an already formatted chat like object i.e. a list of dicts with the keys role and content; but that's counter intuitive since to use TextGeneration with say the column messages one would need to always provide the input_mappings and the logic of format_input had some conditionals to handle that.
Now, since v1.1.0 we decided to include a separate task for that named ChatGeneration that indeed expects a column named messages that will check that's compatible with the expected format and then call the process method with that. This is not also more intuitive, but also the cost of maintaining it is low.
Additionally, this let us define the optional input system_prompt in TextGeneration, meaning that if the system_prompt is available and the use_system_prompt flag is set to True, then the system_prompt will be included as the first message before the instruction.
So on, in v1.1.0 a DeprecationWarning will be raised when using TextGeneration for ChatGeneration, encouraging the user to use ChatGeneration instead, while showing a DeprecationWarning to be applied in v1.2.0.
The text was updated successfully, but these errors were encountered:
Description
In
distilabel
v1.0.0 we included the taskTextGeneration
and at the last moment we decided to include support for an already formatted chat like object i.e. a list of dicts with the keysrole
andcontent
; but that's counter intuitive since to useTextGeneration
with say the columnmessages
one would need to always provide theinput_mappings
and the logic offormat_input
had some conditionals to handle that.Now, since
v1.1.0
we decided to include a separate task for that namedChatGeneration
that indeed expects a column namedmessages
that will check that's compatible with the expected format and then call theprocess
method with that. This is not also more intuitive, but also the cost of maintaining it is low.Additionally, this let us define the optional input
system_prompt
inTextGeneration
, meaning that if thesystem_prompt
is available and theuse_system_prompt
flag is set toTrue
, then thesystem_prompt
will be included as the first message before theinstruction
.So on, in v1.1.0 a
DeprecationWarning
will be raised when usingTextGeneration
forChatGeneration
, encouraging the user to useChatGeneration
instead, while showing aDeprecationWarning
to be applied in v1.2.0.The text was updated successfully, but these errors were encountered: