<commit_before><?xml version="1.0" encoding="UTF-8"?>
<cheatsheet title="Analysing Sensor Data" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="..\contentFile.xsd">
	<intro>
		<description>With ever-increasing data rates from multiple recording systems it is easy for an analysis plot to become swamped.  Debrief NG provides tools to reduce the volume and type of data displayed.  This tutorial will lead you through the management of large volumes of data.</description>
	</intro>
	<item title="Check you have some data" href="/org.eclipse.platform.doc.user/concepts/cnav.htm">
		<description>In the top left hand corner of Debrief you should find the Navigator window.  If it isn&apos;t there, select "Navigator" from Debrief&apos;s Window/Show View menu.  Also check you have our sample data-files - it they&apos;re not there, find how to load them from the "Loading sample data" cheat-sheet.</description>
	</item>
	<item title="Open the sample sensor tracks">
		<description>Double-click on the "sen_tracks.rep" file, and you will see the red and blue vessel tracks.</description>
	</item>
	<item title="Fit to window" href="\org.mwc.debrief.help\html\legacy\moving_around.html#Fit_To_Win">
		<description>To make sure all of the data is visible, click on the "Fit-to-Window" toolbar button.  To these tracks you&apos;re going to add the sensor data</description>
	</item>
	<item title="Drag in the SSK track">
		<description>From the Navigator window, drag the SSK sensor data file  (sen_ssk_sensor.rep) onto the plot.</description>
	</item>
	<item title="And now the FF track">
		<description>Next, drag the SSK sensor data file  (sen_frig_sensor.rep) onto the plot.  No, there hasn&apos;t been a visible change to the plot, but be assured, the data is there.</description>
	</item>
	<item title="View the sensor data">
		<description>From the Outline View, expand the &apos;tree&apos; for each track (they&apos;re called &apos;Frigate&apos; and &apos;New_SSK&apos;).  Within each track you will see named blocks of sensor data.  Make each block of sensor data visible by selecting it, then clicking on the &apos;make visible&apos; toolbar button. As you make each set of data visible you should see its bearing fan appear. Overall there are three blocks of sensor data across the two tracks.</description>
	</item>
	<item title="Sensor formatting options" skip="true">
		<description>Sensor lines can be formatted to change their colour, their label, and the location of their label.  The formatting can be applied to a single sensor line or a series of sensor lines.  Now, the dense fans of sensor data present in the sample files you have don&apos;t lend themselves to being individually annotated. So we won&apos;t.  </description>
	</item>
	<item title="Format the sensor data">
		<description>What we&apos;re going to do now is simulate formatting a series of bearing lines to represent a particular sensor state.  So, from the Outline View open up the "NEW_SSK_BB" sensor for the "New_SSK" track.  Select the first five sensor bearings.  Now switch to the properties view.  This view should show the editable properties for those bearings.  Change the color from red to yellow.  You will see the sensor lines on the plot update.</description>
	</item>
	<item title="Conduct a plot-lock" href="\org.mwc.debrief.help\html\legacy\formatting_data.html#track_shifting">
		<description>What we&apos;re going to do now is to simulate the process of dragging tracks so that their bearing fans match.  In UK this is called a plot-lock, and in the US its called a tie-point.  First we must indicate which tracks we want to view the relationship between - so make the Frigate the primary track, and the New_SSK the secondary track - you should now see them both on the Track Tote.</description>
	</item><commit_msg>fix #856<commit_after><?xml version="1.0" encoding="UTF-8"?>
<cheatsheet title="Analysing Sensor Data" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="..\contentFile.xsd">
	<intro>
		<description>With ever-increasing data rates from multiple recording systems it is easy for an analysis plot to become swamped.  Debrief NG provides tools to reduce the volume and type of data displayed.  This tutorial will lead you through the management of large volumes of data.</description>
	</intro>
	<item title="Check you have some data" href="/org.eclipse.platform.doc.user/concepts/cnav.htm">
		<description>In the top left hand corner of Debrief you should find the Navigator window.  If it isn&apos;t there, select "Navigator" from Debrief&apos;s Window/Show View menu.  Also check you have our sample data-files - it they&apos;re not there, find how to load them from the "Loading sample data" cheat-sheet.</description>
	</item>
	<item title="Open the sample sensor tracks">
		<description>Double-click on the "sen_tracks.rep" file  and you will see the red and blue vessel tracks (select &apos;Over The Ground&apos; if the import dialog pops open).</description>
	</item>
	<item title="Fit to window" href="\org.mwc.debrief.help\html\legacy\moving_around.html#Fit_To_Win">
		<description>To make sure all of the data is visible, click on the "Fit-to-Window" toolbar button.  To these tracks you&apos;re going to add the sensor data</description>
	</item>
	<item title="Drag in the SSK track">
		<description>From the Navigator window, drag the SSK sensor data file  (sen_ssk_sensor.rep) onto the plot.</description>
	</item>
	<item title="And now the FF track">
		<description>Next, drag the SSK sensor data file  (sen_frig_sensor.rep) onto the plot.  No, there hasn&apos;t been a visible change to the plot, but be assured, the data is there.</description>
	</item>
	<item title="View the sensor data">
		<description>From the Outline View, expand the &apos;tree&apos; for each track (they&apos;re called &apos;Frigate&apos; and &apos;New_SSK&apos;).  Within each track you will see named blocks of sensor data.  Make each block of sensor data visible by selecting it, then clicking on the &apos;make visible&apos; toolbar button. As you make each set of data visible you should see its bearing fan appear. Overall there are three blocks of sensor data across the two tracks.</description>
	</item>
	<item title="Sensor formatting options" skip="true">
		<description>Sensor lines can be formatted to change their colour, their label, and the location of their label.  The formatting can be applied to a single sensor line or a series of sensor lines.  Now, the dense fans of sensor data present in the sample files you have don&apos;t lend themselves to being individually annotated. So we won&apos;t.  </description>
	</item>
	<item title="Format the sensor data">
		<description>What we&apos;re going to do now is simulate formatting a series of bearing lines to represent a particular sensor state.  So, from the Outline View open up the "NEW_SSK_BB" sensor for the "New_SSK" track.  Select the first five sensor bearings.  Now switch to the properties view.  This view should show the editable properties for those bearings.  Change the color from red to yellow.  You will see the sensor lines on the plot update.</description>
	</item>
	<item title="Conduct a plot-lock" href="\org.mwc.debrief.help\html\legacy\formatting_data.html#track_shifting">
		<description>What we&apos;re going to do now is to simulate the process of dragging tracks so that their bearing fans match.  In UK this is called a plot-lock, and in the US its called a tie-point.  First we must indicate which tracks we want to view the relationship between - so make the Frigate the primary track, and the New_SSK the secondary track - you should now see them both on the Track Tote.</description>
	</item>
{'fraction_non_alphanumeric': 0.08362279686092886, 'fraction_numerical': 0.002444358677473305, 'mean_word_length': 4.64560639070443, 'pattern_counts': {'":': 0, '<': 87, '<?xml version=': 2, '>': 87, 'https://': 0, 'lorem ipsum': 0, 'www.': 2, 'xml': 4}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2275870', 'n_tokens_mistral': 2207, 'n_tokens_neox': 2153, 'n_words': 1042}