<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">60% of BMSY<br>
      <br>
      On 10/08/12 15:31, Hintzen, Niels wrote:<br>
    </div>
    <blockquote
      cite="mid:8FE8A24E425793428F3C772FA61961A51FBFE7C8@SCOMP0936.wurnet.nl"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Verdana;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
        {font-family:"WenQuanYi Micro Hei";
        panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:"Lohit Hindi";
        panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        text-align:left;
        line-height:normal;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        color:black;
        mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        margin-bottom:5.95pt;
        margin-left:0in;
        text-align:justify;
        mso-line-height-alt:5.1pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:#00000A;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        text-align:left;
        line-height:normal;
        font-size:10.0pt;
        font-family:"Courier New";
        color:black;}
p.western, li.western, div.western
        {mso-style-name:western;
        mso-margin-top-alt:auto;
        margin-right:0in;
        margin-bottom:5.95pt;
        margin-left:0in;
        text-align:justify;
        mso-line-height-alt:5.1pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:#00000A;}
p.cjk, li.cjk, div.cjk
        {mso-style-name:cjk;
        mso-margin-top-alt:auto;
        margin-right:0in;
        margin-bottom:5.95pt;
        margin-left:0in;
        text-align:justify;
        mso-line-height-alt:5.1pt;
        font-size:12.0pt;
        font-family:"WenQuanYi Micro Hei","serif";
        color:#00000A;}
p.ctl, li.ctl, div.ctl
        {mso-style-name:ctl;
        mso-margin-top-alt:auto;
        margin-right:0in;
        margin-bottom:5.95pt;
        margin-left:0in;
        text-align:justify;
        mso-line-height-alt:5.1pt;
        font-size:12.0pt;
        font-family:"Lohit Hindi","serif";
        color:#00000A;}
span.EmailStyle21
        {mso-style-type:personal;
        font-family:"Verdana","sans-serif";
        color:windowtext;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:"Consolas","serif";
        color:black;
        mso-fareast-language:EN-US;}
span.EmailStyle24
        {mso-style-type:personal-reply;
        font-family:"Verdana","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D">Hi
            Laurie,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D">Thanks
            for this, and I agree that F = Fmsy if B > Bmsy where
            Bmsy can be Btrigger. However, based on other criteria than
            biology alone, you could choose for different Fmsy values
            (upper or lower bound for example) which automatically will
            result in different Btrigger values. The problem is that I
            do NOT want to derive a Btrigger through MSE as you suggest,
            we’ve done that before, it works well, but if you are kind
            of in the dark where Btrigger should be, you are up for lots
            of scenarios, the one thing I try to prevent here. Hence,
            I’m looking for a smart way to get an estimate of Btrigger
            which is related to Fmsy without doing lots of scenario
            testing.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D">Any
            other suggestions?<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D">Cheers,
            Niels<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0in 0in 0in">
            <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;mso-fareast-language:EN-GB"
                  lang="EN-US">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;mso-fareast-language:EN-GB"
                lang="EN-US">
                <a class="moz-txt-link-abbreviated" href="mailto:flr-list-bounces@lists.r-forge.r-project.org">flr-list-bounces@lists.r-forge.r-project.org</a>
                [<a class="moz-txt-link-freetext" href="mailto:flr-list-bounces@lists.r-forge.r-project.org">mailto:flr-list-bounces@lists.r-forge.r-project.org</a>]
                <b>On Behalf Of </b>Laurie<br>
                <b>Sent:</b> vrijdag, augustus 10, 2012 15:17<br>
                <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:flr-list@flr-project.org">flr-list@flr-project.org</a><br>
                <b>Subject:</b> Re: [FLR-list] Estimating Btrigger
                suggestions<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <div>
          <p class="MsoNormal">Btrigger is a level of biomass that if
            the stock falls triggers management action to rebuild the
            stock as part of a HCR.<br>
            <br>
            Choosing a value that is too small will result in higher
            risk of stock collapse and loss yield since biomass will
            fall below BMSY, Choosing a value that is too high will
            result in loss yield due to fishing effort being reduced
            unnecessarily. Blim needs to balance these objectives. The
            best way to do this would be to conduct an MSE with
            appropriate uncertainty, i.e. try a variety of values for
            Btrigger and choose the one that performs best. If you have
            an MSY harvest control rule there is no need for an Ftrigger
            as you would be setting F to FMSY if B>BMSY and F to that
            given by the line joining (FMSY, Btrigger) to (Flim,blim).<br>
            <br>
            Laurie<br>
             <br>
            <br>
              <br>
            <br>
            On 10/08/12 14:32, Hintzen, Niels wrote:<o:p></o:p></p>
        </div>
        <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
          <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif"">Dear
              all,</span><o:p></o:p></p>
          <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""> </span><o:p></o:p></p>
          <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif"">Sometime
              soon, I’m faced with another Management Plan Evaluation
              for North Sea herring. Obviously we’ll be using FLR.
              However, I’d like to gain a bit more insight into good
              practices to ‘estimate’ a specific biomass reference
              point, so it is a bit off-topic but the expertise in this
              group is so high I could not resist sending this question!</span><o:p></o:p></p>
          <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""> </span><o:p></o:p></p>
          <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif"">The
              current HCR prescribes an Fbar of 0.1 below Blim
              (determined on a biological basis) and increases linearly
              with SSB up to a Btrigger biomass point (determined in
              2008 based on a performance basis, i.e. scenario testing,
              which scenario performed best). Above this Btrigger, the
              HCR prescribes an Fbar of 0.25 (considered Fmsy).</span><o:p></o:p></p>
          <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""> </span><o:p></o:p></p>
          <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif"">Within
              the new evaluation, Blim, Btrigger and Fmsy will be a
              point of discussion (because the stock assessment changed
              considerably). I have some ideas on how to estimate Blim
              and Fmsy, but with Btrigger I’m a bit in the dark. What I
              can think of so far is to run stochastic equilibrium
              simulation assuming constant Fs (over a range) and, as a
              first guess, taking Btrigger as the median equilibrium
              SSB. Does this make sense, and if not, what would you
              suggest to do. I need some sort of approach to link
              potential Ftrigger points to Btrigger points because else
              I will be running far too many scenarios to be able to
              analyse and discuss later on.</span><o:p></o:p></p>
          <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""> </span><o:p></o:p></p>
          <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif"">Many
              thanks in advance for your suggestions.</span><o:p></o:p></p>
          <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""> </span><o:p></o:p></p>
          <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif"">Kind
              regards,</span><o:p></o:p></p>
          <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""> </span><o:p></o:p></p>
          <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif"">Niels</span><o:p></o:p></p>
          <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""> </span><o:p></o:p></p>
          <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif""> </span><o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:"Times New
              Roman","serif";mso-fareast-language:EN-GB"><br>
              <br>
              <br>
              <o:p></o:p></span></p>
          <pre>_______________________________________________<o:p></o:p></pre>
          <pre>flr-list mailing list<o:p></o:p></pre>
          <pre><a moz-do-not-send="true" href="mailto:flr-list@flr-project.org">flr-list@flr-project.org</a><o:p></o:p></pre>
          <pre><a moz-do-not-send="true" href="https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/flr-list">https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/flr-list</a><o:p></o:p></pre>
        </blockquote>
        <p class="MsoNormal"><span
            style="font-size:12.0pt;font-family:"Times New
            Roman","serif";mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
flr-list mailing list
<a class="moz-txt-link-abbreviated" href="mailto:flr-list@flr-project.org">flr-list@flr-project.org</a>
<a class="moz-txt-link-freetext" href="https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/flr-list">https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/flr-list</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>