search

pacific-hake / hake-assessment

:zap: :fish: Build the assessment document using latex and knitr
MIT License
13 stars 6 forks source link

Bug in forecasting #1133

Closed cgrandin closed 8 months ago

cgrandin commented 8 months ago

I just noticed that the FI 100% forecasts are based off the DHCR. Unless a total coincidence, I don't think the 2024 value should be the same for both FI=100% and DHCR. Here is last year: image Here is this year: image

cgrandin commented 8 months ago

Does not appear to be a bug, it looks like I just had the tolerance for the FSPR case set to 10%, and the FSPR value at the TAC of 545,000 was 0.915 so it passed on the first pass, and never updated the initial value. I am setting the tolerance to 1% and re-running the forecasting (we needed to anyway to update the 2023 TAC to 625,000).

Mt fault on this one, I forgot that I had set all the tolerances so that the forecasting ran more quickly during the draft process so we could "get working" and forgot to re-run them at a lower tolerance. I think we will have to hand out new decision tables.

This should be all done by later tonight or tomorrow. I don't know for sure how long because of the iterative nature of the "zoning in on catch" algorithms.

cgrandin commented 8 months ago

There were two issues here. In addition to the tolerances being set too high I discovered another bug. The FSPR=100% and Default HR cases were swapped. So in the decision table in the draft, rows 'm' and 'n' were swapped. That doesn't really matter and we could just not even mention it because they are almost identical anyway in the draft due to the tolerance issue.

All this has been fixed and the new decision table looks ok. Here it is for Rel. biomass:

image

Also, the last bullet in the One-page Summary has changed a lot due to the 625,000 TAC instead of 545,000: image

andrew-edwards commented 8 months ago

Nicely done. If I remember correctly we had a similar problem in a previous year, or maybe the numbers came out the same (by coincidence) and it was a bit confusing. So the numbers in the draft are correct, they just don't correspond to last year's TAC. I would say the percentages have not changed too much, and such catches are way above realistic catches anyway, so not a huge deal (no need to alert anyone before the meeting I think). And so bullet 3 (and other text) will automatically get updated with the 2023 corrected TAC. All sounds good. Thanks Chris.

andrew-edwards commented 8 months ago

Though I guess stating last year's TAC incorrectly is a bit of a big deal, so maybe we could send an email beforehand.

cgrandin commented 8 months ago

This is fully done now.