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.

Sign up for GitHub

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

Jump to bottom

Accepting alternative inputs for time steps #75

Open

2 tasks

sjordan29 opened this issue Mar 14, 2024 · 0 comments

Labels

Milestone

Additional Perfor...

Contributor

sjordan29 commented Mar 14, 2024

Initial implementation of pre-initializing timesteps takes a integer number of timesteps. We should expand this to include:

Users to specify a timeseries (as a list?) to initialize the time dimension
Users to provide a hotstart dataset that is pre-initialized on the time dimension. This would allow users to input a partially filled in hotstart dataset. The model would find the last populated timestep and use just that timestep onward moving forward to free up memory.

Others?

sjordan29 added the enhancement label

sjordan29 mentioned this issue

Pre-initialize output xarray time coordinates and variables #68

Closed

aufdenkampe added this to the Performance enhancements for NSM demo milestone

aufdenkampe modified the milestones: Performance enhancements for NSM demo, Additional Performance Enhancements

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