Skip to content
This repository was archived by the owner on Oct 21, 2024. It is now read-only.
This repository was archived by the owner on Oct 21, 2024. It is now read-only.

馃悰 [BUG] - quality___language___fasttext_filter function is not utilizing the 'subset' column's text values for filtering#54

Description

@41ow1ives

Environment Settings

default setting

Expected Behavior

The quality___language___fasttext_filter function is not utilizing the 'subset' column's text values for filtering. Although a subset parameter exists in the function, it is not used throughout the logic of the function. However, the function still operates because the language_predict_fasttext function used within automatically targets the 'text' column for filtering. In dataverse testing, the 'text' column is used as the column containing the text. Additionally, there are concerns about potential name conflicts with user input data since the function internally generates columns named labels and scores.

Translate this into easy-to-understand, yet precise English.

Actual Behavior

written above

Reproduction

Simply run with the quality___language___fasttext_filter function without 'text' column.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugSomething isn't workingWIPWork In Progress (someone is working on this issue!)

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions