Find error in dataset(TSB-AD-U idx 277) #37
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After index 500 in the test set, there are no anomaly points present, leading to undefined VUSPR and VUSROC metric values. Please verify the data as this might indicate a potential issue or error in the test dataset.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you very much for your valuable contributions and excellent research efforts!
While evaluating performance metrics, I discovered an issue in the dataset 277_NEK_id_1_WebService_tr_500_1st_17. The data points after index 500 correspond to the test set, but these points contain no anomaly labels. This makes it impossible to compute performance metrics such as VUSPR and VUSROC. Unlike accuracy, precision- and recall-based metrics require both anomaly and normal labels for proper evaluation. Please kindly verify this dataset, as the absence of anomaly labels in the test portion may indicate an unintended data issue or error.