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

Speed compared to HYSPLIT GUI #14

Closed
sean-horvath opened this issue Jul 11, 2017 · 2 comments
Closed

Speed compared to HYSPLIT GUI #14

sean-horvath opened this issue Jul 11, 2017 · 2 comments

Comments

@sean-horvath
Copy link

I'm running SplitR and it takes much much longer to get through simulations that just using the GUI. Did you find this to be true as well? Any ideas how to remedy this? Thanks!

@rich-iannone
Copy link
Owner

Faster code will fix this. I’m going to introduce some timing functions and work toward reducing the time per complete run.

@rich-iannone
Copy link
Owner

When all of the met data is already available, the following takes 1m50s on my MacBook Pro (15-in, 2017, 2.9 GHz Core i7, 16 GB 2133 MHz RAM):

traj_model <- 
  create_traj_model() %>%
  add_grid(
    lat = 49.0,
    lon = -123.0,
    range = c(0.8, 0.8),
    division = c(0.2, 0.2)
  ) %>%
  add_params(
    height = 50,
    duration = 6,
    days = seq(
      lubridate::ymd("2012-02-01"),
      lubridate::ymd("2012-02-28"),
      by = "1 day"
    ),
    daily_hours = c(0, 12),
    direction = "backward",
    met_type = "gdas1",
    met_dir = here::here("met"),
    exec_dir = here::here("out")
  ) %>%
  run_model()

I'm not ever going to compare this against the GUI, but, I will try to reduce this amount of of time with better code.

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

No branches or pull requests

2 participants