SensorBase Blog

Remember that old feature we had in place that would direct you back to your main user page after you had clicked to go to some specific page on sensorbase and it turned out you were logged out and had log back in? Yeah, that’s the one. Well, we decided it was too good of a feature to keep on the site, so we’re replaced it with another which will redirect your back to your intended destination on the site after re-logging back in.  Hopefully, people enjoy this feature a little more : )

If you notice any problems, please let me know!

If anyone tried to add columns to an existing table between Saturday and a few minutes ago, you may have encountered a bug which would not allow you to successfully add the new column. This was discovered and fixed this morning, so you should not be experiencing this problem any longer. This was caused by the fact that we moved the Sensorbase backend to a different machine this weekend and as such, had to reconfigure the MySQL server running on that machine (specifically the user permissions) to be as close to the original machine as possible.

I apologize for any inconveniences this may have caused.

Thanks!

It seems that the XML parsing feature for json location data that takes in something like this:

{”gps_module_name”:”Assisted GPS”,”latitude”:34.069239132371,”longitude”:-118.4429105267, “altitude”:124,”horizontal_accuracy”:60.79863357544,”vertical_accuracy”:65, “fix_time”:”2008-07-08T23:11:34.398000Z”,”speed”:0.5400000214577}

was not working. Going over the code, it seemed that the functionality had not been inserted over a course of rewritting the surrounding code. I added in the functionality again, and it seems to be working fine with the test cases I’ve provided. Let me know if you encounter any problems.

Hey All,

Just  updating everyone on what might be some potential questions about what’s been going on with Sensorbase lately.

From Friday to Sunday, users of Campaignr experienced issues with uploading media content through Campaignr. This was a serious problem that came about as a result from SVN access being set up for all to use. Unfortunately, any media data that was collected between midafternoon on Friday and late afternoon on Sunday was probably not saved. I apologize for this issue, and can assure you that it has been taken care of and will no longer be an issue.

Also, it has been brought up that Sensorbase has been down several times throughout this last week. The first time this occurred it was due to a back up issue brought up while updating the folder structure for database media files. This will not be an issue in the future. Other outages have been caused by our local network operators need to upgrade the firewall which our server is behind. These are short interruptions which shouldn’t have affected many users, but still necessary to state. There should be one such interruption today between 12-12:30pm. As far as I know, it should be the last one for a while.

Lastly, I’m currently investigating a bug in the json_location xml parser; if anyone is trying to use this feature, please ignore the debugging output. I would recommend not trying this feature out until I state that it is fixed anyways.

Some of you may have noticed that clicking on the “get data” button from the table view page in sensorbase resulted in not being able to retrieve your data. This bug was caused by the recent merging of code to the live version of the site. Thanks to Jason for pointing it out, after investigating the problem for a bit, it has now been fixed.

Let me know if there are any other problems! Thanks!

We seem to be having some memory issues that we didn’t have before. I’m not sure if it’s the new implementation or that there’s a whole lot more data coming in now. I have a feeling it’s the latter. We’re looking into some upgrades and possibly a new box, so please bear with us.

Until we get those upgrades, you can still retrieve all of your data. You’ll just have to split it up into like two pieces if you’re going to retrieve more than 100,000 rows of data. For tables with images, I you’ll have to start splitting at around 1,100 rows.

————

Update: We’ve centered in on what’s causing the problem. We’ll be getting some new hardware soon which hopefully gives us the fix.