elenasamuylova

Hi @tugcegns, Thanks for reporting the bug! Could you share: - Which evidently version are you using? - Are you able to show the report in the notebook? Or the...

Thanks @tugcegns - the error trace is helpful! Appreciate you reporting the bug. Let us dig a bit deeper to test what might be wrong. We cannot immediately reproduce it...

Hi @tugcegns, We ran on all our test datasets and unfortunately cannot reproduce the error. 1. Is there a chance you can share a small example dataset for which the...

Hi @tugcegns, Thanks for sharing! I reproduced your code on your example dataset in Colab. Here it is: https://colab.research.google.com/drive/1H4SMRHzWC_GFfqGAnhMTQGUtpeQ6Rlmc?usp=sharing It appears to work correctly. To double-check, did you import NLTK...

Glad it is solved @tugcegns!

Hi @tbaptista, thanks for reporting! Could you try building Evidently from main and see if the issue persists? This bug should have been fixed recently but is not yet released...

Thanks for checking @tbaptista! This will be published next week together with the next release.

Hi @sandeeps311, this is now available in the latest release https://github.com/evidentlyai/evidently/releases/tag/v0.2.8 as `small_distribution` in the JSON output.

Hi @EgorKraevTransferwise, Yes - currently, Evidently uses pandas. We know of users running Evidently on 100s thousand or low million rows per batch. Since the computation happens in memory, the...

Thanks for reporting @userkkw, we will take a look!