Opened 18 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 Changed 18 years ago by
Severity: | normal → minor |
---|---|
Status: | new → assigned |
comment:2 Changed 18 years ago by
Cc: | Tony.Wong@… 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 Changed 16 years ago by
Cc: | Tony.Wong@… removed |
---|---|
Milestone: | ASAP 2.2 → ASAP 2.4 |
comment:5 Changed 15 years ago by
Type: | defect → enhancement |
---|
comment:6 Changed 15 years ago by
Priority: | normal → suspended |
---|
comment:7 Changed 14 years ago by
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.