Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Results of running SentimentAnalyzer() on Amazon Reviews Dataset. #187

Open
mdvsh opened this issue Jan 17, 2020 · 0 comments
Open

Results of running SentimentAnalyzer() on Amazon Reviews Dataset. #187

mdvsh opened this issue Jan 17, 2020 · 0 comments

Comments

@mdvsh
Copy link

mdvsh commented Jan 17, 2020

Background

Under Google Code-In, I used the sentiment analysis model in TextAnalysis.jl to analyse the amazon reviews dataset.. I performed basic text pre-processing to increase the metrics of the model. Some tasks undertaken were:

  • stemming words in each review
  • removing corrupted characters
  • removing definite and indefinite articles

I also found that remove_numbers!() (another pre-processing function mentioned in the Docs) gave an error on running. On further inspection, I found that it isn't still implemented in the src/preprocessing.jl folder. It is an issue worth looking into.

Also, a BoundsError occurred in the midst of the run.

BoundsError: attempt to access 32×5000 Array{Float32,2} at index [Base.Slice(Base.OneTo(32)), 5001]

This didn't effect the running and the results that I get are presented below.

Result

I learnt how precision, recall and f1score are different metrics for measuring how well the model performs and was a wonderful learning experience.

Precision : 0.583117838593833
Recall : 0.5144996465068449
F1Score : 0.5466638895622987

Related To:

  1. BoundsError in sentiment analysis #160
  2. Testing the efficiency of Sentiment Analysis models #185
  3. Better sentiment analysis model #84

cc @Ayushk4 @aviks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant