json, CAN
Posted: Sat Apr 27, 2013 4:10 am
Published notes are attached to this post. Below is the notes that eventually became the presentation.
so the idea is to talk about mongo db in an implementation prepared to log data that doesn't necessarily have a schema. So json is a standard that defines data at a state in time. A sample user of a forum example.
Hi my name is Nathan Sparks and I have 42 posts on the diy_efi board.
Honestly I see the memberships embedded document being deeper but this is for a sample, and I'm trying to keep this simple. In use in engine management this could be used in combination with the network of sensors standard known as CAN. It provides banks of sensors so it would look something like this:
that could be dynamically appended a t value that defines where in the sequence of the logging and that value would be indexed.
so the idea is to talk about mongo db in an implementation prepared to log data that doesn't necessarily have a schema. So json is a standard that defines data at a state in time. A sample user of a forum example.
Hi my name is Nathan Sparks and I have 42 posts on the diy_efi board.
Code: Select all
user
{ _id: BSON_id //a number like 0xb2d91ae6f8416660
{first_name: "Nathan",
last_name: "Sparks",
post_count: 42,
memberships:
{board_name: "diy_efi"}
}
Code: Select all
{
p_0: 15.0
p_1: 0
p_5: duh is this getting boring?
}