Opened 18 years ago
Closed 18 years ago
#26 closed defect (wontfix)
gripes about summary
| Reported by: | Owned by: | Chris Phillips | |
|---|---|---|---|
| Priority: | high | Milestone: | ASAP 2.1 |
| Component: | General | Version: | 2.0 |
| Severity: | normal | Keywords: | |
| Cc: | Tony.Wong@… |
Description
- The output of summary is too verbose now. Information is spread loosely over 3 80-column lines. Hard to remember what each column means, and use of Hz for frequencies creates unwieldy numbers.
- At least on kaputar, invoking scans.summary() opens a separate pager which disappears when done. If the information is not going to pop out in a separate window then it should stay in the screen buffer.
Change History (3)
comment:1 Changed 18 years ago by
| Cc: | Tony.Wong@… added |
|---|---|
| Priority: | normal → high |
| Status: | new → assigned |
comment:2 Changed 18 years ago by
| Cc: | chris.phillips@… added |
|---|---|
| Milestone: | ASAP2 release → ASAP 2.1 |
| Owner: | changed from Malte Marquarding to Chris Phillips |
| Status: | assigned → new |
Tony,
This needs a bit more discussion to what is useful for all cases (mulit-beam/if) I have reassigned this to Chris, and moved it into the Release 2.1 targets
comment:3 Changed 18 years ago by
| Cc: | chris.phillips@… removed |
|---|---|
| Resolution: | → wontfix |
| Status: | new → closed |
Summary function cannot really be cut down any further without being useless. Ticket closed unless a contrete alternative is suggested. I am hoping in the next version of asap all these header variables will be available to the users, so a custom "summary" function specific to the users need could be written easily.
Note: See
TracTickets for help on using
tickets.
I agree, I should reintroduce the verbose toggle. What would you like to see in a terse summary?