Need to add ability to specify more than one custom_MS_source?

[k-doering-NOAA]

In #144 @rwildermuth noted the following:

[...]I need to call run_SSMSE() separately for our project in order to use multiple different custom HCR functions and [run_SSMSE()] won't allow you to specify more than one 'custom_MS_source'.

@rwildermuth, just wanted to ping you about this - is there a good reason why all the functions couldn't be put in one file? Would the option to specify multiple sources (source files) help?

[rwildermuth]

Each of our custom MSs uses a different harvest control rule function (i.e., shape), each of which have different inputs. I'm not sure if there's a place in the run_SSMSE() function to specify arguments for the custom MS wrt each scenario. I know your examples mostly deal with running the same rules on different OM formulations as scenarios, but the way I've set things up is to run a round of HCRs on the same OM scenario. Maybe it makes more sense to vary the OM specification and hold the HCR constant for tandem run_SSMSE() runs? Having an option to specify multiple source files, or an option to provide scenario-specific function arguments, may make things more straightforward. However, because the parallel processing requires all iterations of a scenario to finish before moving on to the next scenario, there's not much difference between calling run_SSMSE() separately for each scenario vs. running multiple scenarios in tandem with a single run_SSMSE() call.

…

On Tue, Dec 27, 2022 at 12:12 PM Kathryn Doering ***@***.***> wrote: In #144 <#144> @rwildermuth <https://github.com/rwildermuth> noted the following: [...]I need to call run_SSMSE() separately for our project in order to use multiple different custom HCR functions and [run_SSMSE()] won't allow you to specify more than one 'custom_MS_source'. @rwildermuth <https://github.com/rwildermuth>, just wanted to ping you about this - is there a good reason why all the functions couldn't be put in one file? Would the option to specify multiple sources (source files) help? — Reply to this email directly, view it on GitHub <#145>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACXJHTQTFPXVV4SJAJNZ7PLWPNETBANCNFSM6AAAAAATKV7TSI> . You are receiving this because you were mentioned.Message ID: ***@***.***>