GatherYourSenses

[Harshad RJ]

All,

I just released version 2.0 of GatherYourSenses. The main updates are:

• Ability to "connect" to your Local Android device. That is, you can see how your Android's sensors behave (and not just remote sensors).
• Ability to set the duration of calibration. The app uses a moving window of specified time, when collecting data for calibration. Hand held calibration can usually be done quicker, while calibration when attached to a telescope might require more time. Hence, the choice of duration.

Frankly, this app has taken a life of its own. I have now learnt a lot about how the sensors behave in practice. I will soon be able to bring this (in a simplified form) to SkEye.

I would appreciate if you can try this on your device and send me feedback as described below.

The app is in beta and can be downloaded from this link:
https://play.google.com/apps/testing/com.lavadip.sensegather

Here's a quick walkthrough for using the latest version of GYS:

• If connecting to Wiced Sense, make sure Wiced Sense is powered on and paired with your Android.
  
• Start the GYS application
• Press "Connect..." button and choose "Local Android" or the "Wiced Sense" device
  
• Press "Calibrate magnetometer"
• Choose duration for calibration. For hand-held calibration, the default of one-minute is sufficient. When attached to telescope you can choose a longer duration.
  
• Move your device (Android / Wiced Sense) around slowly.
  If hand-held, move it in figure 8 movements while rotating gently. Imagine a laser beam coming out of the Wiced Sense. The goal is to point it in as many directions as possible.
  If mounted on a telescope, you can make full 360 degrees one axis, while keeping the other axis steady. For example, on an Alt-Azm mount, hold the altitude steady and make a 360 degree Azimuth rotation. Then switch to a different altitude and repeat.
  
• Click "stop calibration" when you are done.
• Observe the plots.
  The ones on the left are raw. They might be off-center and elliptical.
  The ones on the right are after calibration. They should appear centered around the origin and spherical.
  
• Optionally, click "save" button to store the sensor data of that session into a file.
• Optionally, capture a screenshot and mail it to me along with the sensor data file.

​best,​

--

Harshad RJ

[Brewster LaMacchia]

Hi Harshad,

Just FYI: I tried this (handheld) on my Nexus 5 (6.0.1). App kept crashing trying to calibrate - finally figured out that I have my phone set to autorotate the display and when it did that the app would stop. Forced the phone to portrait mode and all is well.

Brewster

[Harshad RJ]

Ah, thanks for the heads up Brewster.

My phone is always in forced portrait mode so hadn't noticed it.

I believe Starman experienced a similar crash. Will fix and publish an update soon.

--
You received this message because you are subscribed to the Google Groups "SkEye Discussions + Announcements" group.
Visit this group at https://groups.google.com/group/skeye.

--

Harshad RJ

[Harshad RJ]

Fixed the auto-rotation problem and published a new release (2.1). The app now sticks to portrait mode always.

--

Harshad RJ

[Starman]

Thanks Brewster, my Nexus is most always on auto-rotate, I never would have thought of that being a problem!

[Brewster LaMacchia]

Hi Harshad,

After moving the phone around, stopping calibration, and if I hit save the app exits and I get the do you want to report this box. Does that crash dump go back to you if I click OK? I'm not familiar with android app development.

Brewster

[Brewster LaMacchia]

Hi Harshad,

Ran out and did a quick test, first handheld (fitness 82.8%) and then on the bracket (78.1%).  Don't know if that's a meaningful difference, and I did this in a hurry, but I need to experiment with the bracket some more.

HANDHELD:
 



BRACKET:

[Harshad RJ]

Hi,

Yes, the crash report should come to me (via google's services); please do send it. Thanks!

--

You received this message because you are subscribed to the Google Groups "SkEye Discussions + Announcements" group.
Visit this group at https://groups.google.com/group/skeye.

--

Harshad RJ

[Harshad RJ]

Brewster,

The difference between the fitness (78.x and 82.x) isn't much. But in general, the numbers are on the lower side. I get similar numbers on my Nexus 4 when I am indoors. However, if I go outdoors I see a 99% fitness score!

I have fixed the crash-during-save and published an update (version 2.2). When you get the chance, please update and send me the attachments off-list.

Thanks!

--
You received this message because you are subscribed to the Google Groups "SkEye Discussions + Announcements" group.
Visit this group at https://groups.google.com/group/skeye.

--

Harshad RJ

[Harshad RJ]

​Found something interesting today.​ I tried calibration on local android sensors after getting up in the morning (a fresh start for the sensors). The first two attempts yielded very poor results; fitness was about 30%.

But after the two trials, the results were back again into 98% fitness.

Take away: my Nexus 4 takes a couple of minutes of movement to calibrate itself, and after that it does a pretty good job.

On Fri, Aug 26, 2016 at 1:02 AM, Harshad RJ <harsh...@gmail.com> wrote:

The difference between the fitness (78.x and 82.x) isn't much. But in general, the numbers are on the lower side. I get similar numbers on my Nexus 4 when I am indoors. However, if I go outdoors I see a 99% fitness score!

--

Harshad RJ

[Brewster LaMacchia]

Hi Harshad,

On 8/25/2016 3:32 PM, Harshad RJ wrote:
> I have fixed the crash-during-save and published an update (version
> 2.2). When you get the chance, please update and send me the
> attachments off-list.

Hopefully you have two emails now with three runs each from my Nexus 5
and Moto X.


--

Thanks,
Brewster