V-Track Graphical User Interface User Manual
Contents
1. 2 2 2 663190 119395 27632 9 35399 88 1038 2 13890 e l 180468 26899 10026 9804 371 20 36 816446 66531 2267940 19298 77 6 18 The output file for residence and non residence events contains the following items DATETIME the date and or time an event was initiated For example an event at 2012 01 08 12 20 21 will be 2012 01 08 12 00 00 for Hour 2012 01 08 for Day 02 for Week 01 for Month and 12 for Circadian TRANSMITTER ID the ID code of the transmitter FREQ the number of events that occurred in that hour day week month TIMESUM the total residence or non residence time for that hour day week month TIMEMAX the maximum event duration reading for that hour day week month TIMEAV the mean duration of an event in seconds for that hour day week month TIMESTDDEV the standard deviation of the event duration by hour day week month in seconds The below table shows an example output file containing a weekly profile for temperature events DATET TRANSMITT FREQ SENSORM SENSO SENSORST TIMES TIMEM TIMEA TIMEST DETECTI IME ERID AX RAV DEV UM AX V DEV ONS 30319 14820 10106 2 5 4 28 6 28 43 0 288675 58676 28 333 64 1o E e a 2 2 2 24 DATETIME TRANSMITTER ID FREQ SENSORMAX SENSORAV OBE NSORSTDEV TIME SUM TIMEMAX TIMEAV TIMES TDDEV V Track GUI Manual v1 02 the date and or time an event was initiated For example an event at 2012 01 08 12 20 21 will2. Extract events tab The following screen will be displayed V Track GUI versie 7 Step 1 Add to archive Step 2 Extract from archive Step 3 Generate distance matris Step 4 Extract events Step 5 Temporal cond_4 Input file Cc WW Track NEW ARCHIVE ce Browse Distance Maitre Input File from Step 3 E W Track Ocean Arap Recerver Distance Matris cew Browse Output file IC W Track HORIZONTAL MOVEMENT cew Browse Event Parameters 7 ite Detech it tation Event Type Termination window 240 E E i Horizontal movement C0 Sensor Window unit Minutes Extract data from archive Cancel 4 1 Qualifying horizontal movement Checking the Horizontal movement box will result in V Track identifying periods within the detection data when the tagged animals were within or between receiver detection fields The event is triggered every time a transmitter is detected by a new receiver and terminated when the transmitter is detected at another receiver or if the transmitter is not detected by the same receiver within a user defined Termination window This Termination window may be defined as seconds minutes or hours within the Window unit dropdown box Users may also set the Detection unit of interest to Receiver or to Station In order to minimise the risk of 15 V Track GUI Manual v1 02 erroneous pings a minimum of two successive transmitter pings must be detected at receiver for a reside
3. a sensor event Logfile is created Each detection is provided with a SENSOREVENT index code to indicate which event it is associated with in the sensor event file DATETIME SENSOREVENT RECORD TRANSMITTERID RECEIVERID SENSOR1 ELAPSED 2008 11 30 3 0 101 103565 0 08 0 15 41 51 2008 11 30 3 1 101 103565 1 30 483 15 49 54 2008 11 30 3 2 101 103565 1 40 1026 15 58 57 2008 11 30 3 3 101 103565 1 80 1587 16 08 18 2008 11 30 3 4 101 103565 2 10 2298 16 20 09 2008 11 30 3 5 101 103565 0 20 3027 16 32 18 DATETIME the date and time that the information was logged at the receiver SENSOREVENT this number corresponds to the SENSOREVENT number in the sensor event file RECORD the position that this detection is placed within the event RECORD 0 represents the beginning of the event TRANSMITTERID the transmitter id from which the events were determined RECEIVERID the receiver where the event occurred ELAPSED the total duration of the event in seconds 22 V Track GUI Manual v1 02 5 Generating temporal profiles of events This step organises the residence non residence or sensor events generated from Step 4 into profiles classified by temporal conditions By specifying the time profile as hour day week or month the respective time profile is extracted for that particular event Users can also extract a circadian profile for each event where events are filtered for each hour in the diel cycle 24hr and summed across days Once
4. an event catalogue has been created click the Step 5 Temporal conditions tab The following screen will be displayed O Track GUI version LIA xP Step 2 Extract from archive Step 3 Generate distance matrix Step 4 Extract events Step amp Temporal conditions Step 6 Generate _4 Input event file C s Track NONRE SIDENCE csv Browse Output file C S Track NONRE SIDENCE_24h csv Browse Period C Hour C Day C Week f Month Temporal Qualifier S TSATTIME Extract profile Cancel In the Input file field enter the location of the event file generated in Step 4 or alternatively browse to the location of the event file In the Period field select which profile should be extracted i e Hour Day Week Month Circadian In the Temporal Qualifier field select if you want each event to be categorised by the STARTTIME or ENDTIME of each event In the Output file field enter the location and name of the file to be created or alternatively browse to the specified location using the Browse tab 23 V Track GUI Manual v1 02 Click Extract profile to generate the new distance matrix file containing the pairwise distances minus the user defined detection distances 5 1 Temporal profile output files The below table shows an example output file containing a diel profile midnight to 4am for residence events 339434 66089 14143 0 18569 46 522 8 151494 19655 6886 09 7089 859 232 a 974 6
5. depth sensor event for an individual transmitter The Trend has been selected for decreasing changes in depth Each number represents a single detection the number O represents the start of an event and the event is composed of 6 detections in total a The trigger threshold was set to gt 0 5 m b the trigger window was lt 10 minutes c the sensor termination threshold was lt 0 5 m from the starting value and d the termination threshold was lt 60 minutes between detections If more than 60 minutes passes between successive detections during the event a timeout will be returned as the ENDREASON for a sensor event Id 139 event 19 1 Depth mi 00 00 10 00 20 00 30 00 40 00 20 00 Event duration 20 V Track GUI Manual v1 02 In the Output file field enter the location and name of the file to be created or alternatively browse to the specified location using the Browse tab Click Extract data from archive to generate two sensor files 1 a sensor event file 2 a sensor event Logfile The details of these are as follows 4 4 Sensor event output files i Sensor event file This file contains the details about all of the sensor events START END SENSOR TIME TIME EVENT 2008 2008 1 08 18 08 19 23 22 0 00 17 3 9 4 2008 2008 Z 08 19 08 19 10 18 1 10 58 5 2008 2008 3 11 30 11 30 15 41 5 16 32 1 STARTT IME BNDTIME SENSOREVENT TRANSMITTERID RECEIVERID DURATION SOTARTSENSO
6. event which is referenced within the residence event logfile see below TRANSMITTERID the transmitter code for the event RECEIVERID the receiver which recorded the event DURATION the time in seconds from the first to last detection within the event ENDREASON this informs that the data was scored as an event due to the animal appearing at another receiver or if the last detection had passed the user defined timeout threshold NUMRECS the number of acoustic detections comprising the event 16 ii Residence event logfile V Track GUI Manual v1 02 In order to explore the raw data that comprises each residence event a residence event logfile is also created by V Track In the example below the details of all the acoustic detections that comprise RESIDENCE EVENT 2647 are shown RECORD TRANSMITTERID 45 45 45 45 45 45 45 45 45 45 RECEIVERID LOLLS2 LOTS 2 101152 COLLA LOTLS2 LOLL LOLLIS Z LO TZ LOLLSZ LOT 2 ELAPSED O LGL 18 a3 de 34 og 17 18 18 the date and time that the acoustic detection was logged at the receiver corresponds to the RESIDENCEEVENT index number in the residence event the number of the acoustic detection within this particular residence event the transmitter ID to which the event belongs the receiver ID where the event occurred DATETIME RESIDENCEEVENT 2008 04 20 2647 0 05 04 00 2008 04 20 2647 1 05 07 00 2008 04 20 2
7. name of the file to be created or alternatively browse to the specified location using the Browse tab 3 4 The receiver distance matrix file Click Extract data from archive to generate the Receiver Distance Matrix This will show a list of all the receivers within the array on the first row and column and the relative distance meters between each receiver and all the other receivers within the array DM 101156 101152 101154 101151 101141 101142 101155 OT LaG O Laa 0 15650 17600 19400 2 LAO Z2000 101152 L3370 O 1580 3530 J330 7030 B330 101154 L39650 1580 O 1230 3050 4750 6250 101151 17600 3530 1250 O LLOU 2800 4300 101141 19400 5330 3050 1100 O 1000 2500 101142 ALLOY 7030 4150 2800 1000 O 800 i OMe rs 22600 8530 6250 4300 2000 800 O 14 V Track GUI Manual v1 02 4 The event analyser This function identifies and quantifies events within the acoustic detection database These can be horizontal movement events based upon the presence of tagged animals at adjacent receivers or sensor events commonly used as a proxy for vertical movement based upon depth or temperature sensor information V Track defines these events from user defined threshold and timeout parameters The qualification of an event will need to be tailored to each study and will depend upon the study animal the environment the tag transmission rate receiver arrangement and the biological questions asked Once an archive has been created click the Step 4
8. this step to generate the archive file e Step2 bat containing the batch or MS DOS information for the processed file 11 V Track GUI Manual v1 02 3 Distance matrix generator Once an archive has been created click the Step 3 Generate distance matrix tab The following screen will be displayed a V Track GUI version 1 07 po Step O A project install path Step 1 Add to archive Step 2 Extract from archive Step 3 Generate distance matrix Step 4 Extract e_4 Input POINTS file IC AV Track d cean Point file ce Browse Output file IC AV Track d cean Aray Receiver Distance Matrix ce Browse Recerver Matix Calculation f Direct f Circuitous Extract data from archive nn _ This function calculates the distance between the VR2 or VR2 W receiver detection field within the array i e the Receiver Distance Matrix V Track calculates the distance based upon the geographical coordinates of each receiver minus the detection radius m of each receiver The Spatial information provided by the Receiver Distance Matrix is used by V Track in Step 4 to calculate individual movement rates V Track offers two different methods for calculating the Receiver Distance Matrix The user can select by checking the appropriate box 12 V Track GUI Manual v1 02 3 1 The direct distance matrix This is calculated as the shortest straight line distance between each receiver and all the other receiv
9. 647 2 05 07 00 2008 04 20 2647 3 05 08 00 2070472008 2647 4 05 08 00 2008 04 20 2647 5 05 09 00 2008 04 20 2647 6 05 10 00 2008 04 20 2647 7 052 10200 2008 04 20 2647 8 05 10 00 2008 04 20 2647 9 05 11 00 DATETIME RESIDENCEEVENT file RECORD TRANSMITTERID RECEIVERID ELAPSED the period in seconds between consecutive acoustic detections 17 V Track GUI Manual v1 02 iii NONRESIDENCES event file This file contains details of the period when a transmitter leaves the detection field of one receiver and arrives at another START END TIME TIME 2008 08 2008 08 22 22 21 43 00 21 58 00 2008 08 2008 08 22 22 22 49 00 23 09 00 2008 08 2008 08 23 23 00727200 05 09 00 STARTTIME ENDTIME MOVEMENTEVENT RECEIVERID1 RECEIVERID2 DURATION DISTANCE ROM RECEIV RECEIV NONRESIDEN TRANSMITT ER ER DURATI DISTAN CE EVENT ER ID ID1 ID2 ON CE ROM Ao aL bie WOLD 101142 IAD 800 0x86 24634 33 POLIS 7 101140 Laa 1350 Os LO 850 34 LOL 143 LOLTJE 16896 3290 Cee al the date and time of the last detection at the receiver the animal has left at RECEIVERIDI the data and time of the first detection at the receiver the animal has arrived at RECEIVERID2 the unique identifier for the non residence event the ID code of the receiver at the STARTTIME of the non residence event the ID code of the receiver at the ENDTIME of the non residence event between the last acoustic detection at RECEIVERIDI1 andthe first detection at RECEIVERI
10. D2 the period in seconds the distance in meters of the movement event between the two receiver detection fields as determined by the Receiver Distance Matrix If no distance matrix has been loaded into the Distance Matrix Input file field then DISTANCE O is returned the rate of movement in m s of the movement calculated from the duration of the event divided by the distance between the outer limits of the detection fields of the two receivers If no distance matrix is loaded in the Distance Matrix Input file field ROM O is returned 18 V Track GUI Manual v1 02 4 3 Qualifying sensor events If transmitters contain a sensor i e a temperature or depth sensor checking the Sensor box within the Event Type field will allow the user to extract sensor related events according to user defined sensor and time threshold values Once the sensor box is checked the following screen is displayed V Track GUI version 1 02 Step 1 Add to archive Step 2 Extract from archive Step 3 Generate distance matris Step 4 Extract events Step 5 Temporal cond_4 Input file C W Track SUB ARCHIVE csv Browse Distance Matris Input File from Step 3 Browse Output file CAV Track VERTICAL MOVEMENT csy Browse Event Parameters Event Type Trigger threshold 02 f Horizontal movement Trigger window 60 f Sensor Termination threshold i Window unit Minutes Termination window 240 Threshold unit Degrees PC Tr
11. Groups events into the hours over the diel cycle Step 6 The animation generator Creates a KML animation file that can be viewed in Google earth The animation shows periods when a transmitter is within the receiver range of a receiver and when it is moving between receiver detection ranges 28
12. R KNDSENSOR MAXSENSOR TRANSMIT RECEIVE DURATIO START END MAX END NUM TER ID R N SENSO SENSO SENSO REASON REC ID R R R S 101 103565 3325 0 0 0 0 4 1 timeout 5 101 103565 10221 oan Zod 2 6 timeout 4 101 103565 3027 0 08 0 2 2a L timeout 6 the date and time of the first detection of the event RECORD 0 the data and time of the last detection within the event the index number of the event which is referenced within the sensor event logfile the transmitter id from which sensor events were determined the receiver where the sensor event began the duration of the event in seconds from the first to last detection within the event the sensor value when the event was initialised the sensor value when the event was either completed or terminated if the event is an increasing sensor event this is the maximum sensor value attained during the event If the event is a decreasing sensor event MINSENSOR is returned here containing the minimum sensor value attained during the event 21 V Track GUI Manual v1 02 ENDREASON This providing information on why the event was terminated If the sensor returned to a value within the termination threshold from the STARTSENSOR value and within the time threshold return or exceeded the timeout threshold between successive detections timeout NUMRECS The number of records detected within each event ii Sensor event logfile In order to explore the raw data making up each sensor event
13. V Track An application programming interface for analysing and visualising data generated from the VEMCO suite of passive and active acoustic receivers Graphical User Interface User Manual F C 0 lab and Environmental Decisions Group School of Biological Sciences University of Queensland St Lucia Queensland Authors Ross Dwyer Matthew Watts amp Hamish Campbell V Track GUI Manual v1 02 V Track has been created to enable storage analysis and visualisation of detection data from the VEMCO suite of receivers and transmitters It has been written within the R programming language but has a graphical user interface GUI for uploading data and carrying out analysis routines in Microsoft Windows This manual details operation of the V Track GUI V Track consists within a sequential modular format the routine steps for the processing of the acoustic detection data are Archiving of the detection database Creation of sub archives based upon study parameters Creation of a distance matrix using direct or circuitous distances between receivers Identification of animal behavioural events within the detection sub archives Organisation behavioural events by temporal conditions Say SY Create animations to visualise animal movement in Google Earth V Track will assimilate acoustic transmissions derived from the VEMCO suite of continuous and coded tags and detected by the VR2 VR2 W and VR100 receivers This enables the user to proc
14. be 2012 01 08 12 00 00 for Hour 2012 01 08 for Day 02 for Week 01 for Month and 12 for Circadian the ID code of the transmitter the number of events that occurred in that hour day week month the maximum sensor reading that hour day week month this is only returned if a sensor event is entered asthe Input file the mean sensor reading that hour day week month this is only returned if a sensor event is entered asthe Input file the sensor value standard deviation for that hour day week month this is only returned if a sensor event is entered as the Input file the total event time for that hour day week month the maximum event duration reading for that hour day week month the mean duration of an event in seconds for that hour day week month the standard deviation of the event duration by hour day week month in seconds By collating the different events by temporal conditions the acoustic data can answer questions such as what time of year are animals most active What time of day do animals change depth in the water column and what time periods are animals not detected Mean frequency of nonresidence events 6 dT 18 20 22 Hour Mean sensor value of sensor events _ oO ED E o D N LL 0 2 E E m Ww Qo w OQ O O 0 2 4 l 8 10 12 14 16 18 20 22 Hour 25 V Track GUI Manual v1 02 6 Create animation of animal track to view in Googl
15. e Earth 6 1 Generating the Google Earth animation This step creates Google Earth animations to view when animals are within the detection field of various receivers and when they move between receivers A coloured dot is produced at the location of the receiver to demonstrate when an animal is within the detection field and a white line is produced indicating the period when an animal is between the detection fields of adjacent receivers Once an event catalogue has been created click the Step 6 Generate KML Animation tab The following screen will be displayed V Track GUI version 1 02 T E3 Step 3 Generate distance matrix Step 4 Extract events Step 5 Temporal conditions Step amp Generate KML animation Input RESIDENCE file CAV Track RESIDENCE cev Browse Input NON RESIDENCE file C S TrackSNONRESIDENCE cev Browse Input POINTS file IC AV Track cean Point file cs Browse Output file C WW TracksAnimation kml Browse Aecever map colour ia Generate animation Inthe Input RESIDENCE file field enter the location of the RESIDENCES event file generated in Step 4 or alternatively browse to the location of the event file In the Input NON RESIDENCE file field enter the location of the NONRESIDENCES event file generated in Step 4 or alternatively Browse to the location of the event file optional Inthe Input POINTS file field enter or Browse to the location of POINTS file conta
16. e of the location fix TRANSMITTERID the identity of each transmitter ID SENSORI the value of the environmental sensor i e temperature or depth at the time of detection UNITS1 the units of each sensor value m C RECEIVERID the factory assigned receiver serial number Receiver S N STAT IONNAME the user defined station name In addition to the output csv stepl Rand stepl bat and are also created in this step e Stepl1 Rcontains the R code used in this step to generate the archive file e Stepl bat contains the V Track GUI Manual v1 02 2 Querying specifics within the data Once an archive has been successfully generated V Track offers the option to sub set the data by a number of different qualifiers These can be selected individually or in combination Step O A project install path Step 1 Add to archive Step Extract from archive Step 3 Generate distance matrix Step 4 Extract e_4 Input file CAY TrackSMEW amp ACHIVE cs Browse Output file CAV Track SUB ARCHIVE csv Browse Extract quer parameters if Period Start 201 2 01 23 12 00 00 End 2012 03 01 23 59 59 Format vy MeM DD hh mm ss W Transmitter ID 1 36 452 32 Note Specify more than 1 transmitter by seperating them with a space W Receiver ID 1 01147 101148 110445 175000 Note Specify more than 1 receiver by seperating them with a space Station ID Temperature Extract data from archive A sub archive is created which c
17. ecommend reducing the size of your data file using the sub archive extraction protocols Step 2 in V Track Either reduce the number of transmitters within the animation and or the time period of the selected data 27 V Track GUI Manual v1 02 GUI Summary of Steps Step 1 V Track archive Create database from acoustic detection data VR2 VR100 or data repository Amalgamate a collection of different VEMCO acoustic detection files Add data to an existing V Track archive Sort database into chronological order Remove duplicates records from database Convert database from UMT to local time Step 2 SQL Sub archive data by time period receivers stations transmitters sensor type Step 3 Receiver distance matrix calculator Creates a matrix to define the relative distance between all receivers within the array Offers two different options for calculating the route distance between receivers within the array Step 4 The event analyser Identifies and catalogues periods when a transmitter is within the detection range of each receiver Identifies and catalogues periods when transmitter moves between the detection ranges of adjacent receivers Identifies and catalogues events based upon relative changes in the depth sensor data Identifies and catalogues events based upon relative changes in the temperature sensor data Step 5 The event organiser Groups events by temporal conditions these can be hourly daily weekly monthly
18. end Increasing Detection unit Receiver Extract data from archive Cancel In the Input file field enter the location of the archive file or alternatively browse to the location of the archive file Within the Event parameters box the user is provided with four parameters Trigger threshold Trigger window Termination threshold and Termination window The definitions of these variables are listed below Trigger threshold the minimum change in the sensor value for an event to commence Trigger window the maximum time period in which the Trigger threshold must be attained for an event to commence Termination threshold how close the sensor value must be to the starting sensor value before a sensor event is completed and the counter is reset Termination window the maximum time period between consecutive detections before the event is terminated and the counter is reset 19 V Track GUI Manual v1 02 The units for the trigger and termination window can be set to seconds minutes or hours using the Window unit dropdown menu Users can extract sensor events that are triggered by either an Increase or Decrease in the sensor value by selecting either option in the Value dropdown menu The two types of sensor offered by VEMCO in their transmitters is either temperature Degrees C ordepth Meters m and either can be selected in the Threshold unit dropdown menu The below figure shows the raw sensor data that composes a single
19. ers within the array This is the most common method for arrays deployed in a grid formation 3 2 The circuitous distance matrix This is calculated with the receivers in series The user can also add additional waypoints and V Track will calculate the route distance between adjacent receivers through these waypoints This method is most common when receivers are deployed in a linear or curtain formation 3 3 The POINTS file Inthe Input POINTS file field enter the location of the points file or alternatively Browse to the location of the points file All receivers used in the archive file must be listed in the distance matrix along with their corresponding detection radii If the detection radius is unknown the user may set this field to O The points file should be in the following format if the user is looking to create a Receiver Distance Matrix using a Direct distance calculation RECEIVERID LATITUDE LONGITUDE RADIUS 100001 12 402 MAR E 50 100002 ee L1 142 119 50 100003 ee al LAZ LOO 30 13 V Track GUI Manual v1 02 Alternatively to create a receiver distance matrix using a Ci rcuitous distance calculation then additional waypoints can be created by inserting a 0 inthe RECEIVERID field RECEIVERID LATITUDE LONGITUDE RADIUS 100001 A AO LAD LA 50 O 12 402 LAAs Lal O LA 50 8 TAZ oO 100002 S12 cod lL LAS Ll 9 50 O LA cero 142 112 100003 gles ail LA LO 9 30 In the Output file field enter the location and
20. ess data from both active and passive acoustic telemetry within a central database Archived acoustic data stored within a third party database can also be processed and visualised within V Track V Track GUI Manual v1 02 Table of Contents 0 Uploading the V Track GUT gicciehsccestooteciesacetenien abate eE siaiaicined seaenalon a 4 0 2 Exporting data from the VEMCO VUE software essessssesessessrresssrressrreresrrressreresrrreserereserreserereseerese 4 1 Creating the central archive ssesessssessssessssessssesssseossosossseosssecssoecsssecssssossseossosossssosessssese 6 ELTAC PONE ES oon E A E 6 1 2 Important information about the Datetime Field sssssssenseseenesrresssreresrrersrreresrrerssrereserersseeee 7 Diss Ea Ta E EE E E E E E E EE EEEE EE 9 2 Querying specifics within the data ccsccccccccscscsccccscsccccccscnceccccecscececsccscscescececscecessecs 10 3 Distance matrix generator esseessescesceecsesceecoescessoesoesceecoescescoesoesseecoescesceeccesseessesceeseeecee 12 3 1 The direct distance matrix essssssseeresssssssrerreesssssrerrrsssssssrereresssssererressssserereresssseeereeessseeene 13 3 2 The circuitous distance MatriX ererssiscisbscrrenrikiia in Ee n EA 13 SINE FOINT TLC o a E EE E 13 3 4 The receiver distance matrix fil ccccsssssssseccccccseeessesecccccsseeesseeececeesseeessseeeceesssaeesseseseeeesanas 14 4 The event analySer sessssesessesessecsessesesssoss
21. ining the geographical locations of the receivers this file format is described in Step 3 page 10 26 V Track GUI Manual v1 02 In the Output file field enter the location and name of the file to be created or alternatively browse to the specified location using the Browse tab The colour of the receivers to be displayed on the Google Earth image can be selected in the drop down window 6 2 Running the Google Earth animation Download Google Earth from http www google com earth index html and follow the onscreen instruction to install Double click on your kml file generated by V Track The kml file will be opened in Google Earth and the screen will zoom to the study area location All the functionality of Google Earth is now available to view your animal track animations To run the animation click on the highlighted button on the tool bar Feb 10 2010 8 02 pm If the animation is running too fast to appropriately view the animal tracks Click the blue spanner in the left corner of the tool bar This will open a window where the play speed of the animation can be reduced The time scale of the animation can also be extended or reduced through the zoom functions with the magnifying glass icons it should be possible to slow the animation down to a scale of hours and minutes If the animation does not zoom down then there is too much data within the animation Unfortunately this is the limitation of Google Earth 5 0 and we r
22. me columns Encoding No spaces in column headers UTF 8 Unicode No trailing commas ANSI V Track GUI Manual v1 02 Select the transmitters receivers or entire detection file to export Data Export a Output File C vemco database V Track Data csv File Format Comma Separated Value CSV CSV export options are configured through the global options window Tools gt Options gt Export C Legacy VR Format Data will be converted to conform with the selected map and any detections that do not fit the map will be discarded Times are in UTC MAP 110 69 kHz Sensor Format Calibrated sensor values Raw sensor values Output File Change name and location for saved file File Format Select Comma Separated Values CSV Note For V Track versions 21 01 it is no longer necessary to change the export format from the Default format to the Version 1 0 format in VUE The data export format is provided as an option in Step 1 However V Track still requires the exported File Format to be CSV V Track GUI Manual v1 02 1 Creating the central archive 1 1 The Input files While all the acoustic detection data processed by V Track are from the VEMCO suite of receivers and transmitters there may be differences in how the detection data has been processed and stored The first step in V Track is therefore to convert all detection data into a format that can be recognised and processed usi
23. nce event to occur In the Input file field enter the location of the archive file or alternatively browse to the location of the archive file In the Distance Matrix Input file field enter the Distance Matrix file address or alternatively browse to the location of the file V Track has the capacity to create the distance matrix from a point file or alternatively the matrix can be manually created by the user Please see Figure 3 4 for an example of a Receiver Distance Matrix Input file In the Output file field enter the location and name of the file to be created or alternatively browse to the specified location using the Browse tab Click Extract data from archive This will generate three horizontal movement files a residences event file a residence event Logfile and a nonresidences event file The details of these are as follows 4 2 Horizontal movement output files i RESIDENCES event file This file contains the details about all of the residence events RESIDENCE TRANSMITTE RECEIVER END NUM STARTTIME ENDTIME EVENT R ID ID DURATION REASON RECS 2007 07 28 2007 07 28 16198 45 101158 1955 timeout 38 15 16 15 49 2007 07 29 2007 07 29 16199 45 101158 849 receiver 16 13 16 13 30 2007 07 29 2007 07 29 16200 45 101157 1762 receiver 23 13 42 14 12 STARTTIME the date and time of the first detection at the receiver ENDTIME the data and time of the last detection within the receiver RESIDENCEEVENT the index number of the
24. ng the V Track analysis routines To do this Click the Step 1 Add to archive tab The following screen will be displayed V Track GUI version L 02 eg Browse Remove CM T racki TAM Stile cs AAT AMS 0 Data f t 7 ee NE Convert time to local tine W Yemco data is ald 1 0 format f WR100 dual mode O AATAMS Local time is GMT E hours C VW Track Output archive file C W Track MEW ARCHIVE cev Browse Add to archive Cancel Browse to the location of the acoustic detection data you wish to upload into V Track Then select the Data format These files may be either Exports from the VEMCO VUE software VR2 VR2 W From a VR100 receiver V100 dual mode 3 From a third party data repository Australian Acoustic Tracking and Monitoring System AATAMS 4 From an archive already produced by V Track V Track GUI Manual v1 02 5 It is also possible to define the VUE export format as Default or the old Version 1 0 Format Multiple detection data sets can be combined to create a single archive including the adding of detection data sets to existing V Track archives The time stamp for detections collected with VR2 and VR2W receivers is stored as UMT There is an option within V Track to convert the detection time stamp within each detection data file to the local time of the receiver array 1 2 Important information about the Datetime field The DateTime field in the input file must be in the f
25. ontains only the data within the user defined variables In the Input file field enter the location of the archive file or alternatively browse to the location of the archive file The Input file should be in the following format DATETIME ANIMALID SENSOR1 UNITS1 RECEIVERID STATIONNAME 2007 07 27 57 31 448 T t01141 Upper catchment o a 2007 0 727 58 sal 6 101143 Upper catchment Torpil Z007 07 2 7 54 LG ee LZ m LQ Sl Lower catchment LLG In the Output file field enter the location and name of the file to be created or alternatively browse to the specified location using the Browse tab Check each box to define the qualifying parameters from the input file Data can be selected within a Time Period by Transmitter ID s Receiver ID s Station ID s orSensor type As with Step 1 time queries should be in the format YYYY MM DD hh mm ss If more than one Transmitter Receiver or Station ID is required IDs should be separated by a space Multiple or single 10 V Track GUI Manual v1 02 parameters can be selected for and if no selection is desired for a particular parameter then the box should be left unchecked Click Extract data from archive to generate the sub archive file containing only detections qualifying the user defined parameters As with Step 1 this will generate three output files e Asub archive csv containing the raw data which falls within the selected parameters e Step2 R containing the R code used in
26. ormat yyyy mm dd hh mm ss for it to be recognised by V Track If a detection file has been created or saved as a csv in Microsoft Excel then it is likely that the DateTime field in the csv file will no longer be in a format recognisable by V Track To ensure the DateTime field is in the correct format use the following steps Open the document in Microsoft Excel Select the entire Date Time column click the right mouse button and select Format Cells 3 In the Number tab select Custom and in the Type field enter yyyy mm dd hh mm ss 4 Click OK then Save and close the program as a CSV Comma delimited csv file V Track GUI Manual v1 02 Format Cells 0 Red 420 0 00 240 00 0 00 Red 0 00 270 5 0 Type the number format code using one of the existing codes as a starting point Microsoft Excel 2010 window to format time and date into required V Track format V Track GUI Manual v1 02 1 3 The output files Once the user has completed he table in Step 1 successfully and clicked Add to archive V Track will generate a new detection archive containing all the files listed in the input file box This step is required to 1 ensure all selected items are combined in a format consistent with the V Track analysis tools 2 sort each detection in chronological order and 3 remove any duplicate detections The output csv file will contain the following columns DATETIME the date and tim
27. ram and the V Track R package to be installed on their machine The R software can be downloaded from http www r project org The V track R package can be downloaded from http www ug edu au eco lab v track Unzip the package and place the folder entitled V Track into the library folder in the R program The directory for the V track R package will now be something like C Program Files R R 3 0 2 library V Track Download the V Track GUI from http www uq edu au eco lab v track Unzip the folder and click on the V Track executable i e V Track exe The V Track Setup Wizard will open follow the instructions Once installed the V Track GUI will automatically locate the V track R package on your machine Click on the desktop shortcut and the graphical user interface will open The six steps in the analysis process should be visible as tabs across the top of the V Track program window Each step must be run in sequence to create the necessary files for the subsequent analysis You are now ready to start using V Track 0 2 Exporting data from the VEMCO VUE software Open the vdb file in VUE Ensure that the export is Version 1 0 format by selecting Tools gt Options gt Export Display Offload Export Devices Other Comma Separated Value CSV Default format Custom Configuration Version 1 0 format Version 1 0 v Custom Tr Include VUE date amp time currently UTC Separate date amp ti
28. ssossesossssossssossssosssscesssossssossssossssossssossssoesseseoe 15 4 1 Qualifying horizontal MOVEIMENE sesciscsacssccesasweuassbiooesainenedpasacosasadiesanassbeabanedeeveiveadsa ENN ES 15 4 2 Horizontal movement OUTPUT FIIES cece eessccceesececeeececeeescceceeeceeeeneceseeenecessusecessegeceesenseeetes 16 Tio OU Y IA SONG OF CVC ee A E E EE 19 AA Sensor event OUD TNCs aea E 21 5 Generating temporal profiles of events ssssesessessssesessecssseosssecoesseoesssossssosssesesssosessoeses 23 5 1 Temporal profile output TeS screeners arne EA ES 24 6 Create animation of animal track to view in Google Earth sessesessssesessecessecsssessssesseses 26 6 1 Generating the Google Earth animation cccccccsssccccessececeseccceesscceseeseceseuseceseeeeceeseesecesseneees 26 6 2 Running the Google Earth animation ccccccsscccccsssccccessececceseccccesscceseesececeueceeeeeeceseeenecetseneees 27 CGUELSUMMAyY Of SCS Os soos co se tse teers cette cache cee aces ec crea es eee S E 28 V Track GUI Manual v1 02 0 1 Uploading the V Track GUI The V Track graphical user interface GUI runs in both Microsoft Windows and was created so that non specialists in R programming could still access the analysis tools within V Track Although the V Track GUI operates with a point and click interface the underlying functions are run within the R Programming environment therefore users of the GUI will still require both the R prog
Download Pdf Manuals
Related Search