<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mjb/altos/ao-tools/altosui/AltosEepromReader.java, branch telescience-v0.2</title>
<subtitle>AltOS - the operating system for Altus Metrum products
</subtitle>
<id>https://git.ethernal.org/mjb/altos/atom?h=telescience-v0.2</id>
<link rel='self' href='https://git.ethernal.org/mjb/altos/atom?h=telescience-v0.2'/>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/'/>
<updated>2010-09-28T00:11:48+00:00</updated>
<entry>
<title>altosui: Create iterables for log file scanning. Split out display threads</title>
<updated>2010-09-28T00:11:48+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2010-09-28T00:11:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=c89a34d1eb25155405b0036baeadc7bbfeade1c2'/>
<id>urn:sha1:c89a34d1eb25155405b0036baeadc7bbfeade1c2</id>
<content type='text'>
Convert from log file reading paradigm to using iterators which is
more idiomatic for java. Split more code out of AltosUI.java,
including the display update threads for telemetry monitoring and
logfile replay.x

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altosui: Use recorded ground acceleration when reading eeprom files</title>
<updated>2010-09-19T09:50:43+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2010-09-19T09:50:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=7a4d7110debb88f4e906fee7c46f2badd561809d'/>
<id>urn:sha1:7a4d7110debb88f4e906fee7c46f2badd561809d</id>
<content type='text'>
The flight software records 1000 accelerometer samples and records
that in the flight log. Use that value instead of using the very few
samples recorded in the eeprom before boost is detected. This
generates far more accurate accerometer data in the .csv files.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altosui: Stop parsing eeprom file after hitting 'landed' state</title>
<updated>2010-09-10T06:07:16+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2010-09-10T06:04:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=9d0e89e8ad8926dc8371fa809835a580ae49711d'/>
<id>urn:sha1:9d0e89e8ad8926dc8371fa809835a580ae49711d</id>
<content type='text'>
Sometimes there are additional records found in the eeprom file; the
reader is mostly worried about not losing anything, so it reads as
much as it can. However, the last record written for any flight is the
'landed' record, so we can stop looking at the file after hitting that.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altosui: Fill in time value of last Eeprom record read from file</title>
<updated>2010-09-10T06:07:16+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2010-09-10T06:04:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=67b6952f7126704478ede5575e5e938d18fcc329'/>
<id>urn:sha1:67b6952f7126704478ede5575e5e938d18fcc329</id>
<content type='text'>
The last record is handled separately, and was missing the code to
compute the time. Sigh.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altosui: eeprom files place 'boost' time in the flight number record.</title>
<updated>2010-09-05T08:55:56+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2010-09-05T08:55:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=b61fec225ada6a9e252e4c7920101ee18c77cbdc'/>
<id>urn:sha1:b61fec225ada6a9e252e4c7920101ee18c77cbdc</id>
<content type='text'>
Instead of looking for the first state change record, use the Flight
record to get the boost tick.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altosui: Record flight number when scanning file, not when running</title>
<updated>2010-09-05T08:52:36+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2010-09-05T08:52:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=6c653a4cba5fef8d49261cf1c024f3e86e9058c6'/>
<id>urn:sha1:6c653a4cba5fef8d49261cf1c024f3e86e9058c6</id>
<content type='text'>
The very first record in the eeprom is the flight number, but it is
time-stamped with the 'boost' time, and so it gets sorted until much
later, delaying the return of data until the rocket enters boost
mode. This drops all of the nice pad GPS and state date on the floor.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altosui: Eeprom files contain only one date; save it.</title>
<updated>2010-09-05T08:01:10+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2010-09-05T08:01:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=2d58f319a7c1a6a8ccc6a539722009996ba886ab'/>
<id>urn:sha1:2d58f319a7c1a6a8ccc6a539722009996ba886ab</id>
<content type='text'>
While reading eeprom files, the GPS record is reconstructed each time
the system sees the first GPS log item (the time field), but as the
date isn't repeated, we need to copy it from the old GPS data record.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altosui: Remove debugging printf from AltosEepromReader</title>
<updated>2010-09-05T07:59:54+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2010-09-05T07:59:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=b2aa689bf3d61e4a3ebe7c828162d1be20aad0f6'/>
<id>urn:sha1:b2aa689bf3d61e4a3ebe7c828162d1be20aad0f6</id>
<content type='text'>
These were in place while validing the GPS data reconstruction code
that handles eeprom files missing the first GPS date line due to the
record overwriting bug in old firmware versions.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altosui: add elevation and range information</title>
<updated>2010-08-27T17:58:55+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2010-08-27T17:58:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=63bd34cd1b5a411489e8c3ab377f0fe0eec11f67'/>
<id>urn:sha1:63bd34cd1b5a411489e8c3ab377f0fe0eec11f67</id>
<content type='text'>
Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altosui: AltosEepromReader was mis-setting boost tick</title>
<updated>2010-08-27T06:47:38+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2010-08-27T06:47:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=e383595cd281687de903fb6176564bbef270cb83'/>
<id>urn:sha1:e383595cd281687de903fb6176564bbef270cb83</id>
<content type='text'>
It was supposed to use record.tick instead of the (unset) state.tick
value.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
</feed>
