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

Models only perform on-server computation if the output artifacts are missing. #105

Closed
tshead2 opened this issue Nov 25, 2013 · 1 comment
Assignees

Comments

@tshead2
Copy link
Member

tshead2 commented Nov 25, 2013

Currently, we assume that when we finish a model it must compute its output artifacts from its input artifacts. Instead, we should check to see if the output artifacts already exist (i.e. were uploaded from a remote analysis), in which case there's nothing more to do.

@ghost ghost assigned tshead2 Nov 25, 2013
@tshead2
Copy link
Member Author

tshead2 commented Dec 2, 2013

An alternative would be to allow external clients to set the model state from running to finished themselves. In fact, if we're doing external computation, we're going to need to set progress and messages, so this would make external computation work just like internal computation.

Currently, clients start internal computation by changing the state from waiting to running, so if we go this route, we'll need some other way of doing it, i.e. going back to a dedicated API for starting internal computation.

tshead2 added a commit that referenced this issue Dec 2, 2013
…rough the API, and create separate API to start internal computation. Closes #105.
@tshead2 tshead2 closed this as completed Dec 2, 2013
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

1 participant