Annotation Database Cruise Status: Difference between revisions

From MediaWiki
Jump to navigation Jump to search
No edit summary
 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
Importing cruises into the database is a multi-step process involving multiple people and many pieces of data. This page keeps track of the cruises and their status with respect to the database and the import process.
Importing cruises into the database is a multi-step process involving multiple people and many pieces of data. This page keeps track of the cruises and their status with respect to the database and the import process.
= Cruise Import Status =


{| class="wikitable"
{| class="wikitable"
|+ Import Status of Cruises
|+ Import Status of Cruises
|-
|-
! Cruise !! Status !! Metadata !! Crew !! Dives !! Transects !! Navigation !! Telemetry !! Water Properties !! Status !! Comments !! Measurements !! Annotations !! Annotation Software
! Cruise !! Status !! Metadata !! Crew !! Dives !! Transects !! Navigation !! Telemetry !! Water Properties !! Status !! Comments !! Measurements !! Annotations !! Annotation Software !! [[#Dive Time Synchronization|Dive Time Sync]]
|-
| PAC2000-031 || Imported || Yes || Yes || Yes || No || Yes || Depth || No || No || No || No || Observations, Habitat || VideoMiner || 1
|-
| PAC2008-011 || Imported || Yes || Yes || Yes || No || Yes || Depth || No || No || No || No || No || || 1
|-
| PAC2008-024 - 1 || Imported || Yes || Yes || Yes || No || Yes || Depth, Pitch || No || Yes || No || No || No ||  || 1
|-
| PAC2008-024 - 2 || Imported || Yes || Yes || Yes || No || Yes || Depth, Pitch || No || Yes || No || No || No ||  || 1
|-
| PAC2008-024 - 3 || Imported || Yes || Yes || Yes || No || No || No || No || No || No || No || No || || 1
|-
|-
| PAC2000-031 || Imported || Yes || Yes || Yes || No || Yes || Depth || No || No || No || No || Observations, Habitat || VideoMiner
| PAC2008-024 - 4 || Imported || Yes || Yes || Yes || Yes || Yes || Depth, Pitch || No || Yes || No || No || Observations, Habitat || Custom Access || 2
|-
|-
| PAC2008-011 || Imported || Yes || Yes || Yes || No || Yes || Depth || No || No || No || No || No ||  
| PAC2008-024 - 5 || Imported || Yes || Yes || Yes || No || Yes || Depth, Pitch || No || Yes || No || No || Observations, Habitat || Custom Access || 1
|-
|-
| PAC2008-024 || Imported || Yes || Yes || Yes || Yes || Yes || Sound Velocity || No || No || Yes || No || Observations, Habitat || Custom Access
| PAC2008-044 || Imported || Yes || Yes || Yes || No || Yes || Depth || No || No || No || No || No || || 1
|-
|-
| PAC2008-057 || Imported || Yes || Yes || Yes || No || Yes || Depth || No || No || No || No || No ||  
| PAC2008-057 || Imported || Yes || Yes || Yes || No || Yes || Depth || No || No || No || No || No || || 1
|-
|-
| PAC2009-013 || Imported || Yes || Yes || Yes || Yes || Yes || Depth || No || Yes || No || No || Observations || Informal
| PAC2009-013 || Imported || Yes || Yes || Yes || Yes || Yes || Depth || No || Yes || No || No || Observations || Informal || 3
|-
|-
| PAC2009-024  
| PAC2009-024 || Imported || Yes || Yes || Yes || No || Yes || Depth, Pitch || No || No || Yes || No || No || || 1
|-
|-
| PAC2009-044  
| PAC2009-044 - 1 || Imported || Yes || Yes || Yes || No || Yes || Depth || No || Yes || Yes || No || Observations, Habitat || VideoMiner || 1
|-
| PAC2009-044 - 2
|-
|-
| PAC2009-062
| PAC2009-062
Line 96: Line 110:
| PAC2021-054
| PAC2021-054
|-
|-
| PAC2022-005
| PAC2022-005 || Partially Imported || Yes || Yes || Yes || Yes || Ship, ROV || Depth || Yes || Yes || Yes || Orientation || Pending || Biigle
|-
|-
| PAC2021-036
| PAC2021-036
|}
|}
== Dive Time Synchronization ==
The ''Dive Time Sync'' column tracks an issue with dive, transect and telemetry times: the dive time encompasses the time from launch to recovery, so that all telemetry times are contained within those bounds. Transect times are the boundaries of segments when observations can be made and exist mainly for accounting purposes. For research purposes, the transect boundary is meaningful because population density measurements (etc.) are affected by the proximity of the beginning or end of a transect to the first and last observation collected. That is, the transect time determines the size of the region within which organisms are counted -- the larger the region, the lower the density.
Dives were originally not imported with this issue in mind, and dive logs for some cruises are inadequate. For cruises with no, or inadequate, transect information, a transect extends to the ends of the parent dive. For dives with telemetry that extends past the beginning and end times of the dive, the dive time is extended to contain them. Sometimes the launch time of the vehicle and the start of the official "dive" are recorded separately. The launch time will be used. For dives that have been extended, but don't have transects, the transect will cover the originally-recorded dive time. For transects that are recorded, their original times will be maintained.
The ''Dive Time Sync'' column tracks the status of this correction. The possible values are:
# No transects. Transect times are set to the recorded dive times, dive times may be extended to encompass telemetry.
# Has defined transects with start and end times.
# Has ''some'' defined transects; others are set to dive times.


== Notes ==
== Notes ==
Line 106: Line 133:


One of the Access files cannot be opened with current versions of Access. Each of the 5 legs have different protocols.
One of the Access files cannot be opened with current versions of Access. Each of the 5 legs have different protocols.
Leg 4 has defined transect lines with start and end times. The others have no defined transects.
=== PAC2009-044 - 2 ===
Imported but not approved. Need information from Cherisse.


=== PAC2018-007 ===
=== PAC2018-007 ===


The Access database is based on the standard VideoMiner structure with several pivoted columns containing an abundance level for a single species. These have been pivoted back into the main table structure (as extra rows) and imported in the standard way. The 'NA' value is also converted into empty cells.
The Access database is based on the standard VideoMiner structure with several pivoted columns containing an abundance level for a single species. These have been pivoted back into the main table structure (as extra rows) and imported in the standard way. The 'NA' value is also converted into empty cells.
There are multiple habitat observations within one second because those annotations exist in the source data. The same goes for species observation.
=== PAC2022-005 ===
Awaiting Biigle annottions.

Latest revision as of 00:09, 8 March 2024

Importing cruises into the database is a multi-step process involving multiple people and many pieces of data. This page keeps track of the cruises and their status with respect to the database and the import process.

Cruise Import Status

Import Status of Cruises
Cruise Status Metadata Crew Dives Transects Navigation Telemetry Water Properties Status Comments Measurements Annotations Annotation Software Dive Time Sync
PAC2000-031 Imported Yes Yes Yes No Yes Depth No No No No Observations, Habitat VideoMiner 1
PAC2008-011 Imported Yes Yes Yes No Yes Depth No No No No No 1
PAC2008-024 - 1 Imported Yes Yes Yes No Yes Depth, Pitch No Yes No No No 1
PAC2008-024 - 2 Imported Yes Yes Yes No Yes Depth, Pitch No Yes No No No 1
PAC2008-024 - 3 Imported Yes Yes Yes No No No No No No No No 1
PAC2008-024 - 4 Imported Yes Yes Yes Yes Yes Depth, Pitch No Yes No No Observations, Habitat Custom Access 2
PAC2008-024 - 5 Imported Yes Yes Yes No Yes Depth, Pitch No Yes No No Observations, Habitat Custom Access 1
PAC2008-044 Imported Yes Yes Yes No Yes Depth No No No No No 1
PAC2008-057 Imported Yes Yes Yes No Yes Depth No No No No No 1
PAC2009-013 Imported Yes Yes Yes Yes Yes Depth No Yes No No Observations Informal 3
PAC2009-024 Imported Yes Yes Yes No Yes Depth, Pitch No No Yes No No 1
PAC2009-044 - 1 Imported Yes Yes Yes No Yes Depth No Yes Yes No Observations, Habitat VideoMiner 1
PAC2009-044 - 2
PAC2009-062
PAC2010-009
PAC2010-009
PAC2010-043
PAC2010-009
PAC2010-074
PAC2011-006
PAC2011-062
PAC2011-072
PAC2011-073
PAC2012-008
PAC2012-014
PAC2012-035
PAC2012-043
PAC2012-068
PAC2013-011
PAC2013-062(063)
PAC2013-068
PAC2013-070
PAC2014-037
PAC2014-059
PAC2015-013
PAC2015-048
PAC2015-051
PAC2015-053
PAC2016-026
PAC2016-063
PAC2017-021
PAC2017-030
PAC2017-036
PAC2017-094
PAC2018-007 Imported Yes Yes Yes No Yes Depth No Yes Yes No Observations, Habitat VideoMiner
PAC2018-075 Imported Yes Yes Yes Yes Yes Depth No Yes Yes FOV, Laser Distance Observations, Habitat Custom Access
PAC2019-014
PAC2019-015 Imported Yes Yes Yes Yes Yes Depth, Heading, Altitude, Zoom No Yes No No Observations, Habitat Biigle
PAC2021-035 Imported Yes Yes Yes Yes Yes Heading, Altitude, Zoom Temperature Yes Yes No Observations, Habitat Biigle
PAC2021-036
PAC2021-054
PAC2022-005 Partially Imported Yes Yes Yes Yes Ship, ROV Depth Yes Yes Yes Orientation Pending Biigle
PAC2021-036


Dive Time Synchronization

The Dive Time Sync column tracks an issue with dive, transect and telemetry times: the dive time encompasses the time from launch to recovery, so that all telemetry times are contained within those bounds. Transect times are the boundaries of segments when observations can be made and exist mainly for accounting purposes. For research purposes, the transect boundary is meaningful because population density measurements (etc.) are affected by the proximity of the beginning or end of a transect to the first and last observation collected. That is, the transect time determines the size of the region within which organisms are counted -- the larger the region, the lower the density.

Dives were originally not imported with this issue in mind, and dive logs for some cruises are inadequate. For cruises with no, or inadequate, transect information, a transect extends to the ends of the parent dive. For dives with telemetry that extends past the beginning and end times of the dive, the dive time is extended to contain them. Sometimes the launch time of the vehicle and the start of the official "dive" are recorded separately. The launch time will be used. For dives that have been extended, but don't have transects, the transect will cover the originally-recorded dive time. For transects that are recorded, their original times will be maintained.

The Dive Time Sync column tracks the status of this correction. The possible values are:

  1. No transects. Transect times are set to the recorded dive times, dive times may be extended to encompass telemetry.
  2. Has defined transects with start and end times.
  3. Has some defined transects; others are set to dive times.

Notes

PAC2008-024

One of the Access files cannot be opened with current versions of Access. Each of the 5 legs have different protocols.

Leg 4 has defined transect lines with start and end times. The others have no defined transects.

PAC2009-044 - 2

Imported but not approved. Need information from Cherisse.

PAC2018-007

The Access database is based on the standard VideoMiner structure with several pivoted columns containing an abundance level for a single species. These have been pivoted back into the main table structure (as extra rows) and imported in the standard way. The 'NA' value is also converted into empty cells.

There are multiple habitat observations within one second because those annotations exist in the source data. The same goes for species observation.

PAC2022-005

Awaiting Biigle annottions.