0.14.0 Release Notes
This version includes improvements of using the properties (improved properties screen, multiple columns in data screen, improved retrieval relevance property), output text difference highlighting, visibility for the used tokens, and more features, stability and performance improvements that are part of our 0.14.0 release.
0.13.0 Release Notes
This version includes enhancements to the version comparison, additional similarity metrics: ROUGE and BLUE, expansions to the insights mechanism, and more features, stability and performance improvements that are part of our 0.13.0 release.
0.12.0 Release Notes
This page includes updates from our 0.12.0 Release, which includes new features, stability and performance improvements.
0.11.0 Release Notes
This page includes updates from our 0.11.0 Release, which includes new features, stability and performance improvements.
0.10.0 Release Notes
This page includes updates from our 0.10.0 Release, which includes new features, stability and performance improvements.
0.9.0 Release Notes
This page includes updates from our 0.9.0 Release, which includes new features, stability and performance improvements.
0.8.0 Release Notes
This page includes updates from our 0.8.0 Release, which includes new features, stability and performance improvements.
0.7.0 Release Notes
This page includes updates from our 0.7.0 Release, which includes new features, stability and performance improvements.
0.7.0 API Changes (breaking 0.6.0)
Summary of Changes
ext_interaction_id
was changed intouser_interaction_id
- This id must be unique within a single version and can be set by the consumer (otherwise deepchecks will generate one for you). This is the only unique id of the interaction.- We've made some name changes -
user_input
is nowinput
, andresponse
is notoutput
. Additional changes that affect SDK and REST API users are listed below.- We've added an option to set the annotation to
None
and differentiated it fromUnknown
.
None
- Deepchecks will try to estimate the annotation.Unknown
- the interaction input/output where reviewed, and the annotation for that interaction can't be defined as "Good" or "Bad". Deepchecks will not try to estimate an annotation for this sample.