Opened 19 years ago
Closed 14 years ago
#24 closed enhancement (fixed)
strange behaviour of set_restfreqs
| Reported by: | Owned by: | Malte Marquarding | |
|---|---|---|---|
| Priority: | suspended | Milestone: | ASAP 2.4 |
| Component: | General | Version: | 2.0 |
| Severity: | minor | Keywords: | |
| Cc: |
Description
set_restfreqs adds to the vector of rest frequencies instead of replacing it.
For example:
Rest Freqs: [1.09782e+11] [Hz]
scans.set_restfreqs(freqs=115.2712e9)
Rest Freqs: [1.09782e+11, 1.152712e+11] [Hz]
Change History (7)
comment:1 by , 19 years ago
| Severity: | normal → minor |
|---|---|
| Status: | new → assigned |
comment:2 by , 19 years ago
| Cc: | added |
|---|---|
| Milestone: | ASAP2 release → ASAP 2.1 |
This requires a bit of work. The next minor release (2.1) will include this fix.
comment:4 by , 16 years ago
| Cc: | removed |
|---|---|
| Milestone: | ASAP 2.2 → ASAP 2.4 |
comment:5 by , 16 years ago
| Type: | defect → enhancement |
|---|
comment:6 by , 15 years ago
| Priority: | normal → suspended |
|---|
comment:7 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Restfrequencies are no replacing existing ones.
Note:
See TracTickets
for help on using tickets.
The correct restfrequency will be used though. I agree that there should be better feedback about which restfrequency is used where.