You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@betacygni I think we should force convolution to a common beam, or at least check that a single beam is a good approximation, before running statcont on data. But, also, this suggests the need to refactor statcont to use spectral-cube for IO.
Yes, I agree.
Use the tools in astropy Varying_resolution_spectral_cube for IO, to
select good beams, mask_out_bad_beams, calculate average_beams, take it
as common beam, and convolve to it. if needed.
I have a varying beams spectral cube. The casa beams table has disappeared after cutout. None of the result images has a beam value.
Howto fix it please ?
How are beams handled ?
The text was updated successfully, but these errors were encountered: