05 August 2013

my IRAD Proposal slide five note

Here is my fifth slide note in my Human Health Graph proposal This isn’t a solution graphic as much as it is representation of the scalar (as opposed to an anthropometric or vector) human health graph. The area of the parallelogram represents the 2-D view of data volume possible during a life-death time. I need to illustrate a 3rd dimension to really bring the volume of data by type per unit type to life. Whether the data is measured or calculated from sensors | detectors | meters of any type, networked and coupled or not, in, on or off the body doesn’t matter. The reader needs to see a color map of my estimate of the number of measurands known to man as a function of time versus the number of measurements occurring. In the 2D graph, a dot would appear for one or more measurements or calculations during that interval. I want the baseline time interval to be one second meaning 3.15576 billion-second baseline (i.e., 100 Years)! Moreover, if you assume the number of affordable, probable intelligent simultaneous measures and calculated parameters for the human body & mind over all spatial and temporal scales during a century of life is 300 on average for any individual, each measurement-calculation second, consuming a centi-joule, weighing a megabyte (compressed and encrypted), spread over 100 kHz, and consuming one million instructions, implies the 100-Yr human health graph will consume 30 megajoules, weigh approximately 4 petabytes (10^15) and execute at least a peta instructions and floating point operations. Some unmetered amount of air time (RF bandwidth) will be used for subscription-based (fee for access) biotelemetry and biotelematics during the same life-death time. The solution graph is found in previous post from last year. I'm working on an H-Anim humanoid to bring the idea to life. developing software to take most of the friction out of various quantified self real-time measurement threads to H-Anim files (XML documents in an native XML database or catalog of databases) is one hard part of this project.

No comments: