jsonlab

[wandell]

@benjamin-heasly

There is now a github repository for jsonlab. The newer version is supposed to be 2x faster than the original one we have been using.

So, I made a branch (nojsonlab) that I will use for a while. I will include the github jsonlab repository on my path. If it works out OK, then perhaps we can switch over. I think we would put jsonlab repository into your Toolbox Toolbox method, which I am looking forward to using.

[benjamin-heasly]

That sounds interesting. I can also try setting up nojsonlab on my machine and running the automated test suite.

[wandell]

I have been running OK for a couple of days. So far, so good.

[benjamin-heasly]

That's great. 👍

I ran the automated tests on the nojsonlab branch, with jsonlab v1.2 also on my path. Overall, it was good. I had to make a couple of little changes to accommodate new behavior:

• loadjson() started returning logical true/false instead of numerical 1/0.
• savejson() started erroring when passed an empty string, or empty JSON values like [].

I put these changes in the nojsonlab branch.

I also added jsonlab v1.2 to the public toolbox configuration for RemoteDataToolbox. So now tbUse('RemoteDataToolbox') will bring in jsonlab and put it on the path after RemoteDataToolbox.

[JWinawer]

Copying part of a conversation from the vistasoft issues site re jsonlab, from @wandell

"In the meantime I found two more things. First Matlab has now incorporated its own json tool. I haven't tried it. Second, I found a MUCH faster json tool called jsonio. I am using that tool extensively as part of the scitran work. It is an hour work (for me) to convert from json lab to jsionio.

But maybe we should use Matlab's version. Just not sure."