Execution Block ID uid://A001/X15a0/X14e Sgr_A_st_ad_03_TM1

keflavich commented 2 years ago

Sgr_A_st_ad_03_TM1 uid://A001/X15a0/X14e

[x] Observations completed?
[x] Delivered?
[x] Downloaded? (specify where)
- [x] hipergator
- [x] hipergator pipeline run
- Pipeline Run 20240301T145111
- Pipeline Run 20240301T151917
- Pipeline Run 20240302T050402
- Pipeline Run 20220322T131506
- Pipeline Run 20220309T004431
- Pipeline Run 20220309T001438
- [x] UConn
[x] Weblog unpacked
[x] Weblog Quality Assessment?
[x] Imaging: Continuum
- Ash - Weblog looks good - not too much structure
[x] Imaging: Lines
- [ ] HCO+
- Ash - emission left
- [ ] HNCO
- Ash - emission left
- [ ] H13CN
- Ash - looks okay, can we do science here? SiO masers detected
- [ ] H13CO+/SiO
- Ash - looks okay, can we science already?
- [ ] Cont 1
- Ash - hard to tell in weblogs
- [ ] Cont 2
- Ash - hard to tell in weblogs

Summary 18th May [Ash] - All cubes look okay, but need rechecking after full clean.

Product Links:

Reprocessed Product Links:

keflavich commented 2 years ago

The data products were 'size-mitigated'. Therefore, the delivered products should not be used for final science.

Not much going on in continuum, just one point source?

Lots of action in lines. One notable feature that is problematic from the "size-mitigated" data is noise dips: this is a possible indication that the rebinning was not done in a way that preserves uniform noise; those channels with dips are the average of n+1 channels, while the others are averages of n channels

keflavich commented 2 years ago

The download only partially completed; downloads are going at ~15 GB/hr (4 MB/s) from ESO and giving proxy errors (???) from NRAO.

ashleythomasbarnes commented 2 years ago

31. Find Continuum

Some channels could be included in continuum of broadband
HCO+ running up against the band edge - may just be okay

d-l-walker commented 2 years ago

Quick look at some of the cubes ...

Multiple point-like, narrow (< 5 km/s) sources in SPW 25 ... masers? The brightest of these occur ~ channels 588, 595 and 606. Some quick and dirty screenshots to show this below.

SPW 25 channel 588

Screenshot 2022-02-09 at 11 50 15 Screenshot 2022-02-09 at 11 57 06

SPW 25 channel 595

Screenshot 2022-02-09 at 13 09 28 Screenshot 2022-02-09 at 13 10 36

SPW 25 channel 606

Screenshot 2022-02-09 at 13 15 51 Screenshot 2022-02-09 at 13 16 11

ashleythomasbarnes commented 2 years ago

Nice @d-l-walker - I think this last one is towards the continuum core? This also has an associated 24micron point source (no 70micron/8micron though - at least from my quick check).

d-l-walker commented 2 years ago

Yeah I actually wrote that it was coincident with the lone continuum source, but I deleted that comment because it's a bit further away than I realised. It's still close, but not exactly coincident ... ~ 0.5 pc away. Screenshot 2022-02-09 at 13 35 59

keflavich commented 2 years ago

I believe these are SiO stellar masers

ashleythomasbarnes commented 2 years ago

36. Clean results for Sgr_A_star (TARGET) SpW 25,27,29,31,33,35

Looks good - well cleaned - easy as not much structure

38. Clean results for Sgr_A_star (TARGET) SpW

Downsampled by a factor of 2 in spectral resolution
spw 25 and 27 cleans look pretty good - residual empty
spw 29 and 31 emission present in residual
spw 33 and 35 difficult to see in weblog

keflavich commented 2 years ago

spw 29 has some severe issues that I'm not sure how to diagnose - it looks like a steep continuum has been subtracted? This can't happen under normal circumstances, afaik. Not sure if this is a clean issue or something in the visibilities.

ashleythomasbarnes commented 2 years ago

Strange, is this present in the other spw at this position? I think the continuum is fit over all spws.

keflavich commented 2 years ago

No, only the narrow window. I think it's actually coming from uvcontsub, and the issue is that there's a ton of structure

d-l-walker commented 2 years ago

I've encountered this issue before with contsub in CASA, though in that case it was for a very line rich window (cloud C). I got round this by using statcont instead ...

keflavich commented 2 years ago

Yeah, we need to examine this window more closely - possibly image it w/o contsub & do statcont after. That's worked well for ALMA-IMF

thusharags commented 2 years ago

findcont for spw29 (37~41) too close to a broad peak and the brightest feature close to the band edge: Integrated spectra within clean mask not flat (consistent with above comments): But not so obvious as an issue in moment 8 line-free map for spw29. Are there other ways to diagnose without downloading the clean cubes?

xinglunju commented 2 years ago

2. hifa_flagdata One flagging argument in 'Template Files':

mode='manual' spw='29:89.19\~89.198GHz;89.2\~89.203GHz' field='J1744-3116' reason='QA2:applycal_amplitude_frequency'

This is to flag the HCO+ absorption feature in spw29 in the phase calibrator. Maybe worth paying attention to for other SBs.

38. hif_makeimages (cubes) Spw 29 cubes likely have baseline fitting issues as noted by others.

The beam size is ~2'' x 1.2''. The major axis is ~30% higher than what we requested (1.5''). 1.5'' means ~0.05 pc resolution, while 2'' means 0.08 pc and almost 0.1 pc. Should we try re-imaging the data with a smaller robust number or are we ok with this?

keflavich commented 2 years ago

Aggregate continuum beam is 1.73 x 1.02 arcsec, which is still not good enough

snlongmore commented 2 years ago

Following discussion at WP1 meeting, with an aimed resolution of 1.5", 20% (the formal tolerance) is 0.3", so the upper limit on formally acceptable resolution is 1.8".

snlongmore commented 2 years ago

I believe these are SiO stellar masers

Is it worth pinging the BAaDE team (e.g. https://ui.adsabs.harvard.edu/abs/2018ApJ...861...75T/abstract) about these to see if they are interested?

keflavich commented 2 years ago

@snlongmore I think we already have members of the team involved? It might be a nice student project to catalog the SiO masers and cross-match them with AGB stars, but that's probably not super high priority.

xinglunju commented 2 years ago

It may be interesting to cross-match them with known water masers, so as to exclude AGB stars and have a better (but still very likely contaminated) sample of star forming cores traced by water masers.

keflavich commented 2 years ago

If any of these SiO masers are associated with star formation, we should write them up as individual papers - there are only <10 SiO masers known associated with star formation (http://keflavich.github.io/blog/high-mass-protostellar-sio-masers.html). The first order search can just be a check of whether the SiO maser is associated with ALMA continuum and/or molecular gas. I'd be surprised if there turn out to be any, but it would be really cool if there were!

xinglunju commented 2 years ago

Agreed! We should keep eyes on potential SiO v=1 masers toward cores... (on a related note, ALMA just tested the new GPU spectrometer on the TP array using this maser line in Orion: https://www.almaobservatory.org/en/announcements/first-light-with-the-new-spectrometer-for-the-atacama-compact-array/)

thusharags commented 2 years ago

Comments on the reprocessed data: Continuum image looks good (one single point source, no artefacts) I checked the problematic spw29 cube and does not show the slopes we saw in the previous iteration

keflavich commented 2 years ago

Could one or more of the assignees (@thusharags @abulatek @xinglunju @ashleythomasbarnes @d-l-walker) check the reimaged data?

d-l-walker commented 2 years ago

@keflavich I'll take a look

d-l-walker commented 2 years ago

@keflavich I checked the reprocessed continuum & all SPWs -- everything looks good. However, the cubes need to be re-cleaned at native spectral resolution still. I have a backlog of SBs for which I need to upload the channel parameters to the .json file for re-cleaning at the native resolution, so I'll add this to the list. I plan on going through them all tomorrow.

keflavich commented 2 years ago

The un-size-mitigated parameters are only present for spw33, but it looks like they're needed for other windows too: https://github.com/ACES-CMZ/reduction_ACES/blob/main/aces/pipeline_scripts/override_tclean_commands.json#L211-L220

$ gethead NAXIS3 *.cube.I.iter1.image.pbcor.fits
uid___A001_X15a0_X14e.s38_0.Sgr_A_star_sci.spw29.cube.I.iter1.image.pbcor.fits 957
uid___A001_X15a0_X14e.s38_0.Sgr_A_star_sci.spw31.cube.I.iter1.image.pbcor.fits 957
uid___A001_X15a0_X14e.s38_0.Sgr_A_star_sci.spw33.cube.I.iter1.image.pbcor.fits 1917
uid___A001_X15a0_X14e.s38_0.Sgr_A_star_sci.spw35.cube.I.iter1.image.pbcor.fits 1917
uid___A001_X15a0_X14e.s4_0.Sgr_A_star_sci.spw25.cube.I.iter1.image.pbcor.fits  1916
uid___A001_X15a0_X14e.s4_0.Sgr_A_star_sci.spw27.cube.I.iter1.image.pbcor.fits  1916
uid___A001_X15a0_X14e.s4_0.Sgr_A_star_sci.spw29.cube.I.iter1.image.pbcor.fits  1916

d-l-walker commented 2 years ago

@keflavich I forgot to leave a note on this issue earlier sorry, but the cleaning parameters for this were updated in #289, so this will need to be executed again to re-image at full spectral resolution.

keflavich commented 2 years ago

I moved the old files into lores_Nov1_2022/ so a new clean should be triggered soon

d-l-walker commented 1 year ago

All SPWs have successfully been reimaged at native spectral resolution, and look good. Setting this one as done.

keflavich commented 1 year ago

spw33 reimaging has a couple issues:

Bad beam: the beam in the header is reported to be 5x1", which does not match the PSF
The image wasn't cleaned. The model is all zero everywhere.

Need to investigate & redo.

keflavich commented 1 year ago

removed files, triggered reimaging. Cut off two channels on either end. Let's hope the model gets populated this time

keflavich commented 1 year ago

spw33 looks good now, BUT channels 0-128 have an elongated beam

keflavich commented 9 months ago

I'm trying to reimage the low-frequency continuum here, and it's failing with no error message:

2024-02-26 13:39:15     SEVERE  MeasTable::dUTC(Double) (file casacore/measures/Measures/MeasTable.cc, line 4290)       Leap second table TAI_UTC seems out-of-date.
2024-02-26 13:39:15     SEVERE  MeasTable::dUTC(Double) (file casacore/measures/Measures/MeasTable.cc, line 4290)+      Until the table is updated (see the CASA documentation or your system admin),
2024-02-26 13:39:15     SEVERE  MeasTable::dUTC(Double) (file casacore/measures/Measures/MeasTable.cc, line 4290)+      times and coordinates derived from UTC could be wrong by 1s or more.

Segmentation fault (core dumped)

Maybe this is corrupt data? It produced no output.

EDIT: well, it produced this:

total 190M
-rw------- 1 adamginsburg adamginsburg 207M Feb 26 08:45 core.python3-11-1708955127-3663-3389-c30b-s7.ufhpc.1874840
-rw-r--r-- 1 adamginsburg adamginsburg  11K Feb 26 08:39 tclean.pre
drwxr-xr-x 2 adamginsburg adamginsburg 4.0K Feb 26 08:39 TempLattice1874840_135

keflavich commented 9 months ago

Failure happens after this in the log:


2024-02-26 13:39:13     INFO    tclean_script::tclean_script::casa      tclean parameters: {'vis': ['/blue/adamginsburg/adamginsburg/ACES/workdir/ad_aggregate_low_mfs_TM1_A001_X15a0_X14e/uid___A002_Xf49cca_Xde0f_target.ms'], 'selectdata': True, 'field': 'Sgr_A_star', 'spw': ['25:85.96496364629436~85.9656960143156GHz;85.96691662768433~86.02672668275154GHz;86.02770317344653~86.04308290189239GHz;86.04405939258737~86.07457472680534GHz;86.0755512175003~86.08800147386124GHz;86.0894662099037~86.09532515407356GHz;86.09630164476853~86.10484593834957GHz;86.10582242904454~86.10753128776075GHz;86.10850777845572~86.12803759235523GHz;86.1290140830502~86.14439381149606GHz;86.14537030219104~86.19004475148616GHz;86.19126536485487~86.19712430902472GHz;86.1981007997197~86.21982771768289GHz;86.22104833105162~86.24253112634106GHz;86.24350761703603~86.25058717457462GHz;86.25302840131205~86.25424901468077GHz;86.25620199607073~86.25839910013441GHz;86.26206094024056~86.26328155360929GHz;86.26425804430427~86.26547865767299GHz;86.26645514836795~86.27402295125401GHz;86.27499944194899~86.29428513317475GHz;86.29526162386973~86.30820012557814GHz;86.30942073894687~86.31161784301057GHz;86.31259433370553~86.31381494707426GHz;86.31479143776924~86.32089450461284GHz;86.3218709953078~86.3536069428945GHz;86.35458343358947~86.35678053765317GHz;86.35775702834813~86.35873351904311GHz;86.3597100097381~86.36215123647553GHz;86.36312772717051~86.36556895390794GHz;86.36727781262415~86.37240438877278GHz;86.37338087946773~86.37557798353144GHz;86.37655447422642~86.38534289048118GHz;86.38631938117616~86.38778411721863GHz;86.38998122128233~86.39632841079965GHz;86.39730490149464~86.40047849625331GHz;86.40145498694828~86.40633744042316GHz;86.40731393111813~86.41146401657177GHz;86.41317287528798~86.41805532876286GHz;86.41903181945784~86.42440251828019GHz;86.42537900897517~86.43148207581876GHz,27:86.6649149962916~86.67223867800442GHz;86.67321516889947~86.67590051886086GHz;86.67687700975588~86.67736525520341GHz;86.67834174609845~86.67956235971727GHz;86.68053885061231~86.68835077777265GHz;86.6893272686677~86.69274498680035GHz;86.6937214776954~86.70665998205473GHz;86.70861296384483~86.71569252283389GHz;86.71666901372893~86.72838690446946GHz;86.72960751808827~86.73156049987836GHz;86.73278111349717~86.74254602244761GHz;86.74352251334264~86.74401075879017GHz;86.74498724968522~86.75939049038712GHz;86.76036698128216~86.7620758403485GHz;86.76305233124353~86.77403785381279GHz;86.77501434470783~86.77940855373552GHz;86.78062916735433~86.7933235489899GHz;86.79430003988494~86.80675029879674GHz;86.80870328058684~86.82261827584122GHz;86.8245712576313~86.82579187125012GHz;86.82701248486892~86.82750073031644GHz;86.82920958938277~86.83238318479167GHz;86.83335967568671~86.84068335739954GHz;86.84336870736091~86.84678642549356GHz;86.8477629163886~86.85264537086383GHz;86.85533072082521~86.85923668440537GHz;86.86265440253803~86.86363089343308GHz;86.86460738432812~86.92270859258323GHz;86.92368508347829~86.92466157437333GHz;86.92563806526837~86.93296174698119GHz;86.93393823787623~86.97226550550673GHz;86.97324199640175~86.98105392356211GHz;86.98203041445716~86.99594540971154GHz;86.99692190060658~86.99960725056795GHz;87.00058374146299~87.01156926403225GHz;87.01278987765106~87.01791645485002GHz;87.01889294574508~87.02255478660149GHz;87.02353127749653~87.08675906295063GHz;87.08797967656945~87.09432686738724GHz;87.09554748100604~87.1314335213989GHz'], 'timerange': '', 'uvrange': '', 'antenna': ['0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44&'], 'scan': ['7,10,13,16,19'], 'observation': '', 'intent': 'OBSERVE_TARGET#ON_SOURCE', 'datacolumn': 'data', 'imagename': 'uid___A001_X15a0_X14e.s36_0.Sgr_A_star_sci.spw25_27.cont.I.iter1', 'imsize': [2700, 1296], 'cell': ['0.2arcsec'], 'phasecenter': 'ICRS 17:45:02.4619 -029.30.22.130', 'stokes': 'I', 'projection': 'SIN', 'startmodel': '', 'specmode': 'mfs', 'reffreq': '', 'nchan': -1, 'start': '', 'width': '', 'outframe': 'LSRK', 'veltype': 'radio', 'restfreq': [], 'interpolation': 'linear', 'perchanweightdensity': False, 'gridder': 'mosaic', 'facets': 1, 'psfphasecenter': '', 'wprojplanes': 1, 'vptable': '', 'mosweight': True, 'aterm': True, 'psterm': False, 'wbawp': True, 'conjbeams': False, 'cfcache': '', 'usepointing': False, 'computepastep': 360.0, 'rotatepastep': 360.0, 'pointingoffsetsigdev': [], 'pblimit': 0.2, 'normtype': 'flatnoise', 'deconvolver': 'mtmfs', 'scales': [], 'nterms': 2, 'smallscalebias': 0.0, 'restoration': True, 'restoringbeam': 'common', 'pbcor': True, 'outlierfile': '', 'weighting': 'briggs', 'robust': 1.0, 'noise': '1.0Jy', 'npixels': 0, 'uvtaper': [''], 'niter': 40000000, 'gain': 0.1, 'threshold': '0.000218Jy', 'nsigma': 0.0, 'cycleniter': -1, 'cyclefactor': 1.0, 'minpsffraction': 0.05, 'maxpsffraction': 0.8, 'usemask': 'pb', 'mask': '', 'pbmask': 0.0, 'sidelobethreshold': 2.0, 'noisethreshold': 5.0, 'lownoisethreshold': 1.5, 'negativethreshold': 0.0, 'smoothfactor': 1.0, 'minbeamfrac': 0.3, 'cutthreshold': 0.01, 'growiterations': 75, 'dogrowprune': True, 'minpercentchange': 1.0, 'verbose': False, 'fastnoise': False, 'restart': True, 'savemodel': 'none', 'psfcutoff': 0.35, 'parallel': False}
2024-02-26 13:39:13     INFO    tclean_script::tclean_script::casa      calcpsf: True
2024-02-26 13:39:13     INFO    ::casa  Verifying Input Parameters
2024-02-26 13:39:14     INFO    SynthesisImagerVi2::selectData  MS : /blue/adamginsburg/adamginsburg/ACES/workdir/ad_aggregate_low_mfs_TM1_A001_X15a0_X14e/uid___A002_Xf49cca_Xde0f_target.ms | Selecting on fields : Sgr_A_star | Selecting on spw :25:85.96496364629436~85.9656960143156GHz;85.96691662768433~86.02672668275154GHz;86.02770317344653~86.04308290189239GHz;86.04405939258737~86.07457472680534GHz;86.0755512175003~86.08800147386124GHz;86.0894662099037~86.09532515407356GHz;86.09630164476853~86.10484593834957GHz;86.10582242904454~86.10753128776075GHz;86.10850777845572~86.12803759235523GHz;86.1290140830502~86.14439381149606GHz;86.14537030219104~86.19004475148616GHz;86.19126536485487~86.19712430902472GHz;86.1981007997197~86.21982771768289GHz;86.22104833105162~86.24253112634106GHz;86.24350761703603~86.25058717457462GHz;86.25302840131205~86.25424901468077GHz;86.25620199607073~86.25839910013441GHz;86.26206094024056~86.26328155360929GHz;86.26425804430427~86.26547865767299GHz;86.26645514836795~86.27402295125401GHz;86.27499944194899~86.29428513317475GHz;86.29526162386973~86.30820012557814GHz;86.30942073894687~86.31161784301057GHz;86.31259433370553~86.31381494707426GHz;86.31479143776924~86.32089450461284GHz;86.3218709953078~86.3536069428945GHz;86.35458343358947~86.35678053765317GHz;86.35775702834813~86.35873351904311GHz;86.3597100097381~86.36215123647553GHz;86.36312772717051~86.36556895390794GHz;86.36727781262415~86.37240438877278GHz;86.37338087946773~86.37557798353144GHz;86.37655447422642~86.38534289048118GHz;86.38631938117616~86.38778411721863GHz;86.38998122128233~86.39632841079965GHz;86.39730490149464~86.40047849625331GHz;86.40145498694828~86.40633744042316GHz;86.40731393111813~86.41146401657177GHz;86.41317287528798~86.41805532876286GHz;86.41903181945784~86.42440251828019GHz;86.42537900897517~86.43148207581876GHz,27:86.6649149962916~86.67223867800442GHz;86.67321516889947~86.67590051886086GHz;86.67687700975588~86.67736525520341GHz;86.67834174609845~86.67956235971727GHz;86.68053885061231~86.68835077777265GHz;86.6893272686677~86.69274498680035GHz;86.6937214776954~86.70665998205473GHz;86.70861296384483~86.71569252283389GHz;86.71666901372893~86.72838690446946GHz;86.72960751808827~86.73156049987836GHz;86.73278111349717~86.74254602244761GHz;86.74352251334264~86.74401075879017GHz;86.74498724968522~86.75939049038712GHz;86.76036698128216~86.7620758403485GHz;86.76305233124353~86.77403785381279GHz;86.77501434470783~86.77940855373552GHz;86.78062916735433~86.7933235489899GHz;86.79430003988494~86.80675029879674GHz;86.80870328058684~86.82261827584122GHz;86.8245712576313~86.82579187125012GHz;86.82701248486892~86.82750073031644GHz;86.82920958938277~86.83238318479167GHz;86.83335967568671~86.84068335739954GHz;86.84336870736091~86.84678642549356GHz;86.8477629163886~86.85264537086383GHz;86.85533072082521~86.85923668440537GHz;86.86265440253803~86.86363089343308GHz;86.86460738432812~86.92270859258323GHz;86.92368508347829~86.92466157437333GHz;86.92563806526837~86.93296174698119GHz;86.93393823787623~86.97226550550673GHz;86.97324199640175~86.98105392356211GHz;86.98203041445716~86.99594540971154GHz;86.99692190060658~86.99960725056795GHz;87.00058374146299~87.01156926403225GHz;87.01278987765106~87.01791645485002GHz;87.01889294574508~87.02255478660149GHz;87.02353127749653~87.08675906295063GHz;87.08797967656945~87.09432686738724GHz;87.09554748100604~87.1314335213989GHz | Selecting on antenna names : 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44& | Selecting on scan : 7,10,13,16,19 | Selecting on Scan Intent/State : OBSERVE_TARGET#ON_SOURCE | [Opened in readonly mode]
2024-02-26 13:39:15     INFO    SynthesisImagerVi2::selectData    NRows selected : 966240
2024-02-26 13:39:15     SEVERE  MeasTable::dUTC(Double) (file casacore/measures/Measures/MeasTable.cc, line 4290)       Leap second table TAI_UTC seems out-of-date.
2024-02-26 13:39:15     SEVERE  MeasTable::dUTC(Double) (file casacore/measures/Measures/MeasTable.cc, line 4290)+      Until the table is updated (see the CASA documentation or your system admin),
2024-02-26 13:39:15     SEVERE  MeasTable::dUTC(Double) (file casacore/measures/Measures/MeasTable.cc, line 4290)+      times and coordinates derived from UTC could be wrong by 1s or more.
2024-02-26 13:39:20     INFO    SynthesisImagerVi2::defineImage         Define image coordinates for [uid___A001_X15a0_X14e.s36_0.Sgr_A_star_sci.spw25_27.cont.I.iter1] :
2024-02-26 13:39:20     INFO    SynthesisImagerVi2::defineImage         Impars : start
2024-02-26 13:39:20     INFO    SynthesisImagerVi2::defineImage         Shape : [2700, 1296, 1, 1]Spectral : [8.68957e+10] at [0] with increment [4.60193e+08]
2024-02-26 13:39:20     INFO    SynthesisImagerVi2::defineImage         Set Gridding options for [uid___A001_X15a0_X14e.s36_0.Sgr_A_star_sci.spw25_27.cont.I.iter1] with ftmachine : mosaicft
2024-02-26 13:39:20     INFO    SynthesisImager::getVPRecord    Using default Voltage Patterns from the VPManager
2024-02-26 13:39:20     INFO    VPSkyJones::VPSkyJones  PB used ALMA
2024-02-26 13:39:21     INFO    SynthesisImagerVi2::nSubCubeFitInMemory Required memory: 0.2897 GB. Available mem.: 12.76 GB (rc, mem. fraction: 20%, memory: -) => Subcubes: 1. Processes on node: 1.
2024-02-26 13:39:21     INFO    SynthesisImagerVi2::weight()    Set imaging weights : Briggs weighting: sidelobes will be suppressed over full image

keflavich commented 9 months ago

I attempted to re-split the data

split('uid___A002_Xf49cca_Xde0f.ms', outputvis='uid___A002_Xf49cca_Xde0f_target.ms', field='Sgr_A_star')

and ended up with exactly the same error, so it looks like the problem exists in the original .ms.

I'm going to try re-running the ALMA pipeline from scratch. I'll preserve all the data, but let's see if a fresh run makes for better measurement sets...

keflavich commented 8 months ago

Rerun looks to have completed, but I had to rename the _targets.ms file to target.ms:

ln -s /orange/adamginsburg/ACES//data//2021.1.00172.L/science_goal.uid___A001_X1590_X30a8/group.uid___A001_X1590_X30a9/member.uid___A001_X15a0_X14e/calibrated/working/uid
rg/ACES//data//2021.1.00172.L/science_goal.uid___A001_X1590_X30a8/group.uid___A001_X1590_X30a9/member.uid___A001_X15a0_X14e/calibrated/working/uid___A002_Xf49cca_Xde0f_target.ms

keflavich commented 8 months ago

The cubes seem to have completed successfully (statcont cubes exist)

djeff1887 commented 6 months ago

(upper 25_27, lower 33_35) Looks pretty good on both counts. 25_27 was missing last time, so there's no comparison set, but 33_35 looks good. There looks to still be a bit of contamination in 33_35, but it's not bad.

d-l-walker commented 3 months ago

Just reviving the discussion re: SPW 33 having a weirdly large and elongated beam. This issue is not present in the products delivered by ALMA. The screenshot below shows the delivered cube on the left, and the re-imaged cube on the right. Clearly something has gone wrong.

I'm not really sure what's causing this, so I'm initially just going to create a dirty cube locally to see if I can reproduce this issue, then take it from there.

Screenshot 2024-08-27 at 16 53 04

d-l-walker commented 3 months ago

Beam in dirty image for SPW 33 looks fine. I used the same parameters as the ALMA PL, only adjusting the number of channels and channel width to undo size mitigation. No need to trim any channels.

@keflavich I'm not sure what's going on with the cleaning on your end. Do you want me to push these cleaning parameters as overrides and re-run on your end? In the meantime, I'm going to re-run using the exact parameters that you used to see if that changes anything.

Screenshot 2024-08-28 at 13 02 12

keflavich commented 3 months ago

Yes, please do that.

d-l-walker commented 3 months ago

The SPW 35 cube was previously broken for this SB (see below). I think this was just in need of a re-run, but I'm not sure whether this was done in the end.

@keflavich can you please check the uid___A001_X15a0_X14e.s38_0.Sgr_A_star_sci.spw35.cube.I.iter1.image.pbcor.fits image to see whether it looks OK (i.e. not like the image below). Just to save me downloading a 54 GB cube that may or may not be broken.

If all looks good, I'll grab it and re-do the feathering.

Screenshot 2024-08-28 at 13 25 43

keflavich commented 3 months ago

Yeah, everything looks fine in the calibrated/working directory

d-l-walker commented 3 months ago

Update from WP1 meeting: both cubes for SPW 33 & 35 now look good on HPG. I'll download the new cubes and re-do the feathering.

ACES-CMZ / reduction_ACES