search

malonzo47 / pynita_GUI

pynita_GUI is python GUI based implementation of Noise Insensitive Trajectory Algorithm (NITA)
4 stars 3 forks source link

general error handling #49

Closed malonzo47 closed 5 years ago

malonzo47 commented 5 years ago

This issue may be too broad but we need to handle errors wherein users deviate for the strict workflow without the GUI crashing. One example: If user specifies a VI (e.g., ndwi) that is not a column in pts.csv then tries to visualize points, the program crashes. Instead, they should be warned to adjust the VI in Step 1.

Should I actually log an issue for each specific workflow?

vasusingla commented 5 years ago

yes mike, i will require more specific details, as to where the errors arise.

malonzo47 commented 5 years ago

Definitely. I was thinking though: Is there a general way such as a try-catch to deal with as-yet-unknown issues more gracefully? For example, just reporting error text in a pop-up and forcing user to go back one step in their workflow? (no idea if that's feasible in reality).

On Mon, Mar 4, 2019 at 5:26 AM vasusingla619 notifications@github.com wrote:

yes mike, i will require more specific details, as to where the errors arise.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/malonzo47/pynita_GUI/issues/49#issuecomment-469200419, or mute the thread https://github.com/notifications/unsubscribe-auth/AOh1_B3zhUoGwOboouAiJXUIUhR1Qvbxks5vTPSqgaJpZM4baZDd .

vasusingla commented 5 years ago

of course, though i might need to make a lot of changes, the previous code has little exception handling. I've had a lot of crashes myself.

malonzo47 commented 5 years ago

Closing this in favor of more specific exception handling issues.