Smolt Monitoring 2009 Condition Sampling Standardization

Slides:



Advertisements
Similar presentations
Smolt Monitoring Program 1982-Present BPA project#
Advertisements

COLLECTIVE BARGAINING REPORTING Gateway User Guide Data Entry and Submission January 2014.
Observation Tools Overview and User Guide. Does the need to determine the impact a student's ADHD is having in the classroom or quantitatively describe.
Management Information Systems
Part II Objectives F Describe how policies and procedures are used F Identify different types of P & P F Describe the purpose and components of a Policy.
Provider Human Rights Coordinator Role Accessing HCSIS to Support Human Rights Committee Reviews September 11, 2013.
Certification of Market Values STEB PROGRAM Briefing Points 2011 Pennsylvania Department of the Auditor General Thomas E. Marks, CPA Deputy Auditor General.
Unit Introduction and Overview
Improving Data Entry of CD4 Counts March Welcome! The State Office of AIDS (OA) is continuing to work with providers to improve the quality of data.
Survival of Migrating Salmonid Smolts in the Snake and Lower Columbia Rivers, 2009 Technical Management TeamDecember 11, 2009 Lessons Learned 2009 Bill.
South Africa Data Warehouse for PEPFAR Presented by: Michael Ogawa Khulisa Management Services
« A Driver becomes Monitor » Philippe Van der Hofstadt B & C International, Belgium Conférence CEMO 14 Mars 2001.
Module 10: Monitoring ISA Server Overview Monitoring Overview Configuring Alerts Configuring Session Monitoring Configuring Logging Configuring.
Smolt Monitoring Program: Overview and Data Collection (SMP Traps) Brandon R. Chockley SMP Pre-Season Meeting Feb. 11,
NEW FOR 2009 Faster, Easier, Friendlier. Before you start Any student, staff, or faculty member can file an accident/incident report. Accident reporting.
Smolt Monitoring Program: Overview and Data Collection Brandon R. Chockley SMP Pre-Season Meeting February 20,
2015 G AS B UBBLE T RAUMA M ONITORING P ROTOCOL SMP Preseason Meeting – Bypass Facilities February 20, 2015 Brandon R. Chockley 1.
Changes to FPC32.net & GBT.net for 2015 Brandon R. Chockley SMP Pre-Season Meeting Feb. 20, 2015.
Pasewark & Pasewark Microsoft Office 2003: Introductory 1 INTRODUCTORY MICROSOFT OUTLOOK Lesson 3 – Working with Other Outlook Tools.
Ocean rivers SARs LGR-LGR SARs LGR-LGR Harvest Mouth of Columbia predicted returns Mouth of Columbia predicted returns Juvenile travel time and survival.
Writing Informal Reports
Monitoring Afghanistan, 2015 Food Security and Agriculture Working Group – 9 December 2015.
Web Analytics & Social Media Monitoring Assignment Briefing June and September 2013 Clive Whysall CAM Examiner.
The IEP: Progress Monitoring Process. Session Agenda Definition Rationale Prerequisites The Steps of Progress Monitoring 1.Data Collection –Unpack Existing.
Indiana Utility Regulatory Commission Electronic Filing System “EFS” Tutorial.
11/23/2016LCBE/gcm Department of Exceptional Children School Year Information Leslie County Schools.
Chapter 7 Module 27 Résumé.
Iterative Risk Management Workflow Tool
Helping Yourself in PD2 SPS Spotlight Series July 2015.
KARES Demonstration.
Software Application Overview
2016 Smolt Monitoring Program Juvenile Passage Data and
Payette MPG Sockeye Adult Tributary Juvenile Data Tributary Data
Northwest Fisheries Science Center Technical Management Team
MAINTAINING THE INVESTIGATOR’S SITE FILE
Session: 8 Disseminating Results
DATA INPUT AND OUTPUT.
Fundamentals of Information Systems, Sixth Edition
Metrics Replication Presentation for Maryland Staff September 26, 2002
Alliance Data Research and SIS Teams
How to Submit a New Human Ethics Clinical Application
FPAC Development of the Future SMP
Hatchery Subyearling Survival Lower Granite to McNary Dam 1998 to 2007 (preliminary results) Fish Passage Center.
USAJOBS – Application Manager
Age at ocean entry of Snake River Basin fall Chinook and its significance to adult returns prior to summer spill at LGR, LGS, and LMN dams.
MPG Spring-Summer Chinook
Incident Management: Recording New Incidents User Guide
FEASIBILITY STUDY Feasibility study is a means to check whether the proposed system is correct or not. The results of this study arte used to make decision.
Conducting the performance appraisal
Snake River MPG Fall Chinook Adult Tributary Juvenile Data Tributary
Conducting the performance appraisal
StaffTrac By Educational Vistas, Inc.
FACULTY and POs: Routing NEW Thesis-Proposal Approvals in Python
Northwest Fisheries Science Center Technical Management Team
NERC Alerts Training Responding to Alerts
2016 File Maker pro training for Summer program hiring
2017 TMT Year-end Review December 12, 2017 Brandon R. Chockley
Electronic Review Process
How to Create and Start a Test Session
Spring 2006 Gas Bubble Trauma Observed in Fish – Preliminary Analysis
MAINTAINING THE INVESTIGATOR’S STUDY FILE
TECHNICAL REPORT.
Standard Approach for Setting Up a Kaizen Event
International Scholar Dossier Training
Process Evaluation the implementation phase
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
On Site Management Meeting 7.
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
Part II Objectives Describe how policies and procedures are used
Periodic Accounting Review Periodic Revenue Reconciliation
Presentation transcript:

