#57 closed Defect (fixed)
Wrong version strings in header and header_nest files
Reported by: | radekhofman | Owned by: | anphi |
---|---|---|---|
Priority: | minor | Milestone: | FLEXPART 9.2 |
Component: | FP other | Version: | FLEXPART 9.0 |
Keywords: | Cc: | rstow |
Description
When reading outputs from FLEXPART 9.0, there are different version strings in header_nest and header files: header_nest contains "FLEXPART V8.2" and header contains "FLEXPART V9.0" which is confusing.
For reading headers I used flex_81.py module: "Reading and unpacking routines from J.Brioude (NOAA)".
Change History (7)
comment:1 Changed 11 years ago by DefaultCC Plugin
- Cc rstow added
comment:2 Changed 11 years ago by pesei
- Milestone set to FLEXPART 9.2
- Owner changed from somebody to ignacio
- Status changed from new to assigned
comment:3 follow-up: ↓ 4 Changed 10 years ago by anphi
- Owner changed from ignacio to anphi
- Status changed from assigned to accepted
Its solved in FLEXPART version 9.2 beta!
comment:4 in reply to: ↑ 3 ; follow-up: ↓ 5 Changed 10 years ago by pesei
Replying to anphi:
Its solved in FLEXPART version 9.2 beta!
What's the version string like?
Also, to avoid different version strings by mistake, the version string should become a global variable!
comment:5 in reply to: ↑ 4 ; follow-up: ↓ 7 Changed 10 years ago by anphi
Replying to pesei:
Replying to anphi:
Its solved in FLEXPART version 9.2 beta!
What's the version string like?
Also, to avoid different version strings by mistake, the version string should become a global variable!
Yes indeed. It is already solved with a global variable and is set to the current version 9.2!
comment:6 Changed 10 years ago by anphi
- Resolution set to fixed
- Status changed from accepted to closed
comment:7 in reply to: ↑ 5 Changed 10 years ago by pesei
Replying to anphi:
Replying to pesei:
Replying to anphi:
Its solved in FLEXPART version 9.2 beta!
What's the version string like?
Also, to avoid different version strings by mistake, the version string should become a global variable!
Yes indeed. It is already solved with a global variable and is set to the current version 9.2!
I think it would be good if the version string would not only contain major.minor but instead characterise the present release as suggested in http://www.flexpart.eu/ticket/46#comment:2
Even though old version should in principle remain as they are, we might wish to correct all previous versions - it is very problematic.
FLEXPART 9.2 should be carefully checked for correctness. So I assign this to Ignacio.