Opened 18 years ago

Closed 14 years ago

#24 closed enhancement (fixed)

strange behaviour of set_restfreqs

Reported by: Tony.Wong@… 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 Malte Marquarding

Severity: normalminor
Status: newassigned

The correct restfrequency will be used though. I agree that there should be better feedback about which restfrequency is used where.

comment:2 Changed 18 years ago by Malte Marquarding

Cc: Tony.Wong@… added
Milestone: ASAP2 releaseASAP 2.1

This requires a bit of work. The next minor release (2.1) will include this fix.

comment:3 Changed 18 years ago by Malte Marquarding

Milestone: ASAP 2.1ASAP 2.2

Moved to Release 2.2

comment:4 Changed 16 years ago by Malte Marquarding

Cc: Tony.Wong@… removed
Milestone: ASAP 2.2ASAP 2.4

comment:5 Changed 15 years ago by Malte Marquarding

Type: defectenhancement

comment:6 Changed 15 years ago by Malte Marquarding

Priority: normalsuspended

comment:7 Changed 14 years ago by Malte Marquarding

Resolution: fixed
Status: assignedclosed

Restfrequencies are no replacing existing ones.

Note: See TracTickets for help on using tickets.