Smolt Monitoring 2009 Condition Sampling Standardization

Standardization Brief history of what has been done Where we are now What is left to be done Timeline of tasks to be completed

A brief review of steps to date FPAC requested in the fall of 2007 that condition data be reported real-time February meeting with SMP sites to determine data they were collecting (diverse suite of condition sampling data) FPC attempted to report condition data as gathered by sites (had issues with reporting results because some sites did not track individual fish (double counting injuries was possible) COE memo summarizing their findings about condition monitoring May 8, 2008 also showed no standardization FPC check in with FPAC on the condition indices to report (essentially FPC identified same set of categories as in COE memo) memo dated 5/12 discussed and approved at FPAC on 5/13 First step toward standardization was to have sites report data within condition and disease categories implemented on July 1.

Standardizing Fish Condition Data Between Sites Original Standardized LGR 34 19 LGS* 26 LMN* MCN 32 JDA 21 BON * LGS and LMN have changed the way they report condition and now report only the 19 Standardized Conditions

Standardized Fish Conditions Head Injuries Eye Injury Pop Eye Operculum Head Inj. Other Disease Fungus Columnaris BKD Parasite Deformity Disease Other Reported as Disease In Graphs Body Injuries Body Injury Fin Injury Reported as Physical Injury In Graphs Predation Fish Bird Lamprey Pred. Other Descaling Descaled (0-5%) Descaled (6-19%) Descaled (≥ 20%) Currently NOT Reported In Graphs

Examples: JDA and BON have 3 different parasites: Trematode Leech Copepod Parasite McNary Identifies five additional “diseases” that are not included in the standardized format: Fin Rot Digenia Unknown Infection Emaciated Moribund Disease/Parasite Other Lower Granite identifies a predator that is not included in the standardized format: Human Predation Predator Other McNary has seven different “types” of descaling that they identify, Standardized Format has 3: Partial Descaling (5-19%) Descaled (20-50%) Descaled from Bird (20-50%) Descaled from Fish (20-50%) Descaled (>50%) Descaled from Bird (>50%) Descaled from Fish (>50%) Descaled (0-5%) Descaled (6-19%) Descaled (≥ 20%)

Future steps to standardize condition sampling Get input in Defining the uses for the data (this determines what should be collected)--ongoing Determine reports to be generated (data summaries) (FPAC and COE) Determine data to be collected (finalize) check in with FPAC and COE Standardization of indices (carefully define metrics to be gathered so that they are as meaningful as possible) in context of questions being answered – final product protocol document Training SMP personnel to report data in agreed upon categories of injury and disease

Other steps to complete Programming Incorporate condition data entry into new data entry program Include outputs for COE, FPAC and FPC database/web Determine sample size requirements Including addressing whether to examine all fish for descaling or subset Determine sampling frequency necessary to provide reliable condition information

What is the purpose of condition monitoring What is the purpose of condition monitoring? What management decisions will be based upon these data? Examples Identify changes in fish condition (rapid increases?) to find bypass problems at dams Provide triggers for management actions (e.g. 5% injury = rake trash racks or 80% disease stop collecting fish for transport...) Provide historical record for year to year comparisons (descaling events per site/yr) Characterize overall population health

Salmon Managers Objective of condition sampling is to provide information about the impacts of bypass passage on salmonids

Timeline for completing standardization for 2009 season

PC with FPC32 and Touchscreen Outputs SITE WET LAB PC with FPC32 and Touchscreen Outputs Fish Condition Sub-batch Batch Fish Count Files/Reports include: Standardized handlog faxed to FPC Batch data file in .xls format emailed to FPC Fish condition sub-batch data in .xls format; NOTE 1 and 2 could be the same file emailed to FPC At FPC, Daily SMP Summary Batch Report At FPC, Daily Mark Recap Report At FPC, Daily Incidental Catch Report At Site, Daily COE Report(s) – needs to be determined At FPC and Site, Daily Sub-Batch Fish Condition Report 1. Technicians count fish using tallies on tally wacker or standardized handlog 2. Main technician completes standardized handlog with batch data 3. Main technician enters batch data on touch screen or uses office computer --Fish condition data is entered using “Fish Condition buttons” on the touchscreen FPC Outputs FPC Office uses FPC32PST application to upload data to FPC Database Server .xls data files (1 and 2) output saved to thumb drive – can be used on this computer or office computer PC with FPC32 If batch data were not entered in the site wet lab, batch data are entered into FPC32 from the standardized handlog. Data are saved and output in an xls format to email to FPC office. XLS data can be used by SITE for their own functions. Daily reports are generated and also saved in XLS format. SITE OFFICE