Onboard protocol Sample Clauses

Onboard protocol. The sink rate of baited hooks was recorded by attaching CEFAS G5 Time Depth Recorders (TDRs) to the third of five branch lines at a position 30 cm above the hook (Figure 2). On each set TDRs were deployed on randomly selected sections of the main line (the start, middle or end). TDRs were configured to register depth (pressure) every second to generate the sink rate for each treatment. Figure 2: Basic configuration of Brazilian pelagic longline gear, showing the position where TDRs were attached in relation to hooks between buoys. The number of seabirds present was estimated immediately prior to the set and each subsequent hour within a 250 m hemisphere centred at the vessel xxxxx. During the set seabird attacks on baited hooks were recorded as a function of distance aft (0-50 m, 50-75 m, 75-100 m, and > 100m) in ten minute periods while light persisted. Seabird attacks were defined as any attempt by a bird to take bait, including surface attacks and dives to access sinking baited hooks. Tori line aerial extent was recorded for each ten minute period using white streamers as distance markers placed every 10 m along the length of the tori line. Tori line entanglements were recorded when these occurred. Target and non-target species were recorded during the haul to species level.
AutoNDA by SimpleDocs
Onboard protocol. The sink rate of baited hooks was recorded by attaching CEFAS G5 TDRs at three positions (1st, 2nd and 3rd of five secondary lines) at a position 30 cm above the hook (Figure 2). On each set TDRs were deployed on randomly selected sections of the main line (the start, middle or end). TDRs were configured to register depth (pressure) every second to generate sink rate profiles. During tori line treatments, aerial extent was estimated for each observation period using the distance between streamers. Detailed information was recorded each time the tori line became entangled. Observations on seabird attack rate during the set were recorded using PAP protocols3. Where seabird mortality occurred, the section, buoy and hook position were recorded to enable the mortality event to be related to the setting operation.
Onboard protocol. The sink rate of baited hooks was recorded by attaching CEFAS G5 Time Depth Recorders (TDRs) to the middle (third) branch line at a position 30 cm above the hook. TDRs were deployed on randomly selected sections of the main line (the start, middle or end). TDRs were configured to register depth (pressure) every second to generate the sink rate for each treatment. Setting observations Experimental branch lines were stored and set from two bins; one containing Treatment 1 (60g SLs) and the other Treatment 2 (150g SLs). Sample units were colour-coded red and green to aid recording on retrieval (Figure 8a). The line was set from a central position at the xxxxx of the vessel. Treatment hook bins were situated on the starboard (Treatment 1) and port (Treatment 2) sides. For each Treatment two crew members were included in the setting operation. The first removed the hook and branch line from the bin, attached a light stick and passed the assembly to the second crew member who baited and deployed the hook. The weighted swivel was tossed into the propeller wash, which trailed until the monofilament branch line had completely unravelled; the snap was then attached to the mainline and the hook deployed into the water between the main line and the edge of the wash. This process was repeated for Treatment 2. A fifth crewman set floats from the port quarter of the aft deck. Hauling observations Hauling commenced within an hour of first light. All experimental branch lines were observed and the following details were recorded: Operational data recorded included: Treatment, time, sample unit number, sub unit number and hook number (within sub unit). For a sub-sample of 160 branch lines, the distance of SLs from their original position was measured to determine slippage toward the hook. Catch data recorded included: Species, size and condition (i.e. partially predated). For target species (i.e. tunas and swordfish) a size class was recorded. Sharks were assigned to one of three size classes: small (<1 m), Medium (1-2 m) and large (>2 m). All bite-off events were classified into one of five categories 0-4 (0- bite off occurs under water and weight stays under water; 1- weight lands on water; 2- weight hits the bottom half of the boat; 3- weight hits the upper half of the boat; 4- weight flies above the boat). During the haul all SLs were checked and positioned at a standard distance of 3.5 m (adjacent to the un-weighted swivel) from the hook.
Onboard protocol. Seabird abundance was estimated for all experiments by conducting approximately 10- minute observations within a semi-circle extending 200 m aft of the xxxxx of the vessel. The three treatments were deployed sequentially during each experimental trawl. The order in which the three treatments were deployed on each trawl was randomly allocated. Experimental treatments began once the net was on the seabed, each treatment lasting 15 minutes. Data collected during trawls that finished before all three treatments could be deployed were excluded from data analysis. Observations on seabird interactions with trawl warp cables were carried out in 45 minute periods (3x 15 minutes). A single warp cable was chosen for observations based on the side of the vessel where most offal was discharged. Interaction protocols were adapted from Xxxxxxxx and Xxxxxxxxx (2001). This included recording light and heavy contacts between birds on the wing and on the water, and the warp cable. Offal discard was recorded for each new observation period.

Related to Onboard protocol

  • COVID-19 Protocols Contractor will abide by all applicable COVID-19 protocols set forth in the District’s Reopening and COVID-19 Mitigation Plan and the safety guidelines for COVID-19 prevention established by the California Department of Public Health and the Ventura County Department of Public Health.

  • Protocol No action to coerce or censor or penalize any negotiation participant shall be made or implied by any other member as a result of participation in the negotiation process.

  • Training Materials Training Materials will be provided for each student. Training Materials may be used only for either (i) the individual student’s reference during Boeing provided training and for review thereafter or (ii) Customer’s provision of training to individuals directly employed by the Customer.

  • Software Components At any time during the contract period of performance, the Government may require the Contractor to remedy any failure of the software to comply with the requirements of this contract. Support shall consist of correction of errors, provision of modifications, improvements, and other products the original manufacturer makes available to the Government without charge. The Government shall also be provided full documentation of changes and/or modifications to the software provided to meet the Government's requirements.

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.

  • Software Updates XXXXX agrees to keep current with software licensed from Skyward and will install new versions on a timeline approved by XXXXX governance. This timeline will be communicated by NWRDC to the Districts. School District Workstations Configuration requirements for devices and their software that school district personnel use to access WSIPC’s software modules can be found on our website: xxxxx://xxx.xxxxx.xxx/technology‐team/. State Reports XXXXX will provide, at no additional fee, all data reports required by the state that impact 50% or more of the school districts in the state. WSIPC and NWRDC will work with state agencies to gather requirements on the required data. WSIPC will inform NWRDC staff of any mandated changes to state reports and NWRDC will communicate the information to the District. Appendix B NWRDC FTE Fees Fiscal Only NWRDC Software Support Services XXXXX Software Licensing Total FTE Fee $13.63 $20.34 $33.97 $15.56 $13.08 $28.64 $24.52 $20.34 $44.86 Student Only Full Service

  • Protocols Each party hereby agrees that the inclusion of additional protocols may be required to make this Agreement specific. All such protocols shall be negotiated, determined and agreed upon by both parties hereto.

Time is Money Join Law Insider Premium to draft better contracts faster.