SixByNine / sigproc

My version of Dunc Lorimer's public free searching software
sigproc.sourceforge.net
23 stars 18 forks source link

Frequency channel range conversion wrong in filterbank? #1

Closed matteobachetti closed 9 years ago

matteobachetti commented 9 years ago

Hi, I'm converting DFB data in search mode (from SRT) to filterbank format. I use simply filterbank filename.sf -o filename.fil. If I then print the file information with PRESTO's readfile I obtain the following:

(...)
         Central freq (MHz) = 7312             
          Low channel (MHz) = 6802             
         High channel (MHz) = 7824  
(...)           

filterbank format:

(...)
         Central freq (MHz) = 8337             
          Low channel (MHz) = 7826             
         High channel (MHz) = 8848    
(...)         

The filterbank file has the whole frequency range shifted by ~1024 MHz. Any clues? Thanks in advance!

SixByNine commented 9 years ago

Hi,

Two questions: 1) How up-to-date is your sigproc? I have recently fixed a bug with frequency channel ordering in psrfits data. It should be correct in the most recent version.

2) What does the sigproc header say about the file.

Mike

On 17 December 2014 at 05:36, matteobachetti notifications@github.com wrote:

Hi, I'm converting DFB data in search mode (from SRT) to filterbank format. I use simply filterbank filename.sf -o filename.fil. If I then print the file information with PRESTO's readfile I obtain the following:

(...) Central freq (MHz) = 7312 Low channel (MHz) = 6802 High channel (MHz) = 7824 (...)

filterbank format:

(...) Central freq (MHz) = 8337 Low channel (MHz) = 7826 High channel (MHz) = 8848 (...)

The filterbank file has the whole energy range shifted by ~1024 MHz. Any clues? Thanks in advance!

— Reply to this email directly or view it on GitHub https://github.com/SixByNine/sigproc/issues/1.

matteobachetti commented 9 years ago

Hi Mike, looking at timestamps, I was convinced I had the most recent version. But apparently, it was not the case (or maybe I had updated the repo but not recompiled). Thanks for suggesting the obvious :), in the last version the error is fixed. Cheers, Matteo

SixByNine commented 9 years ago

Glad it is solved. I recently worked carefully to make the frequencies correct.

On 17 December 2014 at 22:24, matteobachetti notifications@github.com wrote:

Closed #1 https://github.com/SixByNine/sigproc/issues/1.

— Reply to this email directly or view it on GitHub https://github.com/SixByNine/sigproc/issues/1#event-209256211.