Closed rfriesen closed 7 years ago
What version of radio_beam
do you have? I don't think that's the issue, but I want to check.
I just checked, and it does not look right
In [1]: import pyspeckit
pyspeckit.__version__
In [2]: pyspeckit.__version__
Out[2]: u'0.1.20.dev'
In [3]: import radio_beam
In [4]: radio_beam.__version__
Out[4]: '0.0'
In [5]: radio_beam
Out[5]: <module 'radio_beam' from '/lustre/pipeline/scratch/GAS/python/anaconda/lib/python2.7/site-packages/radio_beam/__init__.pyc'>
OK, @rfriesen could you please check again? I removed an old version of radio beam
In [1]: import radio_beam
...: radio_beam.__version__
...:
Out[1]: u'0.0.dev173'
@keflavich is it possible to give a bump to the version number of radio beam? then we can put that as a requirement in GAS
, what do you think?
@jpinedaf yeah, that's a good idea. We need a new release. It's stable enough to deserve a v0.1 now.
@jpinedaf @keflavich Code is running now. I'll update when I see whether the beam info is kept in the moment maps. Thanks!
@jpinedaf regarding versions: https://github.com/radio-astro-tools/radio_beam/issues/44
Problem solved. Thanks everyone!
@keflavich @low-sky @jpinedaf came across an issue that some of the moment files for DR1 were missing beam info. I tried to rerun PropertyMaps.update_NH3_moment0 at Green Bank but get the below error when trying to read in the baselined cubes with pyspeckit. I did originally run this on my own machine (which died; am waiting for the replacement) and it appeared to run fine (albeit missing beam info?). The beam info is in the header of the input cubes. Looks like spectral-cube is where the issue lies. Checking my backup, I was using spectral-cube version 0.4.0 rather than 0.4.1.dev1308 on the GB machines.
Any ideas on how to fix?