<div dir="ltr">I've created a ticket for myself to make sure I do the proper smoke-testing: <a href="https://dev.guardianproject.info/issues/1772">https://dev.guardianproject.info/issues/1772</a></div><div class="gmail_extra">
<br clear="all"><div><div>++++++++++++++++++++++++++</div><div>Research Fellow, Head of Metadata</div><div><a href="https://guardianproject.info" target="_blank">The Guardian Project</a></div><div><br></div><div>pgp: 0xA4469630</div>
<div>twitter: @harlo</div></div>
<br><br><div class="gmail_quote">On Sat, Aug 24, 2013 at 9:16 AM, David Oliver <span dir="ltr"><<a href="mailto:david@olivercoady.com" target="_blank">david@olivercoady.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I'm thrilled to hear this, and have visions of little JQuery animations dancing in my head.<div><br></div><div>Carrie, we'll talk soon.</div></div><div class="gmail_extra"><div class="im"><br clear="all">
<div>
David M. Oliver | <a href="mailto:david@olivercoady.com" target="_blank">david@olivercoady.com</a> | <a href="http://olivercoady.com" target="_blank">http://olivercoady.com</a> | <a href="http://dmo.tel" target="_blank">http://dmo.tel</a> | @davidmoliver | <a href="tel:%2B1%20970%20368%202366" value="+19703682366" target="_blank">+1 970 368 2366</a></div>
<br><br></div><div><div class="h5"><div class="gmail_quote">On Sat, Aug 24, 2013 at 9:02 AM, Harlo Holmes <span dir="ltr"><<a href="mailto:harlo@guardianproject.info" target="_blank">harlo@guardianproject.info</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">So far, it's worked this way:<div><br></div><div>When our user clicks the camera button, they're directed to InformaCam's camera-management activity, which before launching the user's camera, starts up our sensors and starts a log for those sensor readings. Once this log is created, and all the sensors have started up and are successfully logging, the user is passed to their on-board camera app. As the user takes their photos/videos, each new media item is packaged with a reference to the sensor log file for later. FInally, when the user exits the on-board camera activity, they're brought back to our custom activity which shuts down the sensors, and seals the logs. </div>
<div><br></div><div>So, if a researcher wanted to gauge a user's movement as they took a photo or video, that researcher already has several seconds of sensor data captured before capture, during capture, and after capture; it's up to the researcher (us? j3m-scan!) to properly window that data.</div>
<div><br></div><div>As for resolution, currently, its resolution is not fine enough, as Hans notes. Accelerometer and gyroscope etc currently have a sample rate of 500ms. However, this can be changed very easily because the rate at which each sensor logs is set in a config file and it's a matter of changing that long (and making sure we don't run into out-of-memory errors because of the increased number of data points.) I'm not too concerned about battery life, though, because it's not as if the sensors are running continuously as you use the app; this only happens while the user is making media, which is a relatively short duration. Also, the android sensor API is optimized for gaming, so it should be fine for this minimal use case.</div>
<div><br></div><div>Thanks,</div><div>Harlo</div></div><div class="gmail_extra"><br clear="all"><div><div>++++++++++++++++++++++++++</div><div>Research Fellow, Head of Metadata</div><div><a href="https://guardianproject.info" target="_blank">The Guardian Project</a></div>
<div><br></div><div>pgp: 0xA4469630</div><div>twitter: @harlo</div></div>
<br><br><div class="gmail_quote"><div><div>On Fri, Aug 23, 2013 at 4:42 PM, David Oliver <span dir="ltr"><<a href="mailto:david@olivercoady.com" target="_blank">david@olivercoady.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
<div dir="ltr">I think there's a technology side and a "user scenario" side to this - and I don't want this to be treated like an open-ended problem/issue.<div><br></div><div>Here's the scenario I want to "solve": A photograph is a snapshot of a scene in time. So, for photographs, we need the metadata to align with that moment in time. I can imagine that most metadata we're tracking can also be "snapshotted". BUT, with the accelerometer, the snapshot (single reading) is useless - you need more than one reading to show a delta/change. While you could track accelerometer every 1/10 second, say, and then store readings in a circular queue (of, say, the last 10 seconds), that continuous reading would drain the device's battery. But, to be valid, the readings have to be in the same timeframe as the photo. So,.....open question.</div>
<div><br></div><div>I suppose this is easier for video since you've got a start/stop time (and OS event, likely) allowing you to start/stop accelerometer capture.</div><div><br></div><div>I think if we have geo-position, compass, and accelerometer then you make a nice graphic depiction of positionality and motion at time of capture.</div>
<div><br></div><div>Dave</div></div><div class="gmail_extra"><br clear="all"><div>David M. Oliver | <a href="mailto:david@olivercoady.com" target="_blank">david@olivercoady.com</a> | <a href="http://olivercoady.com" target="_blank">http://olivercoady.com</a> | <a href="http://dmo.tel" target="_blank">http://dmo.tel</a> | @davidmoliver | <a href="tel:%2B1%20970%20368%202366" value="+19703682366" target="_blank">+1 970 368 2366</a></div>
<br><br><div class="gmail_quote"><div><div>On Fri, Aug 23, 2013 at 3:09 PM, Nathan of Guardian <span dir="ltr"><<a href="mailto:nathan@guardianproject.info" target="_blank">nathan@guardianproject.info</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
Adding Harlo to this thread, and cc'ing the list, as this is an<br>
important general topic.<br>
<div><br>
On 08/23/2013 03:06 PM, David Oliver wrote:<br>
> Here's one thing I want to know to aid in this process: As I understand<br>
> it, having a single accelerometer reading is useless for determining<br>
> anything about movement, it is the comparative readings that are important.<br>
> Using, say, 3 readings, you could assert something about motion. But,<br>
> InformaCam does not know "I should collect an accelerometer reading just<br>
> before the picture is taken, then one during, then one after - since it<br>
> does not know when media is created. Yet, you can't possibly gather<br>
> accelerometer (and/or compass) in real time all the time and then wait to<br>
> use it.......so what does InformaCam actually do?<br>
</div>The question is then, how/when are we logging accelerometer data, and<br>
what can or should we infer from it?<br>
<br></div></div><div>
_______________________________________________<br>
Ssc-dev mailing list<br>
<br>
Post: <a href="mailto:Ssc-dev@lists.mayfirst.org" target="_blank">Ssc-dev@lists.mayfirst.org</a><br>
List info: <a href="https://lists.mayfirst.org/mailman/listinfo/ssc-dev" target="_blank">https://lists.mayfirst.org/mailman/listinfo/ssc-dev</a><br>
<br>
To Unsubscribe<br>
Send email to: <a href="mailto:Ssc-dev-unsubscribe@lists.mayfirst.org" target="_blank">Ssc-dev-unsubscribe@lists.mayfirst.org</a><br></div>
Or visit: <a href="https://lists.mayfirst.org/mailman/options/ssc-dev/david%40guardianproject.info" target="_blank">https://lists.mayfirst.org/mailman/options/ssc-dev/david%40guardianproject.info</a><br>
<br>
You are subscribed as: <a href="mailto:david@guardianproject.info" target="_blank">david@guardianproject.info</a><br>
</blockquote></div><br></div>
<br>_______________________________________________<br>
Ssc-dev mailing list<br>
<br>
Post: <a href="mailto:Ssc-dev@lists.mayfirst.org" target="_blank">Ssc-dev@lists.mayfirst.org</a><br>
List info: <a href="https://lists.mayfirst.org/mailman/listinfo/ssc-dev" target="_blank">https://lists.mayfirst.org/mailman/listinfo/ssc-dev</a><br>
<br>
To Unsubscribe<br>
Send email to: <a href="mailto:Ssc-dev-unsubscribe@lists.mayfirst.org" target="_blank">Ssc-dev-unsubscribe@lists.mayfirst.org</a><br></div></div>
Or visit: <a href="https://lists.mayfirst.org/mailman/options/ssc-dev/harlo.holmes%40gmail.com" target="_blank">https://lists.mayfirst.org/mailman/options/ssc-dev/harlo.holmes%40gmail.com</a><br>
<br>
You are subscribed as: <a href="mailto:harlo.holmes@gmail.com" target="_blank">harlo.holmes@gmail.com</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
Ssc-dev mailing list<br>
<br>
Post: <a href="mailto:Ssc-dev@lists.mayfirst.org">Ssc-dev@lists.mayfirst.org</a><br>
List info: <a href="https://lists.mayfirst.org/mailman/listinfo/ssc-dev" target="_blank">https://lists.mayfirst.org/mailman/listinfo/ssc-dev</a><br>
<br>
To Unsubscribe<br>
Send email to: <a href="mailto:Ssc-dev-unsubscribe@lists.mayfirst.org">Ssc-dev-unsubscribe@lists.mayfirst.org</a><br>
Or visit: <a href="https://lists.mayfirst.org/mailman/options/ssc-dev/harlo.holmes%40gmail.com" target="_blank">https://lists.mayfirst.org/mailman/options/ssc-dev/harlo.holmes%40gmail.com</a><br>
<br>
You are subscribed as: <a href="mailto:harlo.holmes@gmail.com">harlo.holmes@gmail.com</a><br>
<br></blockquote></div><br></div>