CI Deployment Plan

The Cascadia Initiative Deployment Plan was developed by an NSF-supported community workshop held in Portland, Oregon in October, 2010. The workshop produced a series of recommendations to maximize the scientific return of the CI. The full workshop report can be found at CI Workshop Reports.

This page provides links to maps and data files for the Deployment Plan and outlines the procedure that CIET will follow when making significant changes to the deployment plan.

Data Files from 2010 Portland Meeting

Links to maps and stations locations that resulted from the Portland workshop are provided below. See the following pages for each year: 

Matlab files for each year:

  • Year 1
  • Year 2
  • Year 3
  • Year 4

Excel file with instrument depths:

    1.    Station locations are from Year 1
    2.    Depths are extracted from Sandwell’s latest 1-minute topography compilation: “topo_13.1.img”

Procedure for Modifying the Deployment Plan

The preliminary deployment plan developed at the 2010 Portland meeting will require modifications in order to take into account, for example, instrument availability, seafloor bathymetry and possible geo/bio-hazards (e.g., trawling, turbidity currents, etc.).

CIET will use the following procedure for making changes to the workshop-defined deployment plan:

  1. When circumstances, eg instrument availability, demand a change to the CI deployment plan, the CIET develops a new plan that remains as close to the original community plan as possible but accommodates the new circumstances.
  2. This plan is made available to community members with specific knowledge or interest relevant to the change for comment and suggestions.
  3. The CIET revises the plan accordingly and presents it to AASC (Amphibious Array Steering Committee).
  4. The AASC reviews the plan, makes suggestions/changes, and approves the modified plan.
  5. The modified plan is posted on the CIET website, at which point community wide input is welcome, within a time frame that is practical for reconsidering the design.

This procedure was discussed on by AASC on May 26, 2011 and approved.

Above are links to two documents on Cascadia trawling from Andrew Barclay. The first (Cascadia_OBS_and_trawling.pdf) is Andrew’s detailed summary of the issues and possible solutions based on his discussions last October with Scott McMullen of the Oregon Fishermen’s Cable Commission (OFCC) and Walt Waldorf (OSU). The second (trawl_report_2010.pdf) is a formal NOAA fisheries summary of 2010 trawling in the area.

I plan to contact Scott McMullen to establish a dialogue on the experiment and hopefully find out where known trawling hangs are in the area of interest for Cruise 1 (mostly the FA). Leaders of Cruise 2 & 3 should probably do likewise for their sites, or perhaps we should discuss a more coordinated approach? If so, Anne is the logical person to do the contacting (but I believe she’s out of the country for another week or two).

Also got the following notes from Andrew on these files:

“Also, for a very rough idea of trawling off Gray’s Harbor, Figure 1a of the second document indicates heaviest fishing along the 100 m contour. The boxes are 10km, and assuming tows are along-slope, then 10 km both sides of the 100 m contour have 29-265 tows, or one every 30-300 m. Assuming the trawl nets are 30 m across, then there is a 10-100% chance that the entire seafloor in the 20-km swath is trawled once per year. Better data (locations where nets are set and recovered) are available from the Pacfin database; I asked for access last fall but never got a reply and didn’t follow up.”