Menu

#28 Beam keywords are not saved in wideband MFS images

1.8
closed
None
2015-05-21
2015-01-15
No

Related to #20, reported by N. Hurley-Walker:

"I might still be seeing a bug in
the MFS fits header outputs though:

[nhw@mwadas2 1067875320]$ wsclean -version

WSClean version 1.5 (2014-12-16)
This software package is released under the GPL version 3.
Author: André Offringa (offringa@gmail.com).

and running a clean with the new -fitbeam option...

But there is no BMAJ, BMIN, BPA in the MFS fitsimage header, only in the
individual subchannels.

See /data/das2/nhw/fitbeam_test/1067875320 for the example files, and the
wsclean command in wsclean.sh."

Related

Tickets: #20

Discussion

  • André Offringa

    André Offringa - 2015-01-15
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,4 +1,4 @@
    -Related to #20 , reported by N. Hurley-Walker:
    +Related to [#20](tickets:#20), reported by N. Hurley-Walker:
    
     "I might still be seeing a bug in
     the MFS fits header outputs though:
    
     
  • André Offringa

    André Offringa - 2015-01-15

    Another comment by Natasha:
    "even with the -fitbeam parameter, the different channels still have
    the same BMAJ, BMIN, BPA in their headers. Is that not right? I just
    assumed they were restored with the same beam (like in the old-style
    -nofitbeam option). In which case the MFS image should just use the same
    beam again. Presumably this is causing a little loss in resolution at all
    but the lowest frequencies that are imaged."

     
  • André Offringa

    André Offringa - 2015-01-15
     
  • André Offringa

    André Offringa - 2015-02-20
    • Milestone: 1.6 --> 1.7
     
  • André Offringa

    André Offringa - 2015-03-10
    • Milestone: 1.7 --> 1.8
     
  • André Offringa

    André Offringa - 2015-05-21
    • status: open --> closed
     
  • André Offringa

    André Offringa - 2015-05-21

    While not yet solved, I close this since the beam parameters are deliberately not written to the MFS image -- Ticket #42 reports the right way to fix this.

     

    Related

    Tickets: #42

MongoDB Logo MongoDB