-
Notifications
You must be signed in to change notification settings - Fork 26
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
reporting percentage job completion #371
Comments
Yes. How you want the callback to behave?
- write to stdout with fixed pattern. E.g. should I write 'PROGRESS=50%` etc to stdout. This is enabled by environment variable such as 'MOOSE_DISPLAY_PROGRESS'. (simple) There is already something similar if you use `moose.start(time, True)` or `moose.start(time, 1)`.
- Write to a fixed temporary files e.g. /tmp/MOOSE_PROGRESS and JS reads it. (simple)
- Transmit logs to a socket. More generic and powerful solution. JS reads from the socket. (moderate complexity).
|
I think "Transmit logs to a socket. More generic and powerful solution. JS reads from the socket. (moderate complexity)" is the best option. Since I need it for the web-portal, for now, I can make a js request and get the progress report. Also, will this solution work for the standalone findsim run? (if upi changes his code in findsim.py) |
Is it essential for GSoC to move ahead? Otherwise I'd put it on backburner for couple of weeks. |
It is not impeding the GSoC project. However, I was thinking that he can implement the JS part to get progress from the Transmit log socket. So it would be better if it can be implemented before GSoC ends, which is 26th July. |
Stale issue message |
Can a callback be implemented to get what percentage of the job is completed after a time period from job submission?
The text was updated successfully, but these errors were encountered: