Opened 15 years ago
Closed 13 years ago
#185 closed enhancement (fixed)
2D ropp_io routine 'rationalisation'
| Reported by: | Huw Lewis | Owned by: | Ian Culverwell |
|---|---|---|---|
| Priority: | normal | Milestone: | 5.1 |
| Component: | ropp_io | Version: | 3.0 |
| Keywords: | Cc: |
Description (last modified by )
The introduction of 2D background data at ROPP-4 has required new ropp_io read/write, init/free routines to process 2D data, and the introduction of a ROprof2d structure.
Only the Level2b and Level2c elements of the ROprof structure differ between ROprof and ROprof2d. At present, entirely separate routines have been written to process ROprof and ROprof2d, with significant overlap between the two codes.
It is desirable to 'rationalise' the ropp_io code further to provide interfaces to most ropp_io/ropp routines at the 'Level' stage such that the 'master' routines call the required subroutines for the Levels required.
This model is currently followed in routines ropp_io_free and ropp_io_init, but could be extended to all read/write routines.
Change history (4)
comment:1 by , 15 years ago
| Description: | modified (diff) |
|---|---|
| Owner: | removed |
| Status: | new → assigned |
comment:2 by , 13 years ago
| Owner: | set to |
|---|
comment:3 by , 13 years ago
| Milestone: | 5.0 → 5.1 |
|---|
comment:4 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
I don't understand this ticket. As far as I can see, ropp_io_read, ropp_io_write etc are the same as ropp_io_free and ropp_io_init. They're all interfaced in the same way in ropp_io.f90, so the user calls ropp_io_read whether he or she wants 1d or 2d info.
It looks to me like the work on this ticket has been done. Closing it.