Closed mhardcastle closed 3 months ago
Away from my laptop now, but I'm pretty sure it puts a single 0 in the weights field of the dict when there's no weight column.
There is a weight column, so not entirely sure what's going on, but I think the breakage wrt previous version may be related to this change in ClassVisServer.py:
if DATA["sort_index"] is not None: # and DATA["Weights"] is not 1: # OMS 2023/12 they're not "1" ever and this seems a bug
DATA["Weights"] = DATA["Weights"][DATA["sort_index"]]
OK, what's happening is that DATA["Weights"]==1 is used as a flag for 'don't use the weights' in GetVisWeights:
def GetVisWeights(self, iMS, iChunk):
"""
Returns path to weights array for the given MS and chunk number.
Waits for CalcWeights to complete (if running in background).
"""
# wmax-only means weights not computed (i.e. predict-only mode)
if self._ignore_vis_weights:
return 1
This change around line 597 therefore breaks existing functionality and I think should be reverted. Can I submit a PR?
Yes please! Sorry about the misguided change...
The continuing saga of upgrading ddf-pipeline to use the current saopicc releases of DDF and kMS.
runs for a while and then gives
DDF.py has run several times on these MSes in the course of the pipeline run, so it shouldn't be a problem with the data.
I'll investigate further but any ideas appreciated.