<?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.30 forecast</title>
  <link rel="self" href="https://vlab.noaa.gov/c/message_boards/find_thread?p_l_id=8790705&amp;threadId=10428197" />
  <subtitle>ss3.30 forecast</subtitle>
  <id>https://vlab.noaa.gov/c/message_boards/find_thread?p_l_id=8790705&amp;threadId=10428197</id>
  <updated>2026-07-21T10:50:33Z</updated>
  <dc:date>2026-07-21T10:50:33Z</dc:date>
  <entry>
    <title>RE: ss3.30 forecast</title>
    <link rel="alternate" href="https://vlab.noaa.gov/c/message_boards/find_message?p_l_id=8790705&amp;messageId=10432242" />
    <author>
      <name>Dan Fu</name>
    </author>
    <id>https://vlab.noaa.gov/c/message_boards/find_message?p_l_id=8790705&amp;messageId=10432242</id>
    <updated>2020-06-11T16:55:50Z</updated>
    <published>2020-06-11T16:55:50Z</published>
    <summary type="html">&lt;p&gt;Thanks Rick, that is very quick. Please keep me posted on the new release :)&amp;nbsp;&lt;/p&gt;</summary>
    <dc:creator>Dan Fu</dc:creator>
    <dc:date>2020-06-11T16:55:50Z</dc:date>
  </entry>
  <entry>
    <title>RE: ss3.30 forecast</title>
    <link rel="alternate" href="https://vlab.noaa.gov/c/message_boards/find_message?p_l_id=8790705&amp;messageId=10431914" />
    <author>
      <name>Richard Methot</name>
    </author>
    <id>https://vlab.noaa.gov/c/message_boards/find_message?p_l_id=8790705&amp;messageId=10431914</id>
    <updated>2020-06-11T16:35:10Z</updated>
    <published>2020-06-11T16:35:10Z</published>
    <summary type="html">&lt;p&gt;Dan,&lt;/p&gt;

&lt;p&gt;I have diagnosed the problem.&amp;nbsp; It is not related to setting the forecast catch = 0.&amp;nbsp; Rather it is a problem with the propagation of the forecast population agecomp from one time step to the next.&amp;nbsp; I see how to fix it and will get a new exe posted soon.&amp;nbsp; But I also want to hunt down when this problem got introduced.&amp;nbsp; A similar issue occurred for another user with age at settlement = 1.&amp;nbsp; That got fixed but now you encounter a similar problem with multiple seasons.&amp;nbsp; Top priority now.&lt;/p&gt;

&lt;p&gt;Rick&lt;/p&gt;</summary>
    <dc:creator>Richard Methot</dc:creator>
    <dc:date>2020-06-11T16:35:10Z</dc:date>
  </entry>
  <entry>
    <title>RE: ss3.30 forecast</title>
    <link rel="alternate" href="https://vlab.noaa.gov/c/message_boards/find_message?p_l_id=8790705&amp;messageId=10431657" />
    <author>
      <name>Dan Fu</name>
    </author>
    <id>https://vlab.noaa.gov/c/message_boards/find_message?p_l_id=8790705&amp;messageId=10431657</id>
    <updated>2020-06-11T15:51:10Z</updated>
    <published>2020-06-11T15:51:10Z</published>
    <summary type="html">&lt;p&gt;Hi Rick, I am using the lastest version from vLab :3.30.15.&lt;/p&gt;

&lt;p&gt;Note that in the model, the F for fleet 6 (longline) is extremely high,&amp;nbsp; although the the catch is very tiny. This is because the selectivity for fleet 6&amp;nbsp;is very&amp;nbsp; poorly estimated. But I don't think this is a separate issue and should not be&amp;nbsp;what cause the problem as the projection&amp;nbsp;works fine in 3.24, and the catch for all fleets are set to zero in the projection anyway.&lt;/p&gt;

&lt;p&gt;&amp;nbsp;&lt;/p&gt;

&lt;p&gt;Thanks for helping out.&lt;/p&gt;

&lt;p&gt;&amp;nbsp;&lt;/p&gt;

&lt;p&gt;Dan&amp;nbsp;&lt;/p&gt;</summary>
    <dc:creator>Dan Fu</dc:creator>
    <dc:date>2020-06-11T15:51:10Z</dc:date>
  </entry>
  <entry>
    <title>RE: ss3.30 forecast</title>
    <link rel="alternate" href="https://vlab.noaa.gov/c/message_boards/find_message?p_l_id=8790705&amp;messageId=10431274" />
    <author>
      <name>Richard Methot</name>
    </author>
    <id>https://vlab.noaa.gov/c/message_boards/find_message?p_l_id=8790705&amp;messageId=10431274</id>
    <updated>2020-06-11T15:42:53Z</updated>
    <published>2020-06-11T15:42:53Z</published>
    <summary type="html">&lt;p&gt;Hi Dan,&lt;/p&gt;

&lt;p&gt;Sorry that you ran into a problem here, we'll take a look.&amp;nbsp; Which version of 3.30 are you using?&lt;/p&gt;

&lt;p&gt;Rick&lt;/p&gt;</summary>
    <dc:creator>Richard Methot</dc:creator>
    <dc:date>2020-06-11T15:42:53Z</dc:date>
  </entry>
  <entry>
    <title>ss3.30 forecast</title>
    <link rel="alternate" href="https://vlab.noaa.gov/c/message_boards/find_message?p_l_id=8790705&amp;messageId=10428196" />
    <author>
      <name>Dan Fu</name>
    </author>
    <id>https://vlab.noaa.gov/c/message_boards/find_message?p_l_id=8790705&amp;messageId=10428196</id>
    <updated>2020-06-11T09:59:52Z</updated>
    <published>2020-06-11T09:46:21Z</published>
    <summary type="html">&lt;p&gt;Dear SS3 team,&lt;/p&gt;
&lt;p&gt;I run into an issue with the SS3.30 (lastest) constant catch
  forecasting, which doesn't appear to be working.&lt;/p&gt;
&lt;p&gt;I simply set up a 10-year forecast with catch set to zero for all
  fleets. The SS3.24 forecast works as intended which shows SSB rapidly
  increasing (see attached SS3.24-forecast.png).&lt;br /&gt; But the forecast
  for  SS3.30 files failed - the SSB crashed a few years into the
  projection period (see attached SS3.30-forecast.png).&lt;/p&gt;
&lt;p&gt;Parameter estimates from the 3.30 are the same as the 3.24 (I used
  the ss_trans.exe for the conversion).&lt;/p&gt;
&lt;p&gt;Running the forecast with alternative catch levels under 3.30 had the
  same issue&lt;/p&gt;
&lt;p&gt;I have attached the input files for SS3.24 and the problem is very
  easy to reproduce.&lt;/p&gt;
&lt;p&gt;Hope you could help me look into this issue - (Most likely I have
  missed some configuration in the 3.30 forecast file?)&lt;/p&gt;
&lt;p&gt;Thanks for your help.&lt;/p&gt;
&lt;p&gt;Dan &lt;/p&gt;</summary>
    <dc:creator>Dan Fu</dc:creator>
    <dc:date>2020-06-11T09:46:21Z</dc:date>
  </entry>
</feed>

