ERROR: No unit set on column; followed later by "ERROR facetselfcal_facet_patch_477: poly2sky failed"

[CDumba]

Could someone help me on how to fix the above error please.. NB:This is on the very first facet.

[Joshuaalbert]

What is you parset?

[CDumba]

using the default factor(v1.3) parset

[Joshuaalbert]

Did prefactor finish properly?

[CDumba]

That am not sure! Have to check with a colleague who did the model extraction with InitialSubtract. There were a few issues of which i dont know how he resolved them in the end. Do you suppose that the issue may have migrated from prefactor?

[Joshuaalbert]

I would guess that, but I would get confirmation from another. @darafferty perhaps

[adrabent]

@CDumba @Joshuaalbert

I did the initsubtract procedure. Indeed, there were some problems running the classical initsubtract, but it was just wsclean not finishing the imaging, so it was right before the data itself has been modified. I would exclude this problem as a source of error.

I was using the new version of initsubtract, maybe there are some buggy things included with that.

Cosmos, could you please post the entire error message?

[CDumba]

Every chunk reports this: 2017-09-11 22:05:47 WARNING facetselfcal_facet_patch_477.executable_args: ERROR: No unit set on column 2017-09-11 22:05:47 WARNING facetselfcal_facet_patch_477.executable_args: INFO: Total time 0.7187s; user time: 0.5296s; system time: 0.0914s 2017-09-11 22:05:47 WARNING facetselfcal_facet_patch_477.executable_args: DEBUG: Start time was 1505160347.2773s; end time was 1505160347.9961s 2017-09-11 22:05:47 DEBUG facetselfcal_facet_patch_477.executable_args: Results for job 23 submitted by ('127.0.0.1', 35871) 2017-09-11 22:05:47 ERROR node.transitix.python_plugin: No unit set on column 2017-09-11 22:05:47 INFO node.transitix.python_plugin: Total time 0.7187s; user time: 0.5296s; system time: 0.0914s 2017-09-11 22:05:47 DEBUG node.transitix.python_plugin: Start time was 1505160347.2773s; end time was 1505160347.9961s 2017-09-11 22:05:48 DEBUG facetselfcal_facet_patch_477.executable_args:

Then after the last chunk, these are the final lines:

2017-09-11 22:05:48 DEBUG facetselfcal_facet_patch_477.executable_args: compute.dispatch results job 23: job_duration: 1.16693305969, returncode: 1 2017-09-11 22:05:49 DEBUG facetselfcal_facet_patch_477.executable_args: Adding node_logging_information 2017-09-11 22:05:49 ERROR facetselfcal_facet_patch_477.executable_args: A job has failed with returncode 1 and error_tolerance is not set. Bailing out! 2017-09-11 22:05:49 WARNING facetselfcal_facet_patch_477.executable_args: Note: recipe outputs are not complete 2017-09-11 22:05:49 WARNING facetselfcal_facet_patch_477.executable_args: recipe executable_args completed with errors 2017-09-11 22:05:49 WARNING facetselfcal_facet_patch_477: poly2sky reports failure (using executable_args recipe) 2017-09-11 22:05:49 ERROR facetselfcal_facet_patch_477: 2017-09-11 22:05:49 ERROR facetselfcal_facet_patch_477: Failed pipeline run: facet_patch_477 2017-09-11 22:05:49 ERROR facetselfcal_facet_patch_477: Detailed exception information: 2017-09-11 22:05:49 ERROR facetselfcal_facet_patch_477: <class 'lofarpipe.support.lofarexceptions.PipelineRecipeFailed'> 2017-09-11 22:05:49 ERROR facetselfcal_facet_patch_477: poly2sky failed 2017-09-11 22:05:49 ERROR facetselfcal_facet_patch_477: 2017-09-11 22:05:49 ERROR facetselfcal_facet_patch_477: LOFAR Pipeline finished unsuccesfully. 2017-09-11 22:05:50 WARNING facetselfcal_facet_patch_477: recipe facetselfcal_facet_patch_477 completed with errors

[adrabent]

Problem is solved after updating to LSMTool 1.2.0.

Issue can be closed.

[darafferty]

Ah, good -- I should have realized it was something to do with that.