I'm using Processing 3 for generating a Treemap.I installed gicentreUtils and placed TreeMappa file in the library folder of Processing. I'm getting nullPointerException in line:
pTreeMappa = new PTreeMappa(this).
The full code can be found in this
link
Can someone please let me know how to resolve this error.
Thanks
It seems the TreeMapa library hasn't been updated in a few years and internally it may use some Processing code that changed from version 2.x to 3.x (like windows/frames/etc.) which is why the error might occur.
I advise using TreeMapa with Processing 2.2.1 available on the Processing Downloads page
Related
I try to get LDAMallet in gensim working, but get the following error
'C:\...\AppData\Local\Temp\eb09f5_state.mallet.gz' not found
The code
ldamallet = gensim.models.\
wrappers.LdaMallet(mallet_path,
corpus=corpus,
num_topics=5,
id2word=dictionary)
(the num_topics is extremely small, but the test goes over 5 sentences; this has no problem in the regular gensim LdaModel)
thanks,
I was facing the same issue. The error I got was as follows:
IOError: [Errno 2] No such file or directory c:\\users\\...\\appdata\\local\\temp \\d36348_state.mallet.gz.
Each time I tried to run the code the prefix before the underscore would change but the error name would always end with the form "~Some Alphanumeric String~_state.mallet.gz".
I tried to understand the stack trace output in the console. The line just before this error line was as follows:
fileobj = self.myfileobj = __builtin__.open(filename, mode or 'rb')
I googled it and found this particular link. It is a github link where a person raised a different error, but the ending part of his error log was the same as mine. The solution to his error was an upgrade of his smart_open module, which gensim depends on, as the upgrade had fixed the issue. So i checked my smart_open module version and it was 1.4.x, last updated about a year and a half ago, so I upgraded it to the version 1.5.7 and the LdaMallet code works without a hiccup.
Please check if the problem on your end is being caused because of the same reasons.
Hope it helps!
P.S. I also updated my gensim module alongside the smart_open to version 3.4.
I am new to parse and I am trying to figure out how to handle the version number.
I have been deploying some cloud code a bunch of times. So when I last deployed it gave me this message:
Uploading source files
Finished uploading files
New release is named v18 (using Parse JavaScript SDK v1.2.19)
So I thought I could go and hit:
https://api.parse.com/18/functions/someFunctionIWrote
So there I tried to use version 18 because of what I saw after deploying. That does not work and it returns a 404.
So, then I tried to hit:
https://api.parse.com/1/functions/someFunctionIWrote
this works and return the JSON I wanted.
So, what am I missing here?
I thought that every time I deploy the version would match. Do I need to specifically go in and change the current version somehow?
Can somebody help understand how to think about this correctly?
Thank you
If you ran a "parse deploy" it put v18 up there for you the URL stays the same.
The version in cloud can be verified in the terminal by typing: "parse releases"
Using 1.4.1 of BreezeJS we found that some new code added to Isolate ES5 Properties is causing IE 8 to have the following error:
Error getting metadata: Metadata import failed for breeze/breeze/Metadata; Unable to process returned metadata:Object doesn't support property or method 'getPrototypeOf'
We tried using both Uber Proto's getPrototypeOf (https://github.com/daffl/uberproto) and es5-sham (https://github.com/kriskowal/es5-shim) but both result with the same issue.
We also tried removing the regular json.parse and using json2's version with the same results.
Metadata import failed for /breeze/breeze/Metadata; Unable to process returned metadata:Out of stack space
Chrome, Firefox, and IE 9+ work without issue, but IE 8 support is required. We can comment out the line to get it to work:
// isolateES5Props(proto);
But I'm guessing that will cause issues somewhere down the line.
This should be fixed in Breeze v 1.4.2, available now.
I have just upgraded from kendoui.web.2013.1.514 to kendoui.web.2013.2.716 and have noticed that in the parts of the code where I require (through require.js) a certain kendo.culture.xx-XX.min.js file that also an unsuccessful request for kendo.core.min.js happens and I get an error in the console.
This did not happen with kendoui.web.2013.1.514 and I think this part inside the kendo.culture.xx-XX.min.js files might be to blame:
("function"==typeof define&&define.amd?define:function(e,n){return n()})(["../kendo.core.min"]
Also this reference to kendo.core appears to only be present in the minified versions. Note that I already have kendo.web.min.js fully loaded and the app works fine even with the invalid request so is this a bug?
If you are using the bundles (i.e. kendo.web.min.js) then you shouldn't use RequireJS to load them or any culture files.
I'm sorry that the documentation didn't mention it, I just added a section to explain this.
I'm using spymemcached version 2.8.1 to read a cookie object but I keep running into the following exception:
app[web.1]: WARN net.spy.memcached.transcoders.SerializingTranscoder:
Caught CNFE decoding 513 bytes of data
app[web.1]: java.lang.ClassNotFoundException
org.apache.http.impl.cookie.BasicClientCookie
I am using httpclient version 4.1.1: https://dl.dropbox.com/u/6207935/Screen%20Shot%202013-02-05%20at%202.47.19%20PM.png
which has BasicClientCookie class inside of it so I'm not quite sure why it "cannot be found"
Also based on hear-say I think that BasicClientCookie is already marked as Serializable in 4.1.1 but the exact javadocs have been a bit difficult to dig up, honestly ... so its an assumption on my part. Anyway, the exception doesn't seem to be related to serialization but I thought I'd throw this out there for question completeness.
What would be some ideas to resolve this issue?
UPDATE # 1 (Feb 5, 2013)
These may shed some light on the problem:
http://code.google.com/p/spymemcached/issues/detail?id=146 - But when using Heroku I don't know how to obtain the same level of control over my app server's file system ... the way its described here.
http://code.google.com/p/spymemcached/issues/detail?id=155 - Not sure how to get spymemcached to use the custom SerializingTranscoder.
The advice given here worked: http://code.google.com/p/spymemcached/issues/detail?id=155#c2
The only additional bit was testing it out after applying the custom SerializingTranscoder to spymemcached
MemcachedClient mc =
new MemcachedClient(
new ConnectionFactoryBuilder()
.setTranscoder(new CustomSerializingTranscoder()) // makes it take effect
.setProtocol(ConnectionFactoryBuilder.Protocol.BINARY)
...