Order of more complex Q parameter setups is not clear

[okenk]

I am trying to set up an index with a power relationship and an extraSD parameter. Based on the examples I am not sure if the extraSD parameter or the power function parameter should go first. Perhaps the example could be slightly more complex, or some text could be added describing the logic SS3 uses when reading in Q parameters.

[Rick-Methot-NOAA]

I suggest generating a test with adhoc order, run with
-stopph -1 -nohess
so that SS3 simply reads the input files, then writes the ss_new files. The parameter labels generated by SS3 will show in the ss_new files and tell you the order. Let us know what it is so we can update the documentation!

[e-perl-NOAA]

Looking at the order of the ss3 read control file, the ss_summary.sso file from the 2025 yellowtail assessment, and lines from an ICES sardine assessment control file, it appears to me that the power param goes before the extra_SD param. This is just one of those classic situations where it's hard to have examples of every configuration in SS3 because there are just so many! But I will be sure to add the extra sd param line to the current example

[okenk]

Well this is embarrassing since I made that yellowtail model! 🤦

Thank you! And yeah, totally understand that you can't have examples of every possible configuration. Maybe if the extraSD parameter always comes last (which I think it does?) it would be worth pointing that out? No need to think of every possible configuration that way.