<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>ss3 projection</title>
  <link rel="self" href="https://vlab.noaa.gov/c/message_boards/find_thread?p_l_id=8790705&amp;threadId=7647389" />
  <subtitle>ss3 projection</subtitle>
  <id>https://vlab.noaa.gov/c/message_boards/find_thread?p_l_id=8790705&amp;threadId=7647389</id>
  <updated>2026-07-12T20:39:44Z</updated>
  <dc:date>2026-07-12T20:39:44Z</dc:date>
  <entry>
    <title>ss3 projection</title>
    <link rel="alternate" href="https://vlab.noaa.gov/c/message_boards/find_message?p_l_id=8790705&amp;messageId=7647388" />
    <author>
      <name>Dan Fu</name>
    </author>
    <id>https://vlab.noaa.gov/c/message_boards/find_message?p_l_id=8790705&amp;messageId=7647388</id>
    <updated>2020-04-10T14:41:24Z</updated>
    <published>2019-09-20T12:41:40Z</published>
    <summary type="html">&lt;p&gt;Hi, I have come across an issue when doing standard ss3 projections&amp;nbsp; where&amp;nbsp;the stock 'crashes' in some future years with certain catch senarios&amp;nbsp;( biomass/F values is too big or too small). I I don't think this is because the the catch has been set too high, as the&amp;nbsp;projection&amp;nbsp;with a much higher catch senario works fine. This appears to be an numeric issue as &amp;nbsp;simply rounding the catch numbers to fewer decimal places can fix the problem in some instances.&amp;nbsp; I wonder if someone has come across similar issues before? Thanks. Dan&amp;nbsp;&amp;nbsp;&lt;/p&gt;</summary>
    <dc:creator>Dan Fu</dc:creator>
    <dc:date>2019-09-20T12:41:40Z</dc:date>
  </entry>
</feed>

