Opened 9 years ago
Last modified 8 years ago
#59 accepted Enhancement
Improve error messages
Reported by: | pesei | Owned by: | anphi |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | FP coding/compilation | Version: | FLEXPART 9.2 beta |
Keywords: | Cc: |
Description
Many of the FLEXPART error messages don't contain enough or appropriate content, for example they say that some variable is outside the expected range but don't give its actual value or the value of the expected range.
Change History (4)
comment:1 Changed 9 years ago by anphi
- Owner changed from somebody to anphi
- Status changed from new to accepted
comment:2 Changed 9 years ago by anphi
comment:3 Changed 9 years ago by pesei
- Version changed from FLEXPART 9.0.2 to FLEXPART 9.2 beta
If the Output/ directory is not found, Fp issues the wrong error message:
#### FLEXPART MODEL ERROR! FILE "COMMAND" #### #### CANNOT BE OPENED IN THE DIRECTORY ####
comment:4 Changed 8 years ago by hasod
Verbosity output should be written from one common method as proposed in the comments to changeset:27 by pesei
Note: See
TracTickets for help on using
tickets.
Everyone who has wishes or ideas to improve the error messages in FLEXPART is welcome to add them in a comment or write an email to me.
I will think about the best way to improve the error handling and keep you updated with a plan and implementation progress.