Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: starting seed selection #29

Open
Jamesrrobbins opened this issue Nov 25, 2022 · 3 comments
Open

Suggestion: starting seed selection #29

Jamesrrobbins opened this issue Nov 25, 2022 · 3 comments

Comments

@Jamesrrobbins
Copy link

Great work on this app - I use it regularly. One thing that would be useful is the ability to reproduce results by adding functionality to select a starting seed.

I have coded this into the local shiny app for personal use, but think it would be useful to be rolled out for others for greater reproducibility and transparency.

All that I did was:

Added the following to L358/359 in ui.r, below selection for number of iterations:

hr(),
numericInput("seed", "Starting seed", 52),

within server.r:
observeEvent(input$actButtonInput_simulPars_GO, {
set.seed(input$seed)
...

elsewhere in server.r (potentially not needed):
reactive({
set.seed(input$seed)

})

I think this addition would help a lot of us in consultancy who end up running many iterations of these models over the development lifecycle of projects.

@bcaneco
Copy link
Member

bcaneco commented Nov 25, 2022

Hi James, thanks for the feedback and for the useful suggestion.

This app is currently undergoing an updating process (e.g. inclusion of multiple WF scenarios, faster runs, etc), where the option of selecting the starting seed is available.

The Beta version is here - https://github.com/dmpstats/sCRM. Feel free to take it for a spin!

@Jamesrrobbins
Copy link
Author

Jamesrrobbins commented Dec 2, 2022 via email

@bcaneco
Copy link
Member

bcaneco commented Dec 2, 2022

Cheers James. The upgraded version also outputs all the draws of simulated collisions, so that should help.

For those large numbers of turbine scenarios I'd probably stick to the recently released stochLAB package - a bit more lead-up coding time required for setting up multiple scenario runs, but in the long term more efficient and reproducible when compared to typing inputs in the app, specially if re-runs are needed (as they almost always are!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants