low-sky
commented
8 years ago The issue here is that a lot of the first look code is defined in terms of specific channel ranges rather than velocity ranges. Thus, in creating a new cube range, a lot of it breaks. However, there's now enough functionality in the baseline package to calculate windows on the fly given velocities. Thus, revisions should be pretty straight forward.
You can check out the results in images/NGC1333/ and hopefully it will work for you now.
All right. After much ado (and slow response-loop), I've made some improvements to the rebaselining code. The major improvement is the creation of
run_rebaseline.pyand the ability to do it after the gridding. I also found an error that was corrupting the estimates of the velocity centre in OrionA which made that region better. Plus lots of little bugs that are now better. I'll send an email about my view on the next analysis steps and the outcomes.