More information about job status, or error messages

[nickhorspool]

We need to think of a way to pass back more information to the scenario page about how the job is progressing. At the moment there are quite a few STATUS codes, which we need to make more clear to a general user. If the job returns an error, we need them to be able to know what that is (ie, not mount VM, anuga crashed (why?), geonode did not send email and make map) etc.

During the workshop, I was monitoring the scenarios, but this is not sustainable. We need to give the user more information, and get our error messages making sense. This will need collaboration with Ross.

[jj0hns0n]

There is a LOG status that is put into the queue periodically, but Im currently ignoring it on the TsuDAT side. Perhaps this can be used for this purpose.

This kind of needs to be broken down into multiple parts:

1. status updates (using the LOG code?). Is there some way to grab the ANUGA log file and push it to the main web server periodically, perhaps using the NFS mounted directory.

2. better reporting of the actual errors that occur. I think its useful to document (on the wiki?) the kinds of errors we have encountered, and from that discuss how each one could be trapped and reported back to the user in the best possible way.

[nickhorspool]

Ross documented some errors - Ross can you forward your wrap up doc to the tsudat mailling list.

nick

On 29/06/2011, at 5:10 AM, jj0hns0n wrote:

There is a LOG status that is put into the queue periodically, but Im currently ignoring it on the TsuDAT side. Perhaps this can be used for this purpose.

This kind of needs to be broken down into multiple parts:

1. status updates (using the LOG code?). Is there some way to grab the ANUGA log file and push it to the main web server periodically, perhaps using the NFS mounted directory.

2. better reporting of the actual errors that occur. I think its useful to document (on the wiki?) the kinds of errors we have encountered, and from that discuss how each one could be trapped and reported back to the user in the best possible way.

Reply to this email directly or view it on GitHub:
#60 (comment)

[jj0hns0n]

Some info from ticket 66 (which was closed as a duplicate)

At present, if the TsuDAT simulation crashes in the ANUGA simulation the user only see's the ABORT status in the scenario page and they do not have any access to the ANUGA logs. Ideally the ANUGA logs should be sent to the scenario page so the user can check the status (ie. the time step the simulation is at) and if it crashes they can at least see the error messages to help debug the scenario.

This task will require assistance from the backend developers to bring the log back to the UI.