masonwan / tweentiment Goto Github PK

Use GSON and remove all code related to JSON-lib. And clean the dependencies.

I am planning to add hashtag support by Sunday.

Exception on Line 27 of WordWeight.java.

Detailed output

happy weight: 0.80654895
jsonTxt:  {"mood":"negative","text":"sad","prob":0.920984729039663}
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/commons/lang/exception/NestableRuntimeException
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(Unknown Source)
    at java.security.SecureClassLoader.defineClass(Unknown Source)
    at java.net.URLClassLoader.defineClass(Unknown Source)
    at java.net.URLClassLoader.access$100(Unknown Source)
    at java.net.URLClassLoader$1.run(Unknown Source)
    at java.net.URLClassLoader$1.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at com.sentiment.weight.WordWeight.getWordWeight(WordWeight.java:27)
    at com.sentiment.file.SentimentFileImpl.getWeight(SentimentFileImpl.java:60)
    at com.sentiment.test.FileMain.main(FileMain.java:33)
Caused by: java.lang.ClassNotFoundException: org.apache.commons.lang.exception.NestableRuntimeException
    at java.net.URLClassLoader$1.run(Unknown Source)
    at java.net.URLClassLoader$1.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    ... 15 more
ERROR: JDWP Unable to get JNI 1.2 environment, jvm->GetEnv() return code = -2
JDWP exit error AGENT_ERROR_NO_JNI_ENV(183):  [../../../src/share/back/util.c:838]

It seems that the data collators uses two different JSON libraries, which are Json-lib and Gson. Would you explain it, @mlanusha ?

The packet is very diverse. I tried to use edu.sjsu.tweentiment but I am not sure it's tweentiment or tweetiment?

The app used to be fast on my machine before integration. After integration with classifier, the app has become very slow and takes forever to load on emulator, in some cases it won't even load any tweet. It is NOT suitable for demo unless we do the demo using my phone.

Add a Sentiment140 API connector in order to evaluate our classifier.

This should only be worked on when prototype is done.

The method MainActivity::urlBuilder() would format the URL based on search types such as search 'Tweets', 'Username' and 'hashtag'. This was supported in my Android client before integrating classifier. The method is still there but current implementation of TwitterSearchUrlBuilder doesn't support this.

Please restore this feature so that UI becomes consistent with the Use cases we mentioned in our report and presentation.

For reference: see earlier version of Android client before integration.

Add a Twitter connector class which wraps the Twitter Stream API and grabs new tweets.

Issues:

• OAuth flow needs UI support.
• The response doesn't return.
• The transferred data is too large.
• The end of a single Tweet object is not obvious.

This is necessary so that our won't have large jar libraries in this repository.

Remove all jar files and update .gitignore.

Use different methods or monitor those words which are able to reverse the sentiment value.

I go into tweet or username data, tweet data not load. I am getting a "No more Tweets."

should the content of /res/words.json file remained unchanged all the time? it always shows 26 rows as its content. I am investigating the sentiment results accuracy and came across it.

Provides an interface to let the user authenticate Twitter access for using Search API.

Possible methods to deal with Android OAuth.

1. Use local callback URL
2. Out-of-band or pin-based OAuth