Show minor edits - Show changes to markup
Workaround: Patch with old re-sampling code.
Workaround: Patch with old re-sampling code, or remember to account for negative values
Versions tested: 4.1,4.2 & 3.8 Versions affected: >=4.1 Workaround: Patch with old re-sampling code.
Versions tested: 4.1,4.2 & 3.8
Versions affected: >=4.1
Workaround: Patch with old re-sampling code.
Versions tested: 4.1,4.2 & 3.8 Versions affected: all Workaround: A patch: patch. Note that this will mean that the DM is not set to 0 when completely decimating in frequency.
Versions tested: 4.1,4.2 & 3.8
Versions affected: all
Workaround: A patch: patch. Note that this will mean that the DM is not set to 0 when completely decimating in frequency.
When resampling a timeseries using decimate, the DM value in the header is set to 0.
When resampling a timeseries using decimate, the DM value in the header is set to 0, even if no frequency decimation occurs.
When using dedisperse with small numbers of channels (<12) and a strong source, the baselining causes the pulse power, and region round the pulse to be lowered. This may happen to a lesser degree with low power pulsars or with many channels, but it does not appear to be significant. This is probably caused when the pulse power is strong enough that single pulses can be detected in a single channel.
Versions tested: 3.8 only
Versions affected: 3.8 (probably affects all versions)
Workaround: Use -nobaseline
Submitted by: M Keith
New acceleration time stretching code causes incorrect acceleration value to be searched. This means that any detections in acceleration are negative of the real value.
Versions tested: 4.1,4.2 & 3.8 Versions affected: >=4.1 Workaround: Patch with old re-sampling code.
Submitted by: M Keith
When resampling a timeseries using decimate, the DM value in the header is set to 0.
Versions tested: 4.1,4.2 & 3.8 Versions affected: all Workaround: A patch: patch. Note that this will mean that the DM is not set to 0 when completely decimating in frequency.
Submitted by: M Keith
When using dedisperse with small numbers of channels (<12) and a strong source, the baselining causes the pulse power, and region round the pulse to be lowered. This may happen to a lesser degree with low power pulsars or with many channels, but it does not appear to be significant. This is probably caused when the pulse power is strong enough that single pulses can be detected in a single channel.
Versions tested: 3.8 only
Versions affected: 3.8 (probably affects all versions)
Workaround: Use -nobaseline
Submitted by: M Keith
Versions affected: 4.1\\
Versions affected: <=4.1\\
Fixed - Various patches to normalization routines.
After upgrading to 4.1, seek produces consistently lower SNR values than previous versions.
Versions tested: 4.1 and 3.8 only
Versions affected: 4.1
Workaround:
Submitted by: R Eatough
This is probably caused when the pulse power is strong enough that single pulses can be detected in a single channel.
Fix: Use -nobaseline
Versions tested: 3.8 only Versions affected: 3.8 (probably affects all versions) Workaround: Use -nobaseline
Please sign your entries here.
If you add any issues please sign your name!
When using dedisperse with small numbers of channels and a strong source, the baselining causes the pulse power, and region round the pulse to be lowered.
When using dedisperse with small numbers of channels (<12) and a strong source, the baselining causes the pulse power, and region round the pulse to be lowered. This may happen to a lesser degree with low power pulsars or with many channels, but it does not appear to be significant.
Fix: Use -nobaseline
Please sign your entries here.
When using dedisperse with small numbers of channels and a strong source, the baselining causes the pulse power, and region round the pulse to be lowered.
M Keith