Locl - User contributions [en]

CalCOFI Drifter Realtime Webpage Info

2009-06-26T21:03:53Z

Kirk ireson:

<h1>CalCOFI SVP Drifter Realtime Webpage Wiki</h1>

NOTES AND THINGS TO KNOW ABOUT THE SVP REALTIME PAGE<br>
Jun, 2009 Kirk

Webpage:
[http://www.icess.ucsb.edu/drifter/realtime-SVP/ SVP Realtime Page]

There are three main parts needed to display the data (details below):<br>
1. Fetching the data (using Python script running on dub-locl)<br>
2. Parsing the data (using PHP script running on website)<br>
3. Displaying the data (using Javascript running on your browser)<br>

<h2>1. FETCHING THE DATA</h2>

On dub-locl.icess.ucsb.edu in /localhome/kirk/scripts/ there is a script 'expect_script_to_fetch_argos_data.py'. It uses 'pexpect', a Python version of the 'expect' scripts, which allows you to script what would normally be an interactive terminal session. This is necessary in this case because we have to obtain the data via a telnet session.
<ul>
<li>There is essentially nothing to configure it, and it's well documented should you need to change anything. It is set to fetch the last 24hours worth of positions.

<li>It may need to be updated with drifter numbers as more are sent drifting.

<li>It is set to run every 6 hours via a "cron job" in the kirk account. To edit this job, as kirk, at the Terminal, type 'crontab -e' and use 'vi' style editing commands, or 'crontab -l' to just show it. (To become kirk, login as drift, then in a Terminal, type 'sudo su -' (then type the drift password) to become root, then 'su kirk' to become kirk.)

<li>It saves the output of this session to /home/locl/file_sharing/SVP_CALCOFI_LATEST_DATA.txt on the ICESS network (which is accessed on dub-locl via /mnt/locl/, which should be mounted automatically if the system reboots, see /etc/fstab)
</ul>

<h2>2. PARSING THE DATA</h2>

When someone visits the webpage (http://www.icess.ucsb.edu/drifter/realtime-SVP/), in the ajax.js file there is instruction to fetch the data. This 'fetch' is accomplished by calling 'parse_argos_data.php' in that directory. This php script reads the file saved above (in /home/locl/), ignores all the non-data lines, and processes/cleans up the crazy ARGOS format output from the telnet session.

It outputs 1 record per position report in this format:<br>
<pre>
drift_no,YY-MM-DD,HH:MM:SS,milliseconds_since_Jan01_1970,orig_report_num,lat,lon,position_type(1=GPS,0=ARGOS),SST(C),batt(V),base_time,record_num
</pre>
e.g.
<pre>
75428,2007-04-03,10:33:37,1175610817000,137,+26.6979,-081.9557,1,NaN,12.4,2007-04-03_11:33:30,2 (a gps position)
</pre>
<ul>
<li>There is very little configuring it, and it's well documented should you need to change anything.

<li>Its output can be seen easily:
http://www.icess.ucsb.edu/drifter/realtime-SVP/parse_argos_data.php
</ul>

<h2>3. DISPLAYING THE DATA (at [http://www.icess.ucsb.edu/drifter/realtime-SVP/ realtime page]) </h2>

The Google mapping code was adapted from the Iridium/Microstar realtime page at http://www.icess.ucsb.edu/drifter/realtime/

The two main javascript files are ajax.js and map.js.

The javascript files are compressed using http://www.icess.ucsb.edu/drifter/realtime/JavascriptCompressor.html, so changes made to the xxx__UNCOMPRESSED__.js files won't show up on the page unless they are compressed and saved without the "__UNCOMPRESSED__" portion in the name, OR at the beginning of index.php those two types of files are commented/uncommented out as appropriate.

<h2> POTENTIAL PROBLEMS / TROUBLESHOOTING</h2>

Prob: The data file (/home/locl/file_sharing/SVP_CALCOFI_LATEST_DATA.txt) is not getting saved/updated
<ul>
<li>Is the dub-locl computer up?
<li>Is /mnt/locl mounted on dub-locl? It should come up automatically
<li>Has 6 hours passed since the last time it ran? It only runs every 6 hours
<li>Try fetching the data yourself via telnet (do these commands at a terminal prompt):
</ul>
<pre>
telnet datadist.argosinc.com
hansen (at the 'Username:' prompt)
aomlus (at the 'Password:' prompt)
prv,7325,ds,,93561-93587 (at the '/' prompt, to get the previous 9 day's worth of data for drifter #93561-93587 )
lo (at the '/' prompt, to log out)
</pre>

NOTE: if you want to get data from a specific time period, use julian dates and GMT hours after the comma after 'ds'.
For example:
<pre>
prv,7325,ds,174/12-175/10,93561-93587 (for June 23rd at 12Z through June 24th at 10Z)
</pre>

Prob: The data file (/home/locl/file_sharing/SVP_CALCOFI_LATEST_DATA.txt) shows no data
<ul>
<li>There probably aren't any drifters talking in the last 24hours (look for the line "No data available or authorization failure" in the file or try manually getting the data)
</ul>

----
<h2>INFO ABOUT TIME CALCULATION</h2>
Basically each data block is for three hourly reports, and data blocks can be repeated (I
have no idea how that's determined), and there is a slight adjustment
to the time based on "fix delay" (or "Length of Acquisition", which is
usually on the order of <60 seconds).<br>
<br>
For example (showing the second to last block in the existing file as
I write this):<br>
<pre>
07325 93575 15 27 N 3 2009-06-25 20:18:59 34.416 240.156 0.000 401652653
2009-06-25 20:21:22 3 12 62 678 94
00 01 344156 01
1198452 01 04 689
01 344155 01 1198448
01 04 661 01
344156 01 1198448 01
04 587 00
</pre>
<br>
This *first line* contains ARGOS only info:
<pre>
prog_num 07325
drift_num 93575
lines_in_sat_pass 15
num_sensors 27
sat_name N
resolution 3
time 2009-06-25 20:18:59
xmit_lat 34.416
xmit_lon 240.156
xmit_alt 0.000
xmit_freq 401652653
</pre>
<br>
The next 7 lines contain 3, hourly GPS reports.<br>
<br>
---- Line 1: (2009-06-25 20:21:22 3 12 62 678 94)<br>
<pre>
BASE Date/Time 2009-06-25 20:21:22
# identical messages rcvd 3
Drogue count over last half hour 12
Battery voltage = n * 0.2 62 -> 12.4V
SST(C) = x * 0.043 - 5 678 -> 24.154
Checksum 94
</pre>
<br>
---- Line 2: (00 01 344156 01)<br>
<pre>
Msg ID 00 -> this is 1st message sent
Valid Pos #1 (1=good, 0=bad) 01 -> good
Lat #1 (ten-thousandths of degree) 344156 -> 34.4156
Lat #1 Ref (0 = South, 1 = North) 01 -> North
</pre>
<br>
---- Line 3: (1198452 01 04 689)<br>
<pre>
Lon #1 (ten-thousandths of degree) 1198452 -> 119.8452
Lon #1 Ref (0 = East, 1 = West) 01 -> West
Pos #1 Length of Acq (seconds = n * 4) 04 -> 16(seconds)
SST #1 (C) = x * 0.043 - 5 689 -> 24.627
</pre>
<br>
---- Line 4: (01 344155 01 1198448)<br>
<pre>
Valid Pos #2 (1=good, 0=bad) 01 -> good
Lat #2 (ten-thousandths of degree) 344155 -> 34.4155
Lat #2 Ref (0 = South, 1 = North) 01 -> North
Lon #2 (ten-thousandths of degree) 1198448 -> 119.8448
</pre>
<br>
---- Line 5: (01 04 661 01)<br>
<pre>
Lon #2 Ref (0 = East, 1 = West) 01 -> West
Pos #2 Length of Acq (seconds = n * 4) 04 -> 16(seconds)
SST #2 (C) = x * 0.043 - 5 661 -> 23.423
Valid Pos #3 (1=good, 0=bad) 01 -> good
</pre>
<br>
---- Line 6: (344156 01 1198448 01)<br>
<pre>
Lat #3 (ten-thousandths of degree) 344156 -> 34.4156
Lat #3 Ref (0 = South, 1 = North) 01 -> North
Lon #3 (ten-thousandths of degree) 1198448 -> 119.8448
Lon #3 Ref (0 = East, 1 = West) 01 -> West
</pre>
<br>
---- Line 7: (04 587 00)<br>
<pre>
Pos #3 Length of Acq (seconds = n * 4) 04 -> 16(seconds)
SST #3 (C) = x * 0.043 - 5 587 -> 20.241
Null bits (only for padding, ignore)
</pre>
<br>
<br>
<b>NOTES:</b><br>
-Total bit count (a very non trivial calculation) of all 7 lines must equal the checksum value or
message block is considered garbled and thus ignored.<br>
<br>
-Times of GPS reports are calculated thusly:<br>
<br>
1) Take BASE time, subtract (Msg ID*3) [that is, if message has been
repeated, it is at least 3 hours old -- I have a switch in my code
(it's turned on for now) which will ignore messages with a message
ID>0 because the original may be also present, and it's possible the
duplicate isn't an exact duplicate and then you get slightly different
reports at similar times]<br>
2) Then, subtract 2 hours for Pos #3, and 1 hour for Pos #2 and 0 for Pos #1<br>
3) Then subtract the associated small "Length of Acq"<br>
<br>
Thus, the 2nd GPS time (i.e. #2) would be calculated thusly:<br>
<pre>
BASE time: 2009-06-25 20:21:22
minus 0 hours (because Msg ID is 0)
minus 1 hour (because it's Pos #2)
minus (pos #2 length of acq) 16 seconds

equals: 2009-06-25 19:21:06
</pre>
<br>
An additional wacky thing is that due to repetition of the messages,
or god knows what, the calculations of the reports you see aren't
necessarily in chronological order. So, after doing all the
calculations, I then sort them chronologically before outputting
(within the parse_argos_data.php script), so that when showing the
track lines, the points are in order.<br>

CalCOFI Drifter Realtime Webpage Info

2009-06-26T20:44:29Z

Kirk ireson:

<h1>CalCOFI SVP Drifter Realtime Webpage Wiki</h1>

NOTES AND THINGS TO KNOW ABOUT THE SVP REALTIME PAGE<br>
Jun, 2009 Kirk

Webpage:
[http://www.icess.ucsb.edu/drifter/realtime-SVP/ SVP Realtime Page]

There are three main parts needed to display the data (details below):<br>
1. Fetching the data (using Python script running on dub-locl)<br>
2. Parsing the data (using PHP script running on website)<br>
3. Displaying the data (using Javascript running on your browser)<br>

<h2>1. FETCHING THE DATA</h2>

On dub-locl.icess.ucsb.edu in /localhome/kirk/scripts/ there is a script 'expect_script_to_fetch_argos_data.py'. It uses 'pexpect', a Python version of the 'expect' scripts, which allows you to script what would normally be an interactive terminal session. This is necessary in this case because we have to obtain the data via a telnet session.
<ul>
<li>There is essentially nothing to configure it, and it's well documented should you need to change anything. It is set to fetch the last 24hours worth of positions.

<li>It may need to be updated with drifter numbers as more are sent drifting.

<li>It is set to run every 6 hours via a "cron job" in the kirk account. To edit this job, as kirk, at the Terminal, type 'crontab -e' and use 'vi' style editing commands, or 'crontab -l' to just show it. (To become kirk, login as drift, then in a Terminal, type 'sudo su -' (then type the drift password) to become root, then 'su kirk' to become kirk.)

<li>It saves the output of this session to /home/locl/file_sharing/SVP_CALCOFI_LATEST_DATA.txt on the ICESS network (which is accessed on dub-locl via /mnt/locl/, which should be mounted automatically if the system reboots, see /etc/fstab)
</ul>

<h2>2. PARSING THE DATA</h2>

When someone visits the webpage (http://www.icess.ucsb.edu/drifter/realtime-SVP/), in the ajax.js file there is instruction to fetch the data. This 'fetch' is accomplished by calling 'parse_argos_data.php' in that directory. This php script reads the file saved above (in /home/locl/), ignores all the non-data lines, and processes/cleans up the crazy ARGOS format output from the telnet session.

It outputs 1 record per position report in this format:<br>
<pre>
drift_no,YY-MM-DD,HH:MM:SS,milliseconds_since_Jan01_1970,orig_report_num,lat,lon,position_type(1=GPS,0=ARGOS),SST(C),batt(V),base_time,record_num
</pre>
e.g.
<pre>
75428,2007-04-03,10:33:37,1175610817000,137,+26.6979,-081.9557,1,NaN,12.4,2007-04-03_11:33:30,2 (a gps position)
</pre>
<ul>
<li>There is very little configuring it, and it's well documented should you need to change anything.

<li>Its output can be seen easily:
http://www.icess.ucsb.edu/drifter/realtime-SVP/parse_argos_data.php
</ul>

<h2>3. DISPLAYING THE DATA (at [http://www.icess.ucsb.edu/drifter/realtime-SVP/ realtime page]) </h2>

The Google mapping code was adapted from the Iridium/Microstar realtime page at http://www.icess.ucsb.edu/drifter/realtime/

The two main javascript files are ajax.js and map.js.

The javascript files are compressed using http://www.icess.ucsb.edu/drifter/realtime/JavascriptCompressor.html, so changes made to the xxx__UNCOMPRESSED__.js files won't show up on the page unless they are compressed and saved without the "__UNCOMPRESSED__" portion in the name, OR at the beginning of index.php those two types of files are commented/uncommented out as appropriate.

<h2> POTENTIAL PROBLEMS / TROUBLESHOOTING</h2>

Prob: The data file (/home/locl/file_sharing/SVP_CALCOFI_LATEST_DATA.txt) is not getting saved/updated
<ul>
<li>Is the dub-locl computer up?
<li>Is /mnt/locl mounted on dub-locl? It should come up automatically
<li>Has 6 hours passed since the last time it ran? It only runs every 6 hours
<li>Try fetching the data yourself via telnet (do these commands at a terminal prompt):
</ul>
<pre>
telnet datadist.argosinc.com
hansen (at the 'Username:' prompt)
aomlus (at the 'Password:' prompt)
prv,7325,ds,,93561-93587 (at the '/' prompt, to get the previous 9 day's worth of data for drifter #93561-93587 )
lo (at the '/' prompt, to log out)
</pre>

NOTE: if you want to get data from a specific time period, use julian dates and GMT hours after the comma after 'ds'.
For example:
<pre>
prv,7325,ds,174/12-175/10,93561-93587 (for June 23rd at 12Z through June 24th at 10Z)
</pre>

Prob: The data file (/home/locl/file_sharing/SVP_CALCOFI_LATEST_DATA.txt) shows no data
<ul>
<li>There probably aren't any drifters talking in the last 24hours (look for the line "No data available or authorization failure" in the file or try manually getting the data)
</ul>

----
<h2>INFO ABOUT TIME CALCULATION</h2>
Basically each data block is for three hourly reports, and data blocks can be repeated (I
have no idea how that's determined), and there is a slight adjustment
to the time based on "fix delay" (or "Length of Acquisition", which is
usually on the order of <60 seconds).<br>
<br>
For example (showing the second to last block in the existing file as
I write this):<br>
<pre>
07325 93575 15 27 N 3 2009-06-25 20:18:59 34.416 240.156 0.000 401652653
2009-06-25 20:21:22 3 12 62 678 94
00 01 344156 01
1198452 01 04 689
01 344155 01 1198448
01 04 661 01
344156 01 1198448 01
04 587 00
</pre>
<br>
This *first line* contains ARGOS only info:
<pre>
prog_num 07325
drift_num 93575
lines_in_sat_pass 15
num_sensors 27
sat_name N
resolution 3
time 2009-06-25 20:18:59
xmit_lat 34.416
xmit_lon 240.156
xmit_alt 0.000
xmit_freq 401652653
</pre>
<br>
The next 7 lines contain 3, hourly GPS reports.<br>
<br>
---- Line 1: (2009-06-25 20:21:22 3 12 62 678 94)<br>
<pre>
BASE Date/Time 2009-06-25 20:21:22
# identical messages rcvd 3
Drogue count over last half hour 12
Battery voltage = n * 0.2 62 -> 12.4V
SST(C) = x * 0.043 - 5 678 -> 24.154
Checksum 94
</pre>
<br>
---- Line 2: (00 01 344156 01)<br>
<pre>
Msg ID 00 -> this is 1st message sent
Valid Pos #1 (1=good, 0=bad) 01 -> good
Lat #1 (ten-thousandths of degree) 344156 -> 34.4156
Lat #1 Ref (0 = South, 1 = North) 01 -> North
</pre>
<br>
---- Line 3: (1198452 01 04 689)<br>
<pre>
Lon #1 (ten-thousandths of degree) 1198452 -> 119.8452
Lon #1 Ref (0 = East, 1 = West) 01 -> West
Pos #1 Length of Acq (seconds = n * 4) 04 -> 16(seconds)
SST #1 (C) = x * 0.043 - 5 689 -> 24.627
</pre>
<br>
---- Line 4: (01 344155 01 1198448)<br>
<pre>
Valid Pos #2 (1=good, 0=bad) 01 -> good
Lat #2 (ten-thousandths of degree) 344155 -> 34.4155
Lat #2 Ref (0 = South, 1 = North) 01 -> North
Lon #2 (ten-thousandths of degree) 1198448 -> 119.8448
</pre>
<br>
---- Line 5: (01 04 661 01)<br>
<pre>
Lon #2 Ref (0 = East, 1 = West) 01 -> West
Pos #2 Length of Acq (seconds = n * 4) 04 -> 16(seconds)
SST #2 (C) = x * 0.043 - 5 661 -> 23.423
Valid Pos #3 (1=good, 0=bad) 01 -> good
</pre>
<br>
---- Line 6: (344156 01 1198448 01)<br>
<pre>
Lat #3 (ten-thousandths of degree) 344156 -> 34.4156
Lat #3 Ref (0 = South, 1 = North) 01 -> North
Lon #3 (ten-thousandths of degree) 1198448 -> 119.8448
Lon #3 Ref (0 = East, 1 = West) 01 -> West
</pre>
<br>
---- Line 7: (04 587 00)<br>
<pre>
Pos #3 Length of Acq (seconds = n * 4) 04 -> 16(seconds)
SST #3 (C) = x * 0.043 - 5 587 -> 20.241
Null bits (only for padding, ignore)
</pre>
<br>
<br>
<b>NOTES:</b><br>
-Total bit count of all 7 lines must equal the checksum value or
message block is considered garbled and thus ignored.<br>
<br>
-Times of GPS reports are calculated thusly:<br>
<br>
1) Take BASE time, subtract (Msg ID*3) [that is, if message has been
repeated, it is at least 3 hours old -- I have a switch in my code
(it's turned on for now) which will ignore messages with a message
ID>0 because the original may be also present, and it's possible the
duplicate isn't an exact duplicate and then you get slightly different
reports at similar times]<br>
2) Then, subtract 2 hours for Pos #3, and 1 hour for Pos #2 and 0 for Pos #1<br>
3) Then subtract the associated small "Length of Acq"<br>
<br>
Thus, the 2nd GPS time (i.e. #2) would be calculated thusly:<br>
<pre>
BASE time: 2009-06-25 20:21:22
minus 0 hours (because Msg ID is 0)
minus 1 hour (because it's Pos #2)
minus (pos #2 length of acq) 16 seconds

equals: 2009-06-25 19:21:06
</pre>
<br>
An additional wacky thing is that due to repetition of the messages,
or god knows what, the calculations of the reports you see aren't
necessarily in chronological order. So, after doing all the
calculations, I then sort them chronologically before outputting
(within the parse_argos_data.php script), so that when showing the
track lines, the points are in order.<br>

CalCOFI Drifter Realtime Webpage Info

2009-06-26T19:08:48Z

Kirk ireson:

<h1>CalCOFI SVP Drifter Realtime Webpage Wiki</h1>

NOTES AND THINGS TO KNOW ABOUT THE SVP REALTIME PAGE<br>
Jun, 2009 Kirk

Webpage:
[http://www.icess.ucsb.edu/drifter/realtime-SVP/ SVP Realtime Page]

There are three main parts needed to display the data (details below):<br>
1. Fetching the data (using Python script running on dub-locl)<br>
2. Parsing the data (using PHP script running on website)<br>
3. Displaying the data (using Javascript running on your browser)<br>

<h2>1. FETCHING THE DATA</h2>

On dub-locl.icess.ucsb.edu in /localhome/kirk/scripts/ there is a script 'expect_script_to_fetch_argos_data.py'. It uses 'pexpect', a Python version of the 'expect' scripts, which allows you to script what would normally be an interactive terminal session. This is necessary in this case because we have to obtain the data via a telnet session.
<ul>
<li>There is essentially nothing to configure it, and it's well documented should you need to change anything. It is set to fetch the last 24hours worth of positions.

<li>It may need to be updated with drifter numbers as more are sent drifting.

<li>It is set to run every 6 hours via a "cron job" in the kirk account. To edit this job, as kirk, at the Terminal, type 'crontab -e' and use 'vi' style editing commands, or 'crontab -l' to just show it. (To become kirk, login as drift, then in a Terminal, type 'sudo su -' (then type the drift password) to become root, then 'su kirk' to become kirk.)

<li>It saves the output of this session to /home/locl/file_sharing/SVP_CALCOFI_LATEST_DATA.txt on the ICESS network (which is accessed on dub-locl via /mnt/locl/, which should be mounted automatically if the system reboots, see /etc/fstab)
</ul>

<h2>2. PARSING THE DATA</h2>

When someone visits the webpage (http://www.icess.ucsb.edu/drifter/realtime-SVP/), in the ajax.js file there is instruction to fetch the data. This 'fetch' is accomplished by calling 'parse_argos_data.php' in that directory. This php script reads the file saved above (in /home/locl/), ignores all the non-data lines, and processes/cleans up the crazy ARGOS format output from the telnet session.

It outputs 1 record per position report in this format:
drift_no,YY-MM-DD,HH:MM:SS,milliseconds_since_Jan01_1970,orig_report_num,lat,lon,position_type(1=GPS,0=ARGOS),SST(C),batt(V)
e.g.
<pre>
75428,2007-04-03,10:33:37,1175610817000,137,+26.6979,-081.9557,1,NaN,12.4 (a gps position)
</pre>
<ul>
<li>There is very little configuring it, and it's well documented should you need to change anything.

<li>Its output can be seen easily:
http://www.icess.ucsb.edu/drifter/realtime-SVP/parse_argos_data.php
</ul>

<h2>3. DISPLAYING THE DATA (at [http://www.icess.ucsb.edu/drifter/realtime-SVP/ realtime page]) </h2>

The Google mapping code was adapted from the Iridium/Microstar realtime page at http://www.icess.ucsb.edu/drifter/realtime/

The two main javascript files are ajax.js and map.js.

The javascript files are compressed using http://www.icess.ucsb.edu/drifter/realtime/JavascriptCompressor.html, so changes made to the xxx__UNCOMPRESSED__.js files won't show up on the page unless they are compressed and saved without the "__UNCOMPRESSED__" portion in the name, OR at the beginning of index.php those two types of files are commented/uncommented out as appropriate.

<h2> POTENTIAL PROBLEMS / TROUBLESHOOTING</h2>

Prob: The data file (/home/locl/file_sharing/SVP_CALCOFI_LATEST_DATA.txt) is not getting saved/updated
<ul>
<li>Is the dub-locl computer up?
<li>Is /mnt/locl mounted on dub-locl? It should come up automatically
<li>Has 6 hours passed since the last time it ran? It only runs every 6 hours
<li>Try fetching the data yourself via telnet (do these commands at a terminal prompt):
</ul>
<pre>
telnet datadist.argosinc.com
hansen (at the 'Username:' prompt)
aomlus (at the 'Password:' prompt)
prv,7325,ds,,93561-93587 (at the '/' prompt, to get the previous 9 day's worth of data for drifter #93561-93587 )
lo (at the '/' prompt, to log out)
</pre>

NOTE: if you want to get data from a specific time period, use julian dates and GMT hours after the comma after 'ds'.
For example:
<pre>
prv,7325,ds,174/12-175/10,93561-93587 (for June 23rd at 12Z through June 24th at 10Z)
</pre>

Prob: The data file (/home/locl/file_sharing/SVP_CALCOFI_LATEST_DATA.txt) shows no data
<ul>
<li>There probably aren't any drifters talking in the last 24hours (look for the line "No data available or authorization failure" in the file or try manually getting the data)
</ul>

----
<h2>INFO ABOUT TIME CALCULATION</h2>
Basically each data block is for three hourly reports, and data blocks can be repeated (I
have no idea how that's determined), and there is a slight adjustment
to the time based on "fix delay" (or "Length of Acquisition", which is
usually on the order of <60 seconds).<br>
<br>
For example (showing the second to last block in the existing file as
I write this):<br>
<pre>
07325 93575 15 27 N 3 2009-06-25 20:18:59 34.416 240.156 0.000 401652653
2009-06-25 20:21:22 3 12 62 678 94
00 01 344156 01
1198452 01 04 689
01 344155 01 1198448
01 04 661 01
344156 01 1198448 01
04 587 00
</pre>
<br>
This *first line* contains ARGOS only info:
<pre>
prog_num 07325
drift_num 93575
lines_in_sat_pass 15
num_sensors 27
sat_name N
resolution 3
time 2009-06-25 20:18:59
xmit_lat 34.416
xmit_lon 240.156
xmit_alt 0.000
xmit_freq 401652653
</pre>
<br>
The next 7 lines contain 3, hourly GPS reports.<br>
<br>
---- Line 1: (2009-06-25 20:21:22 3 12 62 678 94)<br>
<pre>
BASE Date/Time 2009-06-25 20:21:22
# identical messages rcvd 3
Drogue count over last half hour 12
Battery voltage = n * 0.2 62 -> 12.4V
SST(C) = x * 0.043 - 5 678 -> 24.154
Checksum 94
</pre>
<br>
---- Line 2: (00 01 344156 01)<br>
<pre>
Msg ID 00 -> this is 1st message sent
Valid Pos #1 (1=good, 0=bad) 01 -> good
Lat #1 (ten-thousandths of degree) 344156 -> 34.4156
Lat #1 Ref (0 = South, 1 = North) 01 -> North
</pre>
<br>
---- Line 3: (1198452 01 04 689)<br>
<pre>
Lon #1 (ten-thousandths of degree) 1198452 -> 119.8452
Lon #1 Ref (0 = East, 1 = West) 01 -> West
Pos #1 Length of Acq (seconds = n * 4) 04 -> 16(seconds)
SST #1 (C) = x * 0.043 - 5 689 -> 24.627
</pre>
<br>
---- Line 4: (01 344155 01 1198448)<br>
<pre>
Valid Pos #2 (1=good, 0=bad) 01 -> good
Lat #2 (ten-thousandths of degree) 344155 -> 34.4155
Lat #2 Ref (0 = South, 1 = North) 01 -> North
Lon #2 (ten-thousandths of degree) 1198448 -> 119.8448
</pre>
<br>
---- Line 5: (01 04 661 01)<br>
<pre>
Lon #2 Ref (0 = East, 1 = West) 01 -> West
Pos #2 Length of Acq (seconds = n * 4) 04 -> 16(seconds)
SST #2 (C) = x * 0.043 - 5 661 -> 23.423
Valid Pos #3 (1=good, 0=bad) 01 -> good
</pre>
<br>
---- Line 6: (344156 01 1198448 01)<br>
<pre>
Lat #3 (ten-thousandths of degree) 344156 -> 34.4156
Lat #3 Ref (0 = South, 1 = North) 01 -> North
Lon #3 (ten-thousandths of degree) 1198448 -> 119.8448
Lon #3 Ref (0 = East, 1 = West) 01 -> West
</pre>
<br>
---- Line 7: (04 587 00)<br>
<pre>
Pos #3 Length of Acq (seconds = n * 4) 04 -> 16(seconds)
SST #3 (C) = x * 0.043 - 5 587 -> 20.241
Null bits (only for padding, ignore)
</pre>
<br>
<br>
<b>NOTES:</b><br>
-Total bit count of all 7 lines must equal the checksum value or
message block is considered garbled and thus ignored.<br>
<br>
-Times of GPS reports are calculated thusly:<br>
<br>
1) Take BASE time, subtract (Msg ID*3) [that is, if message has been
repeated, it is at least 3 hours old -- I have a switch in my code
(it's turned on for now) which will ignore messages with a message
ID>0 because the original may be also present, and it's possible the
duplicate isn't an exact duplicate and then you get slightly different
reports at similar times]<br>
2) Then, subtract 2 hours for Pos #3, and 1 hour for Pos #2 and 0 for Pos #1<br>
3) Then subtract the associated small "Length of Acq"<br>
<br>
Thus, the 2nd GPS time (i.e. #2) would be calculated thusly:<br>
<pre>
BASE time: 2009-06-25 20:21:22
minus 0 hours (because Msg ID is 0)
minus 1 hour (because it's Pos #2)
minus (pos #2 length of acq) 16 seconds

equals: 2009-06-25 19:21:06
</pre>
<br>
An additional wacky thing is that due to repetition of the messages,
or god knows what, the calculations of the reports you see aren't
necessarily in chronological order. So, after doing all the
calculations, I then sort them chronologically before outputting
(within the parse_argos_data.php script), so that when showing the
track lines, the points are in order.<br>

Main Page

2009-06-25T20:09:35Z

Kirk ireson:

<h1>WELCOME TO LAGRANGIAN OCEAN CURRENTS LAB (LOCL) WIKI!</h1>

<b>Links:</b>
<ul>
<li>[http://www.icess.ucsb.edu/drifter Drifter Homepage]
<li>[http://wiki.icess.ucsb.edu/locl/index.php/HOWTO_Drifter_Data_Processing Kirk's HOWTO on Drifter Data Processing]
<li>[http://wiki.icess.ucsb.edu/locl/index.php/CalCOFI_Drifter_Realtime_Webpage_Info CalCOFI Drifter Realtime Webpage Info]
</ul>

----

<h1>For Wiki Help See:</h1>
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==

* [http://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]
* [http://mail.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]

CalCOFI Drifter Realtime Webpage Info

2009-06-25T20:08:17Z

Kirk ireson: New page: <h1>CalCOFI SVP Drifter Realtime Webpage Wiki</h1> NOTES AND THINGS TO KNOW ABOUT THE SVP REALTIME PAGE<br> Jun, 2009 Kirk Webpage: [http://www.icess.ucsb.edu/drifter/realtime-SVP/ SVP R...

HOWTO Drifter Data Processing

2009-06-22T21:53:36Z

Kirk ireson:

<h1>Kirk's HOWTO on processing Drifter data</h1>
<br>
<h2>Follow these steps to process 'raw' drifter data from [http://www.pacificgyre.com pacificgyre] to final posting on our website:</h2>
<br>
<b>Notes:</b>
<ul>
<li>Once proficient, it takes about 20 min to process a typical day's deployment.
<li>Folders/files referenced here can be found on the ICESS network at /home/locl/users/kirk/ (hereafter referred to as '..../kirk/') in the <b>data</b> or <b>user</b> subfolders.
<li>You should copy the <i>kirk</i> folder contents to your local computer and run the scripts there instead of on the server.
</ul>
<br>
<ol>
<h2>Folder: .../kirk/user/0_Info</h2>
<li><b>On deployment day</b>: be sure to fill out .../kirk/user/0_Info/<b>drifter_hist.xls</b> (drifter history) with the
performance of the drifters to track if there are any consistent problems (<i>Note that this file is now out of date</i>).<br>
<br>
<h2>Folder: .../kirk/user/1_get_data_from_web</h2>
<li>Edit <b>data_dates.m</b> with the start/stop date/times to get.<br>
Notes:<br>
<ul>
<li>Use the [http://pacificgyre.com http://pacificgyre.com] website (log: <i>ohlmann</i>, pass: <i>drifterguy</i>) if you need to get an estimation of
when the drifters went in and came out of the water (look at in-water flag values), or go to
[http://www.icess.ucsb.edu/drifter/realtime/BETA.php http://www.icess.ucsb.edu/drifter/realtime/BETA.php] and enter custom times.
<li>Keep adding date/times to the bottom of this file (or in the appropriate "deployment type" area (e.g. SBCLS), and commented out), then copy these uncommented deployment times to
the top of it to fetch the data. Note, when in the "deployment type" groups, I number the 'dates' sequentially, but when copying one or two of them to the top to fetch, you need to make sure those 'dates' numbering start at 1.
<li>You don't have to be exact on the times (cleanup happens in following steps), just be sure you have a time at least before or at start and a time after or at ending deployment.
</ul>
<li>Run <b>get_data.m</b>
<ul>
<li>Be sure the <b>IRIDIUM</b> value in it is set correctly
<li>Data will be saved in '..../kirk/data/Drifter_Anal/2_data/<i>yyyymmdd</i>' folder as a <i>yyyymmdd_drifter_dat.log</i> file.
<li>Now, move that folder into a 'deployment type' folder (e.g. .../kirk/data/Drifter_Anal/2_data/<b>SBCLS</b>)<br>
</ul>
<br>
Notes:<br>
<ul>
<li>If IRIDIUM is set, you may want to check the settings of <b>REMOVE_GPS_01</b> and <b>CONVERT_GPS_2_TO_2</b> in the <b>convert_Iridium_reports_to_Microstar_format.m</b> file.
<li>Data format (column numbers):
</ul>
<pre>
#1 drifter ID
#2 year
#3 month
#4 day
#5 hour
#6 minute
#7 second
#8 lat
#9 long
#10 satelites availiable
#11 satelites used
#12 com flag
#13 Secs to fix
#14 Mobitex RSSI
#15 in-water flag
</pre>
<h2>Folder: .../kirk/user/2_clean_up</h2>
<li>Edit <b>clean_up_drifter_data.m</b> with the correct <b>area</b> and <b>deploy_date</b> at the top.<br>

<br><br><br><br><br><br><br><br>

Main Page

2009-06-20T17:49:10Z

Kirk ireson:

<h1>WELCOME TO LAGRANGIAN OCEAN CURRENTS LAB (LOCL) WIKI!</h1>

<b>Links:</b>
<ul>
<li>[http://www.icess.ucsb.edu/drifter Drifter Homepage]
<li>[http://wiki.icess.ucsb.edu/locl/index.php/HOWTO_Drifter_Data_Processing Kirk's HOWTO on Drifter Data Processing]
</ul>

----

<h1>For Wiki Help See:</h1>
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==

* [http://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]
* [http://mail.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]

HOWTO Drifter Data Processing

2009-06-20T17:45:49Z

Kirk ireson:

<h1>Kirk's HOWTO on processing Drifter data</h1>
<br>
<h2>Follow these steps to process 'raw' drifter data from [http://www.pacificgyre.com pacificgyre] to final posting on our website:</h2>
<br>
<b>Notes:</b>
<ul>
<li>Once proficient, it takes about 20 min to process a typical day's deployment.
<li>Folders/files referenced here can be found on the ICESS network at /home/locl/users/kirk/ (hereafter referred to as '..../kirk/') in the <b>data</b> or <b>user</b> subfolders.
<li>You should copy the <i>kirk</i> folder contents to your local computer and run the scripts there instead of on the server.
</ul>
<br>
<ol>
<h2>Folder: .../kirk/user/0_Info</h2>
<li><b>On deployment day</b>: be sure to fill out .../kirk/user/0_Info/<b>drifter_hist.xls</b> (drifter history) with the
performance of the drifters to track if there are any consistent problems (<i>Note that this file is now out of date</i>).<br>
<br>
<h2>Folder: .../kirk/user/1_get_data_from_web</h2>
<li>Edit <b>data_dates.m</b> with the start/stop date/times to get.<br>
Notes:<br>
<ul>
<li>Use the [http://pacificgyre.com http://pacificgyre.com] website (log: <i>ohlmann</i>, pass: <i>drifterguy</i>) if you need to get an estimation of
when the drifters went in and came out of the water (look at in-water flag values), or go to
[http://www.icess.ucsb.edu/drifter/realtime/BETA.php http://www.icess.ucsb.edu/drifter/realtime/BETA.php] and enter custom times.
<li>Keep adding date/times to the bottom of this file (commented out), then copy your uncommented deployment times to
the top of it to fetch the data.
<li>You don't have to be exact on the times (cleanup happens in following steps), just be sure you have a time at least before or at start and a time after or at ending deployment.
</ul>
<li>Run <b>get_data.m</b> (be sure the <b>IRIDIUM</b> value in it is set correctly), data will be saved in '..../kirk/data/Drifter_Anal/2_data/<i>yyyymmdd</i>' folder as a <i>yyyymmdd_drifter_dat.log</i> file.<br>
<ul>
<li>Now, move that folder into a 'deployment type' folder (e.g. .../kirk/data/Drifter_Anal/2_data/<b>SBCLS</b>)<br>
</ul>
<br>
Notes:<br>
<ul>
<li>If IRIDIUM is set, you may want to check the settings of <b>REMOVE_GPS_01</b> and <b>CONVERT_GPS_2_TO_2</b> in the <b>convert_Iridium_reports_to_Microstar_format.m</b> file.
<li>Data format (column numbers):
</ul>
<pre>
#1 drifter ID
#2 year
#3 month
#4 day
#5 hour
#6 minute
#7 second
#8 lat
#9 long
#10 satelites availiable
#11 satelites used
#12 com flag
#13 Secs to fix
#14 Mobitex RSSI
#15 in-water flag
</pre>
<h2>Folder: .../kirk/user/2_clean_up</h2>
<li>Edit <b>clean_up_drifter_data.m</b> with the correct <b>area</b> and <b>deploy_date</b> at the top.<br>

<br><br><br><br><br><br><br><br>

HOWTO Drifter Data Processing

2009-06-20T04:05:25Z

Kirk ireson: New page: <h1>Kirk's HOWTO on processing Drifter data</h1> <br> <h2>Follow these steps to process 'raw' drifter data from [http://www.pacificgyre.com pacificgyre] to final posting on our website:</h...

<h1>Kirk's HOWTO on processing Drifter data</h1>
<br>
<h2>Follow these steps to process 'raw' drifter data from [http://www.pacificgyre.com pacificgyre] to final posting on our website:</h2>
<br>
<b>Notes:</b>
<ul>
<li>Once proficient, it takes about 20 min to process a typical day's deployment.
<li>Folders/files referenced here can be found on the ICESS network at /home/locl/users/kirk/ (hereafter referred to as '..../kirk/') in the <b>data</b> or <b>user</b> subfolders.
<li>You should copy the 'user' folder contents to your local computer and run the scripts there instead of on the server.
</ul>
<br>
<ol>
<h2>Folder: .../kirk/user/0_Info</h2>
<li><b>On deployment day</b>: be sure to fill out .../kirk/user/0_Info/<b>drifter_hist.xls</b> (drifter history) with the
performance of the drifters to track if there are any consistent problems.<br>
<br>
<h2>Folder: .../kirk/user/1_get_data_from_web</h2>
<li>Edit <b>data_dates.m</b> with the start/stop date/times to get.<br>
Notes:<br>
<ul>
<li>Use the [http://pacificgyre.com http://pacificgyre.com] website (log: <i>ohlmann</i>, pass: <i>drifterguy</i>) if you need to get an estimation of
when the drifters went in and came out of the water (look at in-water flag values), or go to
[http://www.icess.ucsb.edu/drifter/realtime/BETA.php http://www.icess.ucsb.edu/drifter/realtime/BETA.php] and enter custom times.
<li>Keep adding date/times to the bottom of this file (commented out), then copy your uncommented deployment times to
the top of it to fetch the data.
<li>You don't have to be exact on the times (cleanup happens in following steps), just be sure you have a time at least before or at start and a time after or at ending deployment.
</ul>
<li>Run <b>get_data.m</b> (be sure the <b>IRIDIUM</b> value in it is set correctly), data will be saved in '..../kirk/data/Drifter_Anal/2_data/<i>yyyymmdd</i>' folder as a <i>yyyymmdd_drifter_dat.log</i> file.<br>
<ul>
<li>Now, move that folder into a 'deployment type' folder (e.g. .../kirk/data/Drifter_Anal/2_data/<i>SBCLS</i>)<br>
</ul>
<br>
Notes:<br>
<ul>
<li>Data format (column numbers):
</ul>
<pre>
#1 drifter ID
#2 year
#3 month
#4 day
#5 hour
#6 minute
#7 second
#8 lat
#9 long
#10 satelites availiable
#11 satelites used
#12 com flag
#13 Secs to fix
#14 Mobitex RSSI
#15 in-water flag
</pre>

Main Page

2009-06-19T04:02:50Z

Kirk ireson:

<big>WELCOME TO LAGRANGIAN OCEAN CURRENTS LAB WIKI!</big>

[http://www.icess.ucsb.edu/drifter Drifter Homepage]

----

Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==

* [http://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]
* [http://mail.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]