pentominos:pentominos
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
pentominos:pentominos [2009/02/12 08:38] – deva | pentominos:pentominos [2009/02/26 09:45] – deva | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | =====Pentominos - Data Collection System ===== | + | ======Pentominos - Data Collection System ====== |
+ | =====Overview===== | ||
+ | The Pentominos project consists of several sub-projects, | ||
+ | Here is a list of the current sub-projects: | ||
+ | * [[pentominos: | ||
+ | * [[pentominos: | ||
+ | * Upload Server - Journal writer. | ||
+ | * Pidiod - The uid => patient ID mapper. | ||
+ | * Pidio - The uid => patient ID mapper client (numpad/ | ||
+ | |||
+ | ====LUA elements==== | ||
+ | LUADataValidator | ||
+ | LUADataParser | ||
+ | |||
+ | |||
+ | ====Snaask==== | ||
+ | When an apparatus is connected the following must be crafted: | ||
+ | * Feed parser so file and conf. | ||
+ | * Artefact validator / identifier. | ||
+ | * Makes superficial parsing of the data to identify whether the data is valid. | ||
+ | * Figure out what classes are contained in the data, and report this. | ||
+ | * Artefact interpretation | ||
+ | * Parses and interprets the data, translating it into some output language (eg. xml) | ||
+ | |||
+ | (data, class) => [lua] Parser -> [lua] Interpretation -> [lua/c] Tree structure -> [c] language filter -> network | ||
+ | |||
+ | |||
+ | ====Patient registration==== | ||
+ | The system stores data. These data is connected to a patient ID, a timestamp, a location and an apparatus.\\ | ||
+ | Getting the patient ID is a non-trivial task at best.\\ | ||
+ | See the [[pentominos: | ||
+ | |||
+ | ====RFID tag project==== | ||
+ | [[pentominos: | ||
====Network communication (protocol)==== | ====Network communication (protocol)==== | ||
All network communication are done via XML documents.\\ | All network communication are done via XML documents.\\ | ||
Line 17: | Line 51: | ||
[[pentominos: | [[pentominos: | ||
+ | |||
====Data types==== | ====Data types==== | ||
Line 22: | Line 57: | ||
How to make a query that will hit this multi-data block?\\ | How to make a query that will hit this multi-data block?\\ | ||
Solutions: | Solutions: | ||
- | * Make client send data one time pr. data type, thus storing it in the db under two different classes. | ||
- | * //Pros//: | ||
- | * We don't need to make any changes to the server code. | ||
- | * //Cons:// | ||
- | * The client needs to parse the data (no longer thin). | ||
- | * The data are stored multiple times in the file system. | ||
- | |||
- | * Make validator detects which types of data are contained in the block, adding a list of type tags in the database. | ||
- | * //Pros:// | ||
- | * The data are only stored once in the file system. | ||
- | * //Cons:// | ||
- | * Needs to query an entry in a list in the db. | ||
- | |||
* Make the validator insert one entry in the db for each data type, referring to the same data block (file). | * Make the validator insert one entry in the db for each data type, referring to the same data block (file). | ||
- | | + | * The data are only stored once in the file system. |
- | | + | * We don't need to make drastic changes to the server code (or client for that matter). |
- | * We don't need to make drastic changes to the server code (or client for that matter). | + | |
- | * //Cons:// | + | |
- | * bleh | + | |
====Links==== | ====Links==== |
pentominos/pentominos.txt · Last modified: 2010/01/29 08:46 by deva