Always Not In Knowledge Base using te3-large

  • Resolved samymsa

    (@samymsa)


    1 month, 3 weeks ago

    Hi!

    Using openai TE3 large model, content is always shown as Not In Knowledge Base.

    Source of the problem: In wp-content/plugins/mxchat-basic/admin/class-knowledge-manager.php the mxchat_scan_pinecone_for_processed_content function uses hardcoded 1536 dimension to generate a random unit vector. However, TE3 large dimension is 3072.

    Changing the dimension manually to 3072 fixed the issue. Hope you can find a robust way to fix it.

    Can I use MxChat with TE3 large reliably, or should I better use another embedding model ?

    Best,
    Samy

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support m4xw3ll

    (@m4xw3ll)

    1 month, 3 weeks ago

    hi @samymsa,

    Yes you can. I will review and confirm what you mentioned above. If it is indeed incorrect it will be fixed and released in an update either Sunday or Monday.

    I will update you once I’ve reviewed and thanks for reporting.

    Maxwell

    Plugin Support m4xw3ll

    (@m4xw3ll)

    1 month, 3 weeks ago

    Hi @samymsa,

    Thanks again for reporting. I at first thought you meant the chatbot was always responding with information “not found in knowledge database” but after researching closer and reviewing I see now that you mean in the WordPress import option even when the data is added it shows up as “Not in knowledge” label because the scan is using the hard coded dimension!

    Thanks for reporting. This will be fixed in a version likely released tomorrow.

    Thread Starter samymsa

    (@samymsa)

    1 month, 3 weeks ago

    Hi @m4xw3ll,

    The issue is indeed related to the WordPress import option, sorry if my explanation wasn’t clear enough.

    Anyway, thanks for the update!

    Plugin Support m4xw3ll

    (@m4xw3ll)

    1 month, 2 weeks ago

    hi @samymsa,

    Fixed in v3.1.0 just released.

    thanks again,

    Maxwell

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.