<?xml version="1.0" encoding="UTF-16"?>
<Presentation>
<pptaddin>Articulate Presenter version 6 Pro,build10</pptaddin>
<Filename>C:\DATA\PCDATA\HaWG\Webinars and Podcasts\ADCP Midsection 2014\ADCP Midsection.pptx</Filename>
<LmsProperties>
<protocol>
<method/>
<version/>
</protocol>
<completion>
<method/>
<threshold/>
<target/>
</completion>
</LmsProperties>
<BuiltinProperties>
<Title><![CDATA[ADCP Mid-section Podcast]]></Title>
<BasePath>ADCP Midsection</BasePath>
<PresenterName><![CDATA[Nick Stasulis]]></PresenterName>
<PresenterTitle><![CDATA[Hydrologic Technician]]></PresenterTitle>
<PresenterCompany><![CDATA[]]></PresenterCompany>
<PresenterEmail><![CDATA[nstasuli@usgs.gov]]></PresenterEmail>
<PresenterBio><![CDATA[]]></PresenterBio>
<PresenterPhoto><![CDATA[D5F3C7668888.swf]]></PresenterPhoto>
</BuiltinProperties>
<References>
</References>
<Slides>
<Slide id="076f51ca-ede0-4e04-bef4-b9460c3eb130">
<Filename>slide1.swf</Filename>
<BackgroundFile>bgd1l1.swf</BackgroundFile>
<Title><![CDATA[Using ADCPs for Open Water             Mid-section Measurements]]></Title>
<Notes><![CDATA[Using ADCPs for Open Water Mid-section Measurements Hi there, my name is Nick Stasulis and I am a hydrologic technician with the USGS here in Maine, and a member of the USGS Hydroacoustics Work Group. I’d like to take some time to talk about some common questions when getting started using ADCPs for mid-section measurements in open water. A separate video, available on the OSW hydroacoustics webpage, covers the use of ADCPs through ice.   [Photo Description]: A USGS hydrographer deploys an ADCP from a manned cableway.         ]]></Notes>
<notesswfbig>notes/notesbig1.swf</notesswfbig>
<NotesHeightBig>359</NotesHeightBig>
<notesswfsmall>notes/notessmall1.swf</notesswfsmall>
<NotesHeightSmall>526</NotesHeightSmall>
<SlideTime>26</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
</annotations>
<SlideText><![CDATA[Using ADCPs for Open Water             Mid-section Measurements	 Hydroacoustic Work Group (HaWG) Podcast Recorded May 2014 – Nick Stasulis, Maine Office ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="c971902e-53cf-4a43-b10b-0f3191756cf7">
<Filename>slide2.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[Overview]]></Title>
<Notes><![CDATA[Overview In this podcast, we will first cover some general questions that apply to the use of all ADCPs with the mid-section method, then focus on considerations specific to each software manufacturer, both TRDI’s SxS Pro and SonTek’s RiverSurveyor Stationary Live. This podcast is not intended to be a step-by-step guide on how to use the software, as it will only highlight major considerations. The manuals for both SxS Pro and RiverSurveyor Stationary Live are detailed, and provide sufficient information to answer many of the basic configuration and data collection questions. [Photo Description]: An ADCP is deployed from a manned cableway. ]]></Notes>
<notesswfbig>notes/notesbig2.swf</notesswfbig>
<NotesHeightBig>208</NotesHeightBig>
<notesswfsmall>notes/notessmall2.swf</notesswfsmall>
<NotesHeightSmall>392</NotesHeightSmall>
<SlideTime>38</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
</annotations>
<SlideText><![CDATA[Overview Overall Considerations (applying to all ADCPs) TRDI Specific Considerations SonTek Specific Considerations ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="6690a13f-4b2e-45e1-a01d-9956b28b393b">
<Filename>slide3.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[What is the Mid-section Method?]]></Title>
<Notes><![CDATA[What is the Mid-section Method? Before getting into how we use ADCPs with the mid-section method, let’s be sure we know how the mid-section method is used to compute discharge. This method is nothing new, the USGS has been using mid-section computations to compute discharge for over 50 years, beginning with mechanical current meters, then acoustic point-velocity meters, and most recently, ADCPs.  When using the mid-section method, we first select a cross-section, a straight-line path across the river. We’ll talk more about this measurement cross-section later. Once we have selected our cross-section, we collect depth and velocity readings at multiple locations along this straight-line. This combination of depth, velocity and location is referred to as a station, or vertical. Each station has a width that is equal to the distance halfway to the previous station plus halfway to the next station, and using this width and the depth of each station we can compute area. Then, we multiply the velocity measured by the ADCP and the area to compute a discharge for each station. The sum of these discharges is our measurement discharge. With the mid-section method, it’s important to understand that the velocity we are measuring at each vertical should represent the velocity in the entire “box” that is being used to compute flow. So we not only have to be sure to define changes in velocity, but also changes in depth across the channel. Like any mid-section measurement, we want to measure only 5% or less of the total discharge in any one station. [Photo Description]: Screen capture of mid-section method discharge computations, from the RiverSurveyor S5/M9 System Manual; Courtesy SonTek, a Xylem brand. ]]></Notes>
<notesswfbig>notes/notesbig3.swf</notesswfbig>
<NotesHeightBig>375</NotesHeightBig>
<notesswfsmall>notes/notessmall3.swf</notesswfsmall>
<NotesHeightSmall>894</NotesHeightSmall>
<SlideTime>94</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
<annotation type="square" xpos="426.25" ypos="97.125" width="46.5" height="202.375" color="0x376091" alpha="100" show="36400" hide="44900" bordercolor="0x000000" borderalpha="100" animationtype="stretch" loopcount="1" boxradius="5" borderwidth="3"/>
<annotation type="square" xpos="448" ypos="130" width="49.5" height="38.875" color="0x376091" alpha="100" show="49100" hide="55300" bordercolor="0x000000" borderalpha="100" animationtype="stretch" loopcount="1" boxradius="5" borderwidth="3"/>
<annotation type="square" xpos="424.75" ypos="162.875" width="50.25" height="115" color="0x376091" alpha="100" show="72100" hide="78800" bordercolor="0x000000" borderalpha="100" animationtype="stretch" loopcount="1" boxradius="5" borderwidth="3"/>
</annotations>
<SlideText><![CDATA[What is the Mid-section Method? ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="23a3deed-a651-4636-bfe0-bab88f31b0a3">
<Filename>slide4.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[What should I know about selecting a cross-section?]]></Title>
<Notes><![CDATA[What should I know about selecting a cross-section? Unlike the moving boat application of the ADCP, the mid-section method requires a straight-line cross-section across the river. When using ADCPs for a moving boat measurement, our cross-section can be any path across the river as the ADCP is tracking its movement as it goes, we only need to tell the unit how far it is from shore on the starting and ending edges. When using ADCPs with the mid-section method, we select a cross-section that is straight-line across the river. This could be done using a graduated tagline, a manned cableway, or even a bridge. Regardless of how the unit is deployed, you have to be sure that you can accurately determine the location of the ADCP, either as a distance from shore, or a distance from the last station. Keep in mind that where you are holding the rope on a bridge or cableway may not be the location of the ADCP in the river and you need to note the location of the ADCP in the software. This cross-section should be perpendicular to the mean flow direction, have a uniform distribution of flow, and be free of waves, turbulence and eddies. These conditions are optimal, but unfortunately, not all rivers provide ideal cross-sections. However, we need to do our best to select a cross-section that is ideal as conditions allow.  Another consideration is flow angle through the cross-section. We will talk about accounting for flow angles a little later, and while some ADCPs will compute angles automatically, we still need to be able to manually observe and confirm the flow angle at each vertical. Lastly, swimming or rotation of the ADCP when collecting a station can introduce some biases into our velocity data. We should consider how we can minimize this swimming/rotation when selecting our cross-section and deployment method. [Photo Description]: ADCP deployed from a tagline strung across a canal.  ]]></Notes>
<notesswfbig>notes/notesbig4.swf</notesswfbig>
<NotesHeightBig>425</NotesHeightBig>
<notesswfsmall>notes/notessmall4.swf</notesswfsmall>
<NotesHeightSmall>1027</NotesHeightSmall>
<SlideTime>106</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
</annotations>
<SlideText><![CDATA[What should I know about selecting a cross-section? Perpendicular to mean flow direction Uniform flow distribution Free of waves/turbulence Need to be able to manually observe/confirm flow angles through section Minimize swimming/rotation of ADCP ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="53b11794-d7b9-4a8c-85d5-c36e99a043a5">
<Filename>slide5.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[Do ADCPs work the same way with Mid-section (as they do for moving boat measurements)?]]></Title>
<Notes><![CDATA[Do ADCPs work the same way with Mid-section (as they do for moving boat measurements)?While the same ADCP can be used for a moving boat or mid-section discharge measurement, the software, methods and computations are quite different. As we just mentioned, ADCPs don’t track their movement across the river with a mid-section measurement, the software relies on our entry of a distance from the starting edge or an initial point. This lack of ADCP bottom tracking does provide some advantages, however. Without the need to bottom track, we eliminate potential biases due to moving bed conditions. We also eliminate bottom track errors related to vegetation on the channel bottom, uneven river bottoms, high suspended sediment, turbulent, dynamic river conditions and unsteady boat movement. Since bottom track isn’t being used, that also means that moving bed tests are not required!Since we are not collecting a continuous transect across the river, the mid-section method also allows us to optimize configuration at each vertical in cross-sections with variable depths and velocity conditions, rather than rely on one configuration for the entire measurement. When selecting a cross-section for a moving boat ADCP measurement we are usually not overly concerned if our cross-section isn’t perpendicular to the flow as the moving boat computations don’t require that it be perpendicular. With any mid-section measurement, we need to account for the angle of the flow through our cross-section, and the process of doing this will be discussed for each manufacturer.Lastly, be sure to remember that ADCP-related policies and guidance, like independent temperature checks, processing on site and maintaining a minimum of 2 valid bins, are still required for mid-section measurements. ]]></Notes>
<notesswfbig>notes/notesbig5.swf</notesswfbig>
<NotesHeightBig>324</NotesHeightBig>
<notesswfsmall>notes/notessmall5.swf</notesswfsmall>
<NotesHeightSmall>807</NotesHeightSmall>
<SlideTime>99</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
</annotations>
<SlideText><![CDATA[Do ADCPs work the same way with Mid-section (as they do for moving boat measurements)? With mid-section: ADCPs don’t bottom track-we enter the ADCP location Lack of bottom track = no bottom track biases and errors related invalid bottom track No moving bed tests required! Configuration can be optimized for each vertical  Need to minimize (or account) for flow angles Still must follow ADCP-related policies (like water temperature checks, processing on site and minimum number of valid bins) ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="0eccb843-4b7b-45c7-b41f-6a8cb10e8be4">
<Filename>slide6.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[Do I need to do anything different with my ADCP? What about cost?]]></Title>
<Notes><![CDATA[Do I need to do anything different with my ADCP? What about cost?   Another common question is whether the ADCP hardware needs to be modified, and the answer is no. While the ADCP does not require a physical change, firmware modifications may be needed. Separate software needs to be installed on the data collection device, and there is an additional cost associated with collecting data with the mid-section software from each manufacturer, and how this feature is enabled is slightly different, something we will discuss later.   ]]></Notes>
<notesswfbig>notes/notesbig6.swf</notesswfbig>
<NotesHeightBig>201</NotesHeightBig>
<notesswfsmall>notes/notessmall6.swf</notesswfsmall>
<NotesHeightSmall>369</NotesHeightSmall>
<SlideTime>28</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
</annotations>
<SlideText><![CDATA[Do I need to do anything different with my ADCP? What about cost? No ADCP modifications needed Install manufacturer mid-section software Purchase license for data collection and enable unit ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="ed30a2ec-64e9-4004-b2c2-bf3f0b8db939">
<Filename>slide7.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[Don’t take the software for granted..]]></Title>
<Notes><![CDATA[Don’t take the software for granted.. While both manufacturer software packages seem stable and reliable, they are both relatively new. When using the mid-section method, be sure to collect comparison data in the conditions you will routinely use the method and submit comparisons to the OSW Sharepoint site, using the address shown.  When collecting and processing data, look for potential issues. Be sure that manual entries into the software are carried forward correctly and ensure that each station has the correct location, transducer depth, field notes and other settings before collecting data. Also ensure that automatic calculations (like flow angles) look reasonable based on actual river observations before moving on to the next station.  ]]></Notes>
<notesswfbig>notes/notesbig7.swf</notesswfbig>
<NotesHeightBig>191</NotesHeightBig>
<notesswfsmall>notes/notessmall7.swf</notesswfsmall>
<NotesHeightSmall>425</NotesHeightSmall>
<SlideTime>42</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
</annotations>
<SlideText><![CDATA[Don’t take the software for granted.. This method/software for ADCPs is relatively new Collect comparison data  Look for potential issues during data collection/processing Confirm software readings with river observations  OSW Sharepoint:  https://xcollaboration.usgs.gov/wg/oswha/Testing/default.aspx ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="4cb2b4fb-cc54-4ed8-b2b2-6f60febb7eb2">
<Filename>slide8.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[Extrapolation]]></Title>
<Notes><![CDATA[ExtrapolationAs with moving boat measurements, ADCPs estimate the top and bottom unmeasured areas using extrapolation methods that can be changed by the user. Be sure to review the profile plots in RiverSurveyor Stationary Live and SxS Pro to ensure the default power extrapolation is reasonable. Use of the extrap program is not necessary as the software displays the average profile for each vertical. Often, the same extrapolation method will be used for the entire measurement, though there may be cases where the method may vary on a per station basis, depending on channel conditions.[Photo Description]: Left; Screen capture of the profile plot from RiverSurveyor Stationary Live. Right; Screen capture of the profile plot from SxS Pro. ]]></Notes>
<notesswfbig>notes/notesbig8.swf</notesswfbig>
<NotesHeightBig>182</NotesHeightBig>
<notesswfsmall>notes/notessmall8.swf</notesswfsmall>
<NotesHeightSmall>385</NotesHeightSmall>
<SlideTime>36</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="337.125" ypos="148.625" color="0xC00000" alpha="100" show="11500" hide="13500" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="659.375" ypos="272.625" color="0xC00000" alpha="100" show="13500" hide="15100" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
</annotations>
<SlideText><![CDATA[Extrapolation	 ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="86b083eb-2864-4f8b-a922-b679cbada56e">
<Filename>slide9.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[TRDI - Enabling an ADCP]]></Title>
<Notes><![CDATA[TRDI - Enabling an ADCP Now, let’s discuss some TRDI SxS Pro-specific considerations, starting with how to enable an ADCP for data collection. First, contact TRDI or the HIF to purchase a license for data collection. They will be able to provide specifics on the cost, and any supplemental information needed to activate the unit. Once you have purchased the section by section option, there are two steps. The first is to enable section by section in the unit using the executable provided by TRDI. Then,  the software key needs to be entered into SxS Pro by selecting Help from the menu, then Register ADCP…In the dialog box the appears, simply enter the ADCP serial number and the registration code you were provided with. This code needs to be entered into every laptop that will use this device, so it’s a good idea to have the code noted on the ADCP or kept with the ADCP in the event a hydrographer needs it in the field. Here you can see I have several ADCPs already enabled. [Photo Description]: Left top; Screen capture of the Help menu options in TRDI’s SxS Pro. Left bottom; Screen capture of the ADCP Registration dialog in TRDI’s SxS Pro software. Right; Screen capture of the TRDI NGSPActivate dialog. ]]></Notes>
<notesswfbig>notes/notesbig9.swf</notesswfbig>
<NotesHeightBig>240</NotesHeightBig>
<notesswfsmall>notes/notessmall9.swf</notesswfsmall>
<NotesHeightSmall>574</NotesHeightSmall>
<SlideTime>62</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="664.5" ypos="266.625" color="0xC00000" alpha="100" show="29600" hide="32100" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="276.5" ypos="143.375" color="0xC00000" alpha="100" show="36600" hide="42800" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="312.375" ypos="436.875" color="0xC00000" alpha="100" show="42800" hide="48700" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="lightbox" xpos="89.125" ypos="245.75" width="205.25" height="133.75" color="0x0D0D0D" alpha="50" show="58300" hide="61200" bordercolor="0xFFFFFF" borderalpha="100" animationtype="draw" loopcount="1" boxradius="5" borderwidth="2"/>
</annotations>
<SlideText><![CDATA[TRDI - Enabling an ADCP ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="f6876d18-7c34-4ca4-89e2-e296b4152485">
<Filename>slide10.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[TRDI - Starting a Measurement]]></Title>
<Notes><![CDATA[TRDI - Starting a MeasurementAfter connecting to the unit through the Configure, ADCP Port Settings menu, set the ADCP clock in the Acquire menu and run an ADCP test from the Tests menu. There is an option to calibrate the compass through the Tests menu. Currently, only the Rio Grande and Honeywell RiverRay compass can be calibrated in SxS Pro, the ISM compass in the RiverRay and StreamPro needs to be calibrated in WinRiver II before opening SxS Pro. The compass data is used to account for boat rotation and transform velocity data into the earth coordinate system, and while a compass calibration is not necessary for every measurement, understand that significant errors in the compass from a previous calibration could introduce uncertainty into a mid-section measurement.Once these tests are complete, open the New Measurement dialog from the File menu, or by selecting Control-W. When the unit connects, you will notice the page update based on the unit you’ve connected to. Fill out the station information and file naming information at the top of the dialog. Regardless of the unit you are using, you will leave the data collection duration to 40 seconds for each vertical and enter an ADCP depth, which can be edited before collecting each vertical.Leave the discharge method to mid-section, the method used by the USGS. For velocity method, only magnitude should be used, which requires the user to enter a flow angle for each vertical. Y-velocity is the other option here, but should only be used for ice measurements as it requires the unit to be held at a fixed orientation.If a RiverRay is selected, there are no other options as the unit auto-configures.[Photo Description]: Screen capture of the New Measurement dialog with a RiverRay in the SxS Pro software.]]></Notes>
<notesswfbig>notes/notesbig10.swf</notesswfbig>
<NotesHeightBig>342</NotesHeightBig>
<notesswfsmall>notes/notessmall10.swf</notesswfsmall>
<NotesHeightSmall>822</NotesHeightSmall>
<SlideTime>101</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="343.875" ypos="284.625" color="0xC00000" alpha="100" show="54900" hide="58200" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="538.75" ypos="131.5" color="0xC00000" alpha="100" show="59600" hide="62400" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="543.875" ypos="197.125" color="0xC00000" alpha="100" show="62400" hide="65700" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="358.125" ypos="370.5" color="0xC00000" alpha="100" show="65700" hide="76000" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="341.625" ypos="408.5" color="0xC00000" alpha="100" show="76000" hide="89000" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
</annotations>
<SlideText><![CDATA[TRDI - Starting a Measurement ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="08af25c1-f908-4067-baba-6152f02e975b">
<Filename>slide11.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[TRDI - Starting a Measurement]]></Title>
<Notes><![CDATA[TRDI - Starting a MeasurementIf a StreamPro is selected, the ADCP setup information on the right should be populated, including the channel depth and velocity conditions, as well as selection of a water mode. In open water, select the use compass option, leave long range enabled and use the default cell size and number of cells. For a Rio Grande, you would populate the channel depth and velocity conditions, the streambed type, and typically leave bottom mode and water mode set to auto, unless you knew a specific mode that would provide the best results based on your conditions. Use of secondary depth is not necessary with the Rio Grande as you can stop pinging at any time during the measurement and return to this page to optimize your configuration for each vertical, if needed. This can also be done with the StreamPro, as well.[Photo Description]: Left; Screen capture of the New Measurement dialog with a StreamPro in the SxS Pro software. Right; Screen capture of the New Measurement dialog with a Rio Grande in the SxS Pro software.]]></Notes>
<notesswfbig>notes/notesbig11.swf</notesswfbig>
<NotesHeightBig>240</NotesHeightBig>
<notesswfsmall>notes/notessmall11.swf</notesswfsmall>
<NotesHeightSmall>502</NotesHeightSmall>
<SlideTime>48</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="154.375" ypos="254" color="0xC00000" alpha="100" show="2300" hide="6100" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="320.625" ypos="255.375" color="0xC00000" alpha="100" show="6100" hide="10500" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="254" ypos="312.25" color="0xC00000" alpha="100" show="10500" hide="15500" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="319.875" ypos="339.875" color="0xC00000" alpha="100" show="15500" hide="18100" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="511.75" ypos="254.75" color="0xC00000" alpha="100" show="19800" hide="22500" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="674.25" ypos="258.375" color="0xC00000" alpha="100" show="22500" hide="24600" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="675.75" ypos="301.75" color="0xC00000" alpha="100" show="24600" hide="28100" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
</annotations>
<SlideText><![CDATA[TRDI - Starting a Measurement ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="a66d67c5-f858-4cbd-9712-8f32c674c633">
<Filename>slide12.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[TRDI - Collecting data]]></Title>
<Notes><![CDATA[TRDI - Collecting data	 Once the unit is configured and ready to go, the software will prompt you for starting edge information, then bring you to the configuration page for the next vertical, shown here. Confirm the extrapolation method, typically left to the standard power/power during data collection, enter the distance from the initial point, confirm the ADCP depth and note any flow angle. Since “magnitude” is the method used for open water measurements in SxS Pro, the flow angle must be measured. Measure the flow angle using a protractor or paper field form, and enter that reading as a coefficient, like 0.98, or an angle, like 13 degrees. The water depth source is something we will discuss on the next slide. Make notes as needed, and hit record or F5 to begin the vertical.  Also notice on this dialog that there is a water track error velocity for each vertical. This is due to the fact that the unit can be configured for each vertical, and this setting is configured by the software once configuration changes are made.  [Photo Description]: Screen capture of the Vertical dialog in TRDI’s SxS Pro software; Courtesy TRDI.  ]]></Notes>
<notesswfbig>notes/notesbig12.swf</notesswfbig>
<NotesHeightBig>275</NotesHeightBig>
<notesswfsmall>notes/notessmall12.swf</notesswfsmall>
<NotesHeightSmall>626</NotesHeightSmall>
<SlideTime>62</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="240.5" ypos="142.625" color="0xC00000" alpha="100" show="11000" hide="16300" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="594.875" ypos="161.375" color="0xC00000" alpha="100" show="16300" hide="26500" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="lightbox" xpos="498.25" ypos="204.625" width="119.875" height="55.25" color="0x0D0D0D" alpha="50" show="29100" hide="37900" bordercolor="0xFFFFFF" borderalpha="100" animationtype="draw" loopcount="1" boxradius="5" borderwidth="2"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="605.375" ypos="252.5" color="0xC00000" alpha="100" show="40900" hide="43900" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="325.125" ypos="286.75" color="0xC00000" alpha="100" show="43900" hide="45500" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="325.875" ypos="389.875" color="0xC00000" alpha="100" show="45500" hide="47800" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="300.375" ypos="245" color="0xC00000" alpha="100" show="50500" hide="53800" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
</annotations>
<SlideText><![CDATA[TRDI - Collecting data ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="1e635d68-8529-4901-83e1-5be6735ac3a3">
<Filename>slide13.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[TRDI - Water Depth Source]]></Title>
<Notes><![CDATA[TRDI - Water Depth Source The water depth source determines how the software will get a depth for that vertical. As a default, use Bottom Track, which uses the average depth measured by the 4 beams. Vertical beam might be an option, if you are using a RiverRay with that feature. Composite will use the vertical beam, if available, and use bottom track otherwise. The manual depth might be useful if the ADCP is having issues detecting the bottom depth, and can be entered once measured using a wading rod, survey rod, weighted line, or some other method. Depths from intermittent valid pings from SxS Pro might also be used. Once the manual depth has been measured, select manual depth as the source and enter the value. There are many cases where the ADCP can’t measure a depth, but with a manual depth, can still measure a valid water profile. Depth source can be changed after the data is collected.  [Photo Description]: Screen capture of the Vertical dialog in TRDI’s SxS Pro software.  ]]></Notes>
<notesswfbig>notes/notesbig13.swf</notesswfbig>
<NotesHeightBig>275</NotesHeightBig>
<notesswfsmall>notes/notessmall13.swf</notesswfsmall>
<NotesHeightSmall>593</NotesHeightSmall>
<SlideTime>54</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
</annotations>
<SlideText><![CDATA[TRDI - Water Depth Source ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="07c52d36-85c9-410c-ba1d-d9ab6916ae74">
<Filename>slide14.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[TRDI - Processing Settings]]></Title>
<Notes><![CDATA[TRDI - Processing Settings The processing dialog shows settings that can be applied to the entire measurement, and has some useful features, including the ability to change data screening thresholds and the speed of sound settings. Typically, these will be left to the default settings. Notice the bottom track and water track thresholds here as well, which won’t vary based on the unit’s configuration, they remain constant. The good ensemble in cell setting is mentioned on the next slide.  In the lower right corner, you will notice a setting for reference, with ADCP and bottom as the options. The default setting for SxS Pro mid-section measurements is ADCP, which assumes the ADCP isn’t moving and references the velocity to the ADCP itself. If bottom is selected the program will remove the bottom track velocity from instrument movement, which can cause large errors in moving bed conditions. The power exponent here is used for extrapolation. While the extrapolation method is changed at the vertical, the exponent is changed here, and only applies to the entire measurement, it can’t be changed for each vertical like the method. Again, the discharge method should be mid-section and the velocity method should be magnitude. [Photo Description]: Screen capture of the Processing dialog in the SxS Pro software.  ]]></Notes>
<notesswfbig>notes/notesbig14.swf</notesswfbig>
<NotesHeightBig>308</NotesHeightBig>
<notesswfsmall>notes/notessmall14.swf</notesswfsmall>
<NotesHeightSmall>710</NotesHeightSmall>
<SlideTime>70</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="317.625" ypos="337.625" color="0xC00000" alpha="100" show="15400" hide="21300" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="314.625" ypos="442.125" color="0xC00000" alpha="100" show="21300" hide="25900" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="596.375" ypos="337.625" color="0xC00000" alpha="100" show="25900" hide="50300" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="595.625" ypos="366.75" color="0xC00000" alpha="100" show="50300" hide="63000" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="595.625" ypos="392.875" color="0xC00000" alpha="100" show="63000" hide="999999999" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
</annotations>
<SlideText><![CDATA[TRDI - Processing Settings ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="cb9aa8a6-cc33-4ab4-9f69-faf8c78f0279">
<Filename>slide15.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[TRDI - Good ens. in cell]]></Title>
<Notes><![CDATA[TRDI - Good ens. in cell Several users have shared data sets and noted one depth cell, usually near the bottom of the profile, that shows a velocity that doesn’t seem to be realistic. These depth cells are usually based on just one or two ensembles that had a velocity at that depth and SxS Pro gives you an option to screen depth cells based on the number of ensembles they are computed from. As a default, this setting will allow a depth cell to be used in a station even if that depth cell was only measured in one ensemble. If you see these outlying bins with high or low erroneous velocities, try changing this good ensembles in cell setting to screen the erroneous depth cell. Usually increasing the good ensemble in cell setting to 2 will remove these erroneous depth cells. If this setting doesn’t remove them, the water track screening thresholds can usually be changed to remove them. [Photo Description]: Left; Screen capture of data from a contour plot in the SxS Pro software. Right; Screen capture of the Processing dialog in the SxS Pro software. ]]></Notes>
<notesswfbig>notes/notesbig15.swf</notesswfbig>
<NotesHeightBig>275</NotesHeightBig>
<notesswfsmall>notes/notessmall15.swf</notesswfsmall>
<NotesHeightSmall>576</NotesHeightSmall>
<SlideTime>53</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="167.125" ypos="308.5" color="0xC00000" alpha="100" show="4100" hide="11100" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="594.875" ypos="342.125" color="0xC00000" alpha="100" show="22500" hide="33200" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
</annotations>
<SlideText><![CDATA[TRDI - Good ens. in cell	 ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="1633deb9-1442-4916-b0d8-9c92997a829a">
<Filename>slide16.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[SonTek - Enabling an ADCP]]></Title>
<Notes><![CDATA[SonTek - Enabling an ADCP Now, let’s move our discussion to the RiverSurveyor Stationary Live software, or RSSL, starting with how to enable an ADCP. Unlike SxS Pro, an ADCP to be used with RiverSurveyor Stationary Live is activated by purchasing a firmware license or access code; pricing information can be obtained by contacting SonTek or the HIF. After purchasing the code, connect to the unit using the SonTek Utilities program and select Security Options, which will bring up the Security Options dialog. In this dialog, select Enable System Option, where you enter the code provided by SonTek. Once activated, this ADCP can connect to any laptop with the RSSL software installed and collect data. [Photo Description]: Left; SonTek Utilities dialog when connected to a SonTek RiverSurveyor M9; Courtesy Kevin Labbe. Right; Security Options dialog from the SonTek Utilities software; Courtesy Kevin Labbe. ]]></Notes>
<notesswfbig>notes/notesbig16.swf</notesswfbig>
<NotesHeightBig>208</NotesHeightBig>
<notesswfsmall>notes/notessmall16.swf</notesswfsmall>
<NotesHeightSmall>492</NotesHeightSmall>
<SlideTime>46</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="308.625" ypos="192" color="0xC00000" alpha="100" show="27000" hide="30200" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="469" ypos="123.25" color="0xC00000" alpha="100" show="30200" hide="33200" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="135" xpos="658.625" ypos="341.375" color="0xC00000" alpha="100" show="33200" hide="37900" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
</annotations>
<SlideText><![CDATA[SonTek - Enabling an ADCP ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="665cafdb-fcb9-45e6-b3af-71c874ae72c9">
<Filename>slide17.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[SonTek - Starting a Measurement]]></Title>
<Notes><![CDATA[SonTek - Starting a Measurement	 Once connected to the ADCP, you are brought to the Start Page, where you can set the ADCP clock, run a system test and perform the compass calibration. The compass calibration and it’s importance will be discussed on the next slide. Once the pre-measurement tests are done, go through the steps of entering site information and system settings.  In system settings, you notice an option for setting the tagline azimuth, we will discuss this on the next slide. You can also enter the measured salinity value for your cross-section as well as set the track reference and depth reference. For track reference, leave the default of System selected. Bottom track is the other option, and should not be used as it could introduce errors caused by bottom track biases like a moving bed condition. For depth reference, using either vertical beam or bottom track is fine as the data can be reviewed and this setting changed during playback. The discharge method is left to mid-section, as this is the method used by the USGS. If the ADCP thermistor was broken, you could enter a measured river temperature or a computed speed of sound in the sound speed correction area. [Photo Description]: Screen capture of the RiverSurveyor Stationary Live Start Page with the System Settings dialog open; Courtesy Paul Campbell. ]]></Notes>
<notesswfbig>notes/notesbig17.swf</notesswfbig>
<NotesHeightBig>308</NotesHeightBig>
<notesswfsmall>notes/notessmall17.swf</notesswfsmall>
<NotesHeightSmall>726</NotesHeightSmall>
<SlideTime>68</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="493.75" ypos="428" color="0xC00000" alpha="100" show="8200" hide="13800" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="467.5" ypos="235.25" color="0xC00000" alpha="100" show="23700" hide="26600" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="476.5" ypos="268.875" color="0xC00000" alpha="100" show="36700" hide="45400" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="478" ypos="287.5" color="0xC00000" alpha="100" show="45400" hide="53300" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="478" ypos="303.25" color="0xC00000" alpha="100" show="53300" hide="58600" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="479.5" ypos="361.5" color="0xC00000" alpha="100" show="58600" hide="999999999" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
</annotations>
<SlideText><![CDATA[SonTek - Starting a Measurement ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="0f190a69-1680-472f-8e0c-97f8a7ec948d">
<Filename>slide18.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[SonTek - Accounting for Angles]]></Title>
<Notes><![CDATA[SonTek - Accounting for Angles In RSSL there are two options for angle adjustment, which can be changed on a per station basis or for the entire measurement in the station configuration page, shown here. The first option is to use the internal compass to account for flow angles, which is referred to as ENU. The second is referred to as XYZ, and requires the unit to be held at a fixed orientation to the cross-section, much like we would do with a FlowTracker, and is not practical with most open water mid-section deployments. Using the compass with the ENU method is the preferred method in RSSL. Using this method requires the compass first be calibrated using the software’s tool in the Start Page. [Photo Description]: Screen capture of the Station dialog in the SonTek RiverSurveyor Stationary Live software.]]></Notes>
<notesswfbig>notes/notesbig18.swf</notesswfbig>
<NotesHeightBig>208</NotesHeightBig>
<notesswfsmall>notes/notessmall18.swf</notesswfsmall>
<NotesHeightSmall>442</NotesHeightSmall>
<SlideTime>44</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
</annotations>
<SlideText><![CDATA[SonTek - Accounting for Angles ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="0f190a69-1680-472f-8e0c-97f8a7ec0301">
<Filename>slide19.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[SonTek - Accounting for Angles]]></Title>
<Notes><![CDATA[SonTek - Accounting for Angles  Once the calibration is complete, select change system settings on the Start Page. There, you will be able to select get tagline azimuth, which will open a new dialog.  As you can see in the get tagline azimuth dialog you first orient the ADCP with the connector facing downstream, perpendicular to the tagline. This will require you to hold the hydroboard and ADCP in place, while orienting the ADCP  to the tagline the entire time. This reading is very important to the measurement, so be sure the unit is oriented correctly and that you can hold it steady for the 10 or 20 seconds recommended by the software. Once you have started the process and are finished collecting this heading data, simply press stop. Given the fact that this method relies on the compass for angle correction, it is very important you confirm the angle being measured by the unit with the actual river conditions. [Photo Description]: First; Start page in the RiverSurveyor Stationary Live Software. Second left; System Settings dialog from the RiverSurveyor Stationary Live Software; Courtesy SonTek, a Xylem brand. Second right; Get Tagline Azimuth dialog from the RiverSurveyor Stationary Live Software; Courtesy SonTek, a Xylem brand. ]]></Notes>
<notesswfbig>notes/notesbig19.swf</notesswfbig>
<NotesHeightBig>292</NotesHeightBig>
<notesswfsmall>notes/notessmall19.swf</notesswfsmall>
<NotesHeightSmall>676</NotesHeightSmall>
<SlideTime>55</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
<annotation type="arrow" linkid="anArrowRnd" rotation="90" xpos="196.25" ypos="108.25" color="0xC00000" alpha="100" show="6500" hide="9600" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="90" xpos="440.5" ypos="309.25" color="0xC00000" alpha="100" show="13300" hide="21500" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
</annotations>
<SlideText><![CDATA[SonTek - Accounting for Angles ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="0f190a69-1680-472f-8e0c-97f8a7ec0305">
<Filename>slide20.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[SonTek - Accounting for Angles]]></Title>
<Notes><![CDATA[SonTek - Accounting for Angles If you observe an angle being reported by the software with the ENU method that does not agree with your river observations you can account for the angle using the XYZ method. First, change the coordinate system for that one station to XYZ. Then, ensure the ADCP is aligning itself with the mean flow direction. Ultimately, you should ensure the black connector on the ADCP is facing directly downstream, parallel to the direction the water is moving. If the ADCP is aligning itself with the flow, you can measure the angle or correction factor and enter it into the software for that one station. This method is similar to how a AA or pygmy measurement would account for an angle. With those methods, we align the meter into the flow, and apply a coefficient for that velocity from the cross-section. This coefficient could be measured with a traditional paper measurement form, or protractor, like the one shown here.[Photo Description]: Left; Screen capture of the Station dialog from the SonTek RiverSurveyor Live software. Right; Screen capture of the Angle Coefficient Protractor from the AquaCalc Pro Instruction Manual; Courtesy JBS Instruments.]]></Notes>
<notesswfbig>notes/notesbig20.swf</notesswfbig>
<NotesHeightBig>241</NotesHeightBig>
<notesswfsmall>notes/notessmall20.swf</notesswfsmall>
<NotesHeightSmall>609</NotesHeightSmall>
<SlideTime>56</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="313.125" ypos="339.875" color="0xC00000" alpha="100" show="11200" hide="34100" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="310.875" ypos="384.625" color="0xC00000" alpha="100" show="34100" hide="39000" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
</annotations>
<SlideText><![CDATA[SonTek - Accounting for Angles ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="570bd523-06df-4c3c-88c4-5b68a7863498">
<Filename>slide21.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[SonTek - Collecting Data]]></Title>
<Notes><![CDATA[SonTek - Collecting DataOnce the unit is configured, enter the start edge information and you will be taken to the Station dialog, where you enter information for the next vertical, including the distance from the initial point or the distance from the last station. The water surface type will be left to open water, and you can enter the ADCP depth, as well as the screening distance, per OSW policy.  As a reminder the screening distance should be the transducer depth plus 0.52 ft and should be set prior to data collection. There is an option for a user input water depth if the ADCP is unable to obtain one, and once measured, could be entered here.The coordinate system will remain set to ENU, which will use the compass for automated angle corrections. Notice these settings have the ability to apply that setting to the entire measurement by selecting the apply to all check box.The velocity correction factor can be used to account for a non-measured station, say water too shallow for the ADCP to measure. You would enter a user input water depth, and use a correction factor based on the velocity at the last station to account for the shallow water at the current station. Gage height information can also be entered here. The extrapolation methods can be modified using the profile extrapolation button, here.[Photo Description]: Screen capture of the RSSL Station dialog. ]]></Notes>
<notesswfbig>notes/notesbig21.swf</notesswfbig>
<NotesHeightBig>298</NotesHeightBig>
<notesswfsmall>notes/notessmall21.swf</notesswfsmall>
<NotesHeightSmall>633</NotesHeightSmall>
<SlideTime>79</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="402.375" ypos="150.875" color="0xC00000" alpha="100" show="10000" hide="14200" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="406.875" ypos="181.5" color="0xC00000" alpha="100" show="14200" hide="18100" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="421" ypos="293.5" color="0xC00000" alpha="100" show="18100" hide="22700" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="409.125" ypos="332.375" color="0xC00000" alpha="100" show="22700" hide="30000" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="406.875" ypos="316.625" color="0xC00000" alpha="100" show="30000" hide="37800" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="407.625" ypos="358.5" color="0xC00000" alpha="100" show="37800" hide="43900" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="472.75" ypos="324.125" color="0xC00000" alpha="100" show="43900" hide="51800" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="406.875" ypos="401.125" color="0xC00000" alpha="100" show="51800" hide="72200" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="411.375" ypos="431.75" color="0xC00000" alpha="100" show="72200" hide="74600" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
<annotation type="arrow" linkid="anArrowRnd" rotation="180" xpos="234.5" ypos="493.75" color="0xC00000" alpha="100" show="74600" hide="77300" bordercolor="0x0D0D0D" borderalpha="100" animationtype="bounce" loopcount="1" scale="125"/>
</annotations>
<SlideText><![CDATA[SonTek - Collecting Data	 ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="8887b010-db7b-4b7c-960b-6d5d08e390c5">
<Filename>slide22.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[Data Evaluation and Review]]></Title>
<Notes><![CDATA[Data Evaluation and Review When collecting any mid-section ADCP data, be sure to evaluate the data you are collecting while it’s being collected. While collecting data you should be reviewing the profile plot in RiverSurveyor Stationary Live for possible SNR separation due to air entrainment. With any instrument, confirm the angle for each station, whether it’s being measured by the ADCP or you are entering it manually. With either method, the angle for each vertical should be confirmed with river observations. Ensure stations are measuring appropriate amounts of flow, and representing changes in river depth and velocity conditions. If stations are measuring too much water, or not defining changes in velocity or depth, be sure to insert new stations before the measurement is closed. Be sure that manual entries into the software are carried forward correctly and ensure that each station has the correct location, transducer depth, field notes and other settings before collecting data.   ]]></Notes>
<notesswfbig>notes/notesbig22.swf</notesswfbig>
<NotesHeightBig>241</NotesHeightBig>
<notesswfsmall>notes/notessmall22.swf</notesswfsmall>
<NotesHeightSmall>542</NotesHeightSmall>
<SlideTime>57</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
</annotations>
<SlideText><![CDATA[Data Evaluation and Review During collection:  SonTek-Review SNR plots for separation Confirm angles (either those entered manually or those measured by software) Confirm flow in each station < 5% Confirm velocity/depth conditions are being represented Insert new stations before the measurement is closed Confirm any manual entry (location, transducer depth, field notes, etc)  ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="a123a119-c132-4b64-98a4-e80d667d8aaa">
<Filename>slide23.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[Data Evaluation and Review]]></Title>
<Notes><![CDATA[Data Evaluation and Review During playback, there are some basic checks we can perform before leaving the site. Were pre-measurement tests, like a system test, ADCP test or compass calibration performed and error free? Are basic settings, like coordinate reference, velocity method and discharge method correct? Is the battery voltage reasonable? Is the number of stations appropriate to define the measured discharge and the channel conditions? Were there enough depth cells in each vertical and were there a large number of invalid ensembles or samples?  A very quick way to identify major issues with angle correction is to look over angles displayed above the contour plot. In SxS Pro, errors are caused by a user input error, while errors in RiverSurveyor Stationary Live are likely attributed to a compass issue.  As for a moving boat measurement, RiverSurveyor Stationary Live and SxS Pro measurements can be locked after final review is complete and backed up to a USB drive.    ]]></Notes>
<notesswfbig>notes/notesbig23.swf</notesswfbig>
<NotesHeightBig>308</NotesHeightBig>
<notesswfsmall>notes/notessmall23.swf</notesswfsmall>
<NotesHeightSmall>593</NotesHeightSmall>
<SlideTime>60</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
</annotations>
<SlideText><![CDATA[Data Evaluation and Review During playback:  Look over pre-measurement tests (system test, ADCP test, compass cal, etc) Are basic settings correct? (coordinate reference, velocity method, discharge method, etc) Check battery voltages Appropriate number of stations? Were the number of invalid and valid bins/ensembles reasonable? Do angles plotted over contour plot look reasonable?  ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="eb5ee22d-2a9d-484a-94fb-94e7e4cd4d09">
<Filename>slide24.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[Could you summarize all of this?]]></Title>
<Notes><![CDATA[Could you summarize all of this? Now, let’s highlight some of the main points we covered in this talk. First, don’t forget this software and technique is relatively new, so collect comparison data and submit it to the OSW Sharepoint page. Also, be sure you are following applicable policies for moving boat ADCP measurements, like temperature comparison checks and processing on site. Moving bed tests are not required! With SxS Pro, you must manually observe and enter flow angle corrections, while the RSSL software will use the compass to account for flow angles; you have to be sure you are confirming those angles with river observations.  Manual depths can be used in cases where the ADCP can’t obtain a depth on it’s own, particularly in areas with vegetation or a very uneven bottom. Keep in mind how these conditions might affect your ability to measure velocity, however. It is very important that you confirm what you are seeing in the software with what’s happening in the river, too often with ADCPs we trust the software, without using our experience and hydraulic knowledge to confirm what we are seeing. Lastly, please ask questions. It’s common to hear from users who have been dealing with hardware and software issues for quite some time, issues that could have been easily remedied had they sought out help.  ]]></Notes>
<notesswfbig>notes/notesbig24.swf</notesswfbig>
<NotesHeightBig>324</NotesHeightBig>
<notesswfsmall>notes/notessmall24.swf</notesswfsmall>
<NotesHeightSmall>760</NotesHeightSmall>
<SlideTime>79</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
</annotations>
<SlideText><![CDATA[Could you summarize all of this? Collect comparisons Follow policy- WT checks, process on site TRDI-enter angles manually SonTek-make sure the measured angles are correct! Manual depths can be entered when unit won’t obtain one Make sure what you are seeing in the software makes sense Ask questions! ]]></SlideText>
<framerate>30</framerate>
</Slide>
<Slide id="6fbfc89f-e5bd-4f6f-80d9-ef24b2d3290b">
<Filename>slide25.swf</Filename>
<BackgroundFile>bgd1l3.swf</BackgroundFile>
<Title><![CDATA[Where do I go for help?]]></Title>
<Notes><![CDATA[Where do I go for help? While it seems several offices are using ADCPs with the mid-section method, it also seems that communication between these offices is relatively minimal. It also seems that some offices who are new to the technique are not sure where to go with questions.  If you have questions on the equipment, software, deployment options or methods when using ADCPs with this method there are two main options. The first is to email the USGS Hydroacoustics Work Group. The email address to reach the group is shown here. Another option is to post a topic on the OSW Hydroacoustics forum, which has a specific area for posts relating to mid-section measurements. In addition to these resources, an often under-utilized resource is the manual or help section of both SxS Pro and RiverSurveyor Stationary Live.  For those users who are more experienced, consider sharing what’s worked and what hasn’t worked on the forum so the information is there for those just getting started. We thank you for taking the time to watch this informational video….look forward to more information from the Office of Surface Water and the HaWG on ADCP mid-section use soon.    ]]></Notes>
<notesswfbig>notes/notesbig25.swf</notesswfbig>
<NotesHeightBig>392</NotesHeightBig>
<notesswfsmall>notes/notessmall25.swf</notesswfsmall>
<NotesHeightSmall>726</NotesHeightSmall>
<SlideTime>69</SlideTime>
<waitforuser>true</waitforuser>
<Hidden>false</Hidden>
<navlocked>false</navlocked>
<branch>
<prev>default</prev>
<next>default</next>
</branch>
<DisplayMode></DisplayMode>
<level>0</level>
<PlayListId>-1</PlayListId>
<annotations>
</annotations>
<SlideText><![CDATA[Where do I go for help? Contact the Hydroacoustic Work Group (HaWG) hawg@simon.er.usgs.gov  Use the OSW Hydroacoustic Forum Mid-Section discussion area: https://simon.er.usgs.gov/smf/index.php?board=7.0  Use the software manual/help section   ]]></SlideText>
<framerate>30</framerate>
</Slide>
</Slides>
</Presentation>
