EOSC473/573
Methods Cruise 2011 - Bamfield
|
(updated Mar 20 2011)
If you are interested, here's last
year's web
page.
Bamfield Contacts:
Education Coordinator: Anne Stewart 250-728-3301 local 226 astewart@bms.bc.ca
Boat Master: John Richards - 250-728-3301 local 224
jrich@bms.bc.ca
The Bamfield Marine
station also
has a
web site which is
worth looking at.
Plan:
Lora and David drive to BAMFIELD SUNDAY (BLUE VAN
)
Rest of class drive SUNDAY (Van fleet) , arriving
mid-afternoon.
- meet at loading bay entrance to EOS-MAIN
BUILDING at 7
am, leaving
to catch
the 8:30am ferry at
Horseshoe Bay.
- at arrival in Bamfield there will be an (1)
orientation tour by Bamfield staff, (2) course planning
meeting
(UBC staff), (3) Boat
safety orientation (UBC staff), (4) GPS exercise
(students).
MONDAY-WEDNESDAY - sampling exercises
Class split into 3 groups, and will rotate through the
different
exercises, given below. The general idea is that field
sampling
will
occur in the first part of the day (say, 8-lunch). The
afternoon
will
be spent doing lab analysis, with writeups done in the
evening. Around
8pm or so there will be a group meeting in which each group
will
do a short
presentation (10 minutes or so) to the others about
what happened that day,
passing on any useful hints!
Physics: Rich
- CTD analysis
and plotting of data
Chemistry: Lora/David
- Winkler O2, nutrients,
Chlorophyll
Biology:Desiree
- plankton
tows, Light
|
Monday morning
|
Tuesday morning |
Wednesday morning |
Group A
|
ALTA/phys - Rich
|
skiff1/elec1/nets - Desiree (David?) |
skiff2/elec2/chem -
Lora/David
|
Group B
|
skiff2/elec2/chem -
Lora
|
skiff2/elec2/phys-Rich |
ALTA/nets
- Desiree
|
Group C
|
skiff1/elec1/nets
-Desiree/David
|
ALTA/chem
- Lora (David?) |
skiff1/elec1/phys-Rich
|
Wednesday evening your research proposal will be finalized
and we
will have a coordination
meeting to set up the field plan for the next two days.
THURSDAY/FRIDAY - sampling TBD (for proposals)
return SATURDAY (if we leave exactly at 8am and
conditions
are good and you drive really fast
you can *just* make
the 10:30 ferry, but usually we leave at 8:30-9 and we can make
the 12:30, arriving between 11:30 and 12:15, if we don't stop
anywhere). All return to
UBC to help unload vehicles, and return rentals.
Class Details
Class size = 16
Undergrads = 8
Grads =8
Male = 5, Female = 11
Vegetarians = 2
Bamfield
computer
resources
 | There are a bunch of PCs available for general use in the
