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

define SCR_Start_input API #485

Open
adammoody opened this issue Feb 27, 2022 · 0 comments
Open

define SCR_Start_input API #485

adammoody opened this issue Feb 27, 2022 · 0 comments

Comments

@adammoody
Copy link
Contributor

adammoody commented Feb 27, 2022

For applications that write output datasets SCR_FLAG_OUTPUT, it would be useful to define a start/complete interface for accessing those files for input. Input datasets could be checkpoints.

Similar to the restart interface, this might look something like:

SCR_Have_input(int* have_input, char* dset)
SCR_Start_input(char* dset)
SCR_Complete_input(int valid)

One could provide the name of the dataset that they intend to open. SCR should be able to report whether it has that dataset available. This could be done in the Have_input call. Those semantics are a bit different than Have_restart. If we adopt this new interface, we might deprecate Have_restart or redefine its behavior.

SCR would identify where the dataset exists, perhaps loading it if needed (which may include extraction, decompression, rebuild, etc). Between the start/complete calls, route_file would point to the proper location. The start/complete calls are needed since SCR may move/delete the dataset outside of those bookends.

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

1 participant