Skip to content

Releases: nmfs-fish-tools/MSSPM

1.2.6 Release for Linux

02 Sep 03:17
Compare
Choose a tag to compare
  • Fixed bug with parameter estimation starting with mid-range point instead of with the initial parameter value

1.2.5 Release for Windows

30 Aug 21:40
Compare
Choose a tag to compare
  • Added a wait cursor to the Covariate save functionality
  • Added a stop timer call after a Bees run (If then followed by an NLopt run, the NLopt run wouldn’t finish)
  • Fixed problem with random number generator sometimes returning the incorrect scaled value (this allowed negative parameters)

1.2.5 Release for Linux

30 Aug 20:53
Compare
Choose a tag to compare
  • Added a wait cursor to the Covariate save functionality
  • Added a stop timer call after a Bees run (If then followed by an NLopt run, the NLopt run wouldn’t finish)
  • Fixed problem with random number generator sometimes returning the incorrect scaled value (this allowed negative parameters)

1.2.4 Release for Windows

26 Aug 21:04
Compare
Choose a tag to compare
  • Modified elapsed timer to update for estimations without any specified ranges

1.2.4 Release for Linux

26 Aug 20:44
Compare
Choose a tag to compare
  • Modified elapsed timer to update for estimations without any specified ranges

1.2.3 Release for Windows

26 Aug 16:56
Compare
Choose a tag to compare

Release Instructions

  1. I've modified the models table structure to support the additional parameter for GN_CRS2_LM. In order for MSSPM to work correctly going forward, you must do one of the following:
  • Import the new sample database. N.B. Doing this will overwrite your current database!
    OR
  • If you don't want to overwrite your current database, run the following lines at the mysql command line prompt:
    • use keyrun_2022
    • alter table models add column NLoptUseInitialPopulationSize int NULL after NLoptUseStopAfterIter;
    • alter table models add column NLoptInitialPopulationSize double NULL after NLoptStopAfterIter;
  1. If you choose not to load the new sample database, and if you haven't already copied and pasted the covariate data into your database, you can import it from within MSSPM.
  • Importing Covariate data:
    • Click Import in the Estimation Tab 6 - Covariate Data.
    • When the Import popup appears, click No, and then find and Open the covariate.csv in the sample_data directory.
    • Click Save to save the imported covariate data to your current database.

Release Notes

  • Added new Troubleshooting Estimation topic
  • Added Hubert’s Covariate data to sample database as well as covariate.csv to sample_data directory
  • Added another global minimizer algorithm: GN_ESCH - an evolutionary algorithm
  • Added additional parameter for GN_CRS2_LM NLopt model
  • Modified WhatsThis help for Minimizer algorithms (currently the popup may not fit on a laptop)
  • Modified the maximum parameter range that can be automatically set by the user to be ±99%
  • Fixed ClearSpecificOutput widgets not being properly loaded
  • Fixed bug when flipping chart type to Diagnostics or Forecasts, before they’ve been run, not yielding a blank plot
  • Fixed Retrospective Analysis Chart showing a blue plot line when chart type changes from Diagnostics to something else and back to Diagnostics
  • Fixed crash when changing the database and saving the Project but not loading a model

1.2.3 Release for Linux

26 Aug 15:22
Compare
Choose a tag to compare

Release Instructions

  1. I've modified the models table structure to support the additional parameter for GN_CRS2_LM. In order for MSSPM to work correctly going forward, you must do one of the following:
  • Import the new sample database. N.B. Doing this will overwrite your current database!
    OR
  • If you don't want to overwrite your current database, run the following lines at the mysql command line prompt:
    • use keyrun_2022
    • alter table models add column NLoptUseInitialPopulationSize int NULL after NLoptUseStopAfterIter;
    • alter table models add column NLoptInitialPopulationSize double NULL after NLoptStopAfterIter;
  1. If you choose not to load the new sample database, and if you haven't already copied and pasted the covariate data into your database, you can import it from within MSSPM.
  • Importing Covariate data:
    • Click Import in the Estimation Tab 6 - Covariate Data.
    • When the Import popup appears, click No, and then find and Open the covariate.csv in the sample_data directory.
    • Click Save to save the imported covariate data to your current database.

Release Notes

  • Added new Troubleshooting Estimation topic
  • Added Hubert’s Covariate data to sample database as well as covariate.csv to sample_data directory
  • Added another global minimizer algorithm: GN_ESCH - an evolutionary algorithm
  • Added additional parameter for GN_CRS2_LM NLopt model
  • Modified WhatsThis help for Minimizer algorithms (currently the popup may not fit on a laptop)
  • Modified the maximum parameter range that can be automatically set by the user to be ±99%
  • Fixed ClearSpecificOutput widgets not being properly loaded
  • Fixed bug when flipping chart type to Diagnostics or Forecasts, before they’ve been run, not yielding a blank plot
  • Fixed Retrospective Analysis Chart showing a blue plot line when chart type changes from Diagnostics to something else and back to Diagnostics
  • Fixed crash when changing the database and saving the Project but not loading a model

1.2.2 Release for Windows

22 Aug 14:40
Compare
Choose a tag to compare
  • Added another check when deleting last covariate time series column
  • Added topic groups for Troubleshooting GUI

1.2.2 Release for Linux

22 Aug 14:10
Compare
Choose a tag to compare
  • Added another check when deleting last covariate time series column
  • Added topic groups for Troubleshooting GUI

1.2.1 Release for Windows

18 Aug 21:50
Compare
Choose a tag to compare
  • Changed Setup “Add” Project Database button name to “New”
  • Added an “Import” Project Database button to Project Setup page
  • Added a check that after an Import, the project name must be the name of the project in the imported database, and if not, the user should change the name
  • Added a Troubleshooting issue