computer room. I install the Seabird CTD processing/display software,
and
they have Word and some other software (a grab-bag that varies from
year to year). No Matlab. Bamfield is on the net, but it is sometimes
very slooooowwwww to get to the outside world.
Bamfield now has WiFi most places. |
Some
Charts
I've made a few black-and-white versions of the relevant charts. On the
right is a close-up of Bamfield Inlet.Click on the image to see a
larger version. The Marine Station is at the tip of the spit in the
center, with Trevor channel (the main route out to the Pacific) at
upper left. Regions shallower than 10m are shaded.
Note
that this is a pretty crappy version of the chart - better to use the
postscript/pdf versions below.
This
is a map of the eastern part of Barkley Sound. Bamfield is
along
the eastern side of the inlet, near the mouth. You can see a
few
beachs nearby - in particular Pachena Bay directly to the south has a
very shallow and sandy beach.
The following are actual pdfs derived from the chart info
without
scanning, and are probably more useful:
If you want to use MATLAB to make a nice figure, this .mat file
contains a super-high resolution coastline on the NAD83 datum. This
code fragment shows how it can be used:
load BMS_coastline
plot(BC(:,1),BC(:,2)); % For a line coastline
or
clf; % For a filled coastline
load BMS_coastline
ii=find(isnan(BC(:,1)));
for k=1:length(ii)-1,
patch(BC(ii(k)+1:ii(k+1)-1,1),BC(ii(k)+1:ii(k+1)-1,2),[.8 .8
.8]);
end;
Student
Equipment List
Raingear (be prepared to be outside in bad weather)
Gloves, hat, sweaters (did I mention you should be prepared
to be
outside in bad weather?)
Steel toed rubber boots if you have them (otherwise we can
provide)
473 Notes (helpful in planning fieldwork)
Pens, Paper for assignments
Laptop or small personal computer if you wish (very helpful
though), otherwise there will be "lab" computers, see above)
A small waterproof notepad for use during
fieldwork.
A small backpack or something to hold your notebook while on
a
small boat.
SEASICKNESS PILLS - if you haven't worked on a small boat
before
it may be wise to invest in these....
Personal toilet gear (towel, toothbrush, etc.)
Pillows with pillowcases and mattress covers are provided,
but you should
BRING YOUR OWN blanket/sleeping bag etc.
A flashlight can be useful when walking around at night.
A small amount of money (you will be responsible
for your
own lunch while travelling there; meals are provided at Bamfield)
If you are interested in a particular kind of
sampling
check the equipment list above to see if it can be done. If not, see
one of the TAs or instructors and we will try to make sure you get
what you need!
Student
exercise
writeup details
During the first three days the theory is that students will learn
about various sampling techniques while taking some useful data. These
exercises will have to be written up. This writeup should be
2 or
3 pages in length (not including figures) for each exercise,
and
will include
1) A brief statement of the day's objectives and the means
by which they were carried out. E.g.
"Objective for Feb 17th were to acquire
CTD data
from a transect beginning at Bamfield and
moving up Grappler and
Bamfield Inlets. A
large seagoing ferry was used which unfortunately
ran aground repeatedly. A
heavy swell was
present so data from the first few meters is suspect".
2) A summary of your data collection. Include
locations
(lat/long), times, dates, weather info and sea
state, personnel and vessels involved
and relevant
comments for all stations. This should
be in the form of a table.
3) A Summary of the results of the days observations (do some
science!).
For example, describe the variation of temperature
with
depth and
location for CTD data, or the species observed in
net
tows. Plot your profiles, describe your
species...and then write a few paragraphs
explaining what
is there.
Exercises can be written up singly or in groups (Group
writeups
should be correspondingly longer and some note should be made of each
person's contribution).
Please hand in a HARD COPY which will be marked, and email in
a PDF which will be archived.
Research
proposal
guidelines
A research proposal will have to be submitted on Wednesday during the
field trip.
This should be NO MORE than 2 pages of text in
length, with an (optional) figure showing sampling locations.
In fact, we won't read more than 2 pages.
Research proposals can be individual, group, or joint
proposals (A
joint proposal is one written by an individual or group that is somehow
linked to a separate proposal written by other individuals or
groups). The contribution of each individual in a
multi-person
proposal should be clearly outlined.
Basically, a proposal should answer the questions "Who,
What, Why,
When, Where, and How".
Who: are the
personnel (later, who will
be doing what)?
What: is
the question you want to
address?
Why: do you
(or indeed would anyone)
care about this problem?
When: do
you want to take your data?
Also you should estimate how long it will take to take the required
data, e.g. in terms of available ship resources, time on
station,
lab time, etc. DO YOU HAVE ENOUGH DATA TO ANSWER THE QUESTION?
Where: do
you want to take data from
(a map of stations is helpful here), and where will the analysis be
done (relevant if you are doing things in a particular lab at UBC).
How: Unless
you are doing some
strange and
bizarre form of sampling, you can assume that the people reading your
proposal
know how data is collected. On the other hand, you may want to give
specific
non-standard details - for example, you may want CTD data only from the
first
10m, are cores to be sampled every 1cm or every 10cm? Similarly you
should
have some idea about how the data is going to be analyzed - what kind
of
tools (physical or mathematical) are you going to use?
Your proposal should have (a) a Title, (b) an Abstract, (c)
an
Introduction (with background and a statement of the problem), (d) a
Methods section (detailing the fieldwork requires and the analysis
plans), (e) Figures (probably only a map of station
locations).
Alternatively you can use the Who/What/Why/When/Where/How
headings
to organize things.
The abstract is a short (short!) summary of the proposal - a
few
sentences at most.
- Think about the audience. Typically only one (or maybe no)
members of a granting committee are experts in your field, although
they are trained scientists. A proposal full of dense jargon is usually
not a good idea.
Feel free to consult with any of the staff about
these
questions while writing your proposal!
Keep in mind that proposed work, even when funded, often
turns
into something quite different. Your final report shouldn't be too
different than the original proposal, but it doesn't have to be
exactly the same either. The first problems will arise on Wednesday
evening when we try to schedule all the fieldwork - you may not get
everything you want. Think about fallbacks - what is the MINIMUM amount
of data you need. What would be nice to have?
If you can use data from the exercises of previous days
(whether
it is yours or belongs to others) then do so if at all possible, but
you should also propose collecting more data of some kind.
Check your spelling and proofread - get someone else
to do this (and you can do the same for them)
Details of what the final report should look like will be
presented later - but in general it will be "like a journal paper" and
marked accordingly.
Conference
Guidelines
At the end of term we will have a "conference" at which everyone will
present a 10 minute talk on their results. Talks MUST be given by
individuals
- "group" presentations will NOT be allowed. This does not
mean
you cannot have "multiple-author" talks - it just means that for any
one talk a single person is responsible for presenting everything. If
you are working in a group and are unsure how to do this see Prof.
Pawlowicz. Generally speaking
any project can be broken up into smaller sub-projects. For example, if
two people A and B are working with a single dataset one person can
give a
self-contained talk on the methodology and its advantages/disadvantages
(e.g.
"Pitfalls in measuring estuarine depths", by A and B), and the other a
self-contained
talk that discusses implications of the results (e.g. "Estuarine depths
and
their relationship to the phase of the moon", by B and A).
This procedure is standard for conferences:
- A "call for papers" is issued.
2011
Bamfield Field School
Conference
Submissions relating to problems
arising from and related to the 2011 EOSC field
schools
at Bamfield Marine
Station are being solicited.
- Before the session deadline each participant submits the
title
and author(s) of their talk, as well as their preferred scheduling
(date in
this case).
Deadline
for abstract submission
is 23:59 PDT, Tuesday, March 15, 2011.
- Session organizers (instructors here) then organize the
abstracts
in some fashion that makes sense, and publish a schedule. You may get
your preferred scheduling, or you may not.
The
schedule will be emailed to
you by TUESDAY, March 22th, 2011.
- At the appointed time, you stand up and give your
presentation.
You will have 10 minutes and will be cut off if you go over. MAKE SURE
YOU
DON'T GO OVER YOUR ALLOTTED TIME - it is a shame to have to leave off
the
conclusions...
Here is what you need to know:
- for a 10 minute talk plan on talking for only 8
minutes,
leaving time for questions at the end. The only way to know how to do
this is....practise...practise...practise. If you are lying in bed
awake, go over your talk. If you are on the bus...practise your talk
(to yourself). Roughly speaking about 1 overhead or data slide per
minute is about right, but complicated slides can take more time to
explain.
- A talk should contain the following parts (and you will be
marked
accordingly).
- a title slide
- a statement of the problem and a discussion of the
rationale for
studying this problem
- a brief summary of the methods
- a discussion of the results
- some conclusions and (possibly) ideas about future work.
- Try to relate your work to that of others ("if you examine my data
slide in relation to this profile of temperature obtained by so-and-so,
you will see that..."). When writing the talk, try to anticipate
possible questions (i.e., think to yourself "If I say XXX then someone
is sure to wonder YYY so how do I prevent this").
- Figures:
- Should be legible (especially graph axes). Use pretty large
font
sizes - larger than you would use for a figure in a paper.
When
showing a figure, explain what the axes represent (nothing worse that
seeing a plot flash by in 10 seconds accompanied by "this figures shows
XXX"). Overheads and powerpoint presentations are both possible - but
you should show up early to make sure your powerpoint presentations
work; otherwise you are cutting into your 10 minutes....
- Should be easily understood - if you have to use legends,
make
them BIG. Colour is also good.
- Should illustrate the points being made. Don't be afraid to
redraw a figure to emphasize the points you want.
-Marking will be based on
- Timing of the talk (not too long or too short)
- Completeness (does it contain all the parts listed above)
- Quality of the figures (legibility, ease of understanding,
do
they illustrate the points being made?)
- Quality of the presentation (was the speaker articulate,
could we
hear them?)
-Notice that marking is NOT based on having final definitive results -
but you should have SOMETHING to talk about.
Final
Report Guidelines
The final report will be written up in the style of a journal article.
You may follow the style of any journal that you feel is an appropriate
place for your work. After you choose a journal get a copy of their
``information for contributors''. These instructions are usually in the
first issue of each volume, and outline such things as the arrangement
of sections, style to be used for references, and so forth.
Many
journals are now available in electronic form via the UBC library;
instructions are sometimes found on
the journal web pages as well. If you have problems after
reading
the
instructions come and see one of us. When you hand
in your
paper
you must also had in a copy of the "instructions''. Note that I will
permit
one deviation from the instructions. These usually request that the
figures
in a paper follow the text (a remnant of days when the paper would be
physically
split apart and text sent to a typesetter, figures to a photographer).
Feel
free to include your figures "in line".
In order to make sure that you aren't going wrong we require you to
hand in a rough draft some time before the final version is due (drafts
due March 31, 2009, final versions due April 21, 2009. The rough draft
need not be complete (in particular, if you have not finished
analyzing your data the Results and
Discussion
sections may be somewhat skimpy), but you should briefly
outline
what must still be done. The more you have in your draft the more
useful our feedback will be. The more useful our feedback the higher
quality your work, the higher quality the work the better the mark...
Both the draft and the final report should be handed in via Prof.
Pawlowicz's mailbox in the EOSC main office by 3pm on the due date.
A PDF of the final version should ALSO be emailed to Prof. Pawlowicz.
Marked drafts should be available within a couple of days.
Things to note:
- SI units should be used.
- The length of the paper is up to you. Be concise but
thorough.
Its unlikely you will need to have more than 8 figures at most.
- The paper must be typed and double spaced.
- The Title Page should have a
title, author's name
and student number, and a date.
- The Abstract should be concise and
complete in itself
without reference to the body. It should NOT repeat anything that is
stated in the title, since these two sections always appear together
and are consequently considered a unit. It should summarize the
observations and conclusions of the paper.
- The paper should have the following sections, each with its
own
section heading: Introduction, Methods, Results,
Discussion
or Conclusions, and References.
Sometimes these are
broken
up into other sections; check "your'' journal to see how people do
this.
Subheadings sometimes help.
- Avoid the use of "I'', e.g. use "It was found
that...''
rather than "I found...''
- Always include a map of the study site and the sampling
locations
used.
- The Introduction should include a
description of the
problem and the hypothesis you are testing. In other words, do not
assume your reader has seen the research proposal. This section should
also include a literature search and a brief review of your topic.
- If appropriate, include tables giving the raw data
collected
(this applies primarily to results of bottle, net, and bottom
samples). However, be aware that presenting tables is a mind-numbingly
dull way of showing
data, and it is unlikely your audience will spend more than a minimal
time
assimilating info in a table - MAKE A FIGURE.
- Figures should be "publication quality'' - avoid freehand
drawing. You should spend a lot of time on your figures - indeed, one
way of writing a paper is to first get the figures together, and then
describe them.
- In general, marks will be assigned partly on form, that is,
how
well can you adhere to a ``scientific'' style, and partly on
content,
that is, do the words make scientific sense.
- References must be referred to in the text!
Methods cruise '98 (Howe Sound)
Methods cruise '99 (Indian Arm)
Methods Cruise '00 (Bamfield - coring in Middle
Channel)
Methods Cruise '01 (Getting ready for the next station)
Methods Cruise '02 (Fun with sea cucumbers)
Methods Cruise
'03 (Waiting for the
messenger to close the bottle)
Methods Cruise '04
(Brady's Beach)

Methods Cruise '06 (Sampling Bamfield Inlet)

Methods Cruise '11 (The Year of Snow and Storms)