Skip to content

Return starting model and config file for delay calibration#101

Open
tikk3r wants to merge 6 commits intomasterfrom
return-delay-config
Open

Return starting model and config file for delay calibration#101
tikk3r wants to merge 6 commits intomasterfrom
return-delay-config

Conversation

@tikk3r
Copy link
Member

@tikk3r tikk3r commented Mar 9, 2026

I recently found myself in multiple scenarios where I needed to re-run or tweak the delay calibration on difficult fields. With settings and skymodels now being generated automatically, this is cumbersome at the moment as they are not outputs of the main workflow and as such do not "survive" a successful pipeline run. This PR adds the starting models as outputs of the pipeline as well as the config file that comes from phaseup-concat (the automatic selection does not yet generate config files, I'll leave that for a future PR). This should improve reproducibility in general as well by having easier access to the combination of model and settings that were used.

@tikk3r tikk3r requested a review from lonbar March 17, 2026 10:17
Copy link
Member

@lonbar lonbar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. A few minor syntax nits.

Comment on lines +142 to +146
outputSource:
- generate_skymodels/skymodel
type: File[]
pickValue: all_non_null
linkMerge: merge_flattened
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
outputSource:
- generate_skymodels/skymodel
type: File[]
pickValue: all_non_null
linkMerge: merge_flattened
outputSource: generate_skymodels/skymodel
type: File[]

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The source is a single array which is required so the pickValue and linkMerge aren't necessary.

Comment on lines +452 to +456
- id: facetselfcal_config
outputSource:
- phaseup/facetselfcal_config
type: File
pickValue: all_non_null
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- id: facetselfcal_config
outputSource:
- phaseup/facetselfcal_config
type: File
pickValue: all_non_null
- id: facetselfcal_config
outputSource: phaseup/facetselfcal_config
type: File

@lonbar
Copy link
Member

lonbar commented Mar 17, 2026

I'm wondering if it makes sense to bundle outputs such as these into a record or perhaps a JSON file. It seems more like metadata; the user is not interested in these output per se. It is definitely a good idea to store them, but bundling it up could perhaps simplify the outputs that we have in the workflows. What do you think?

@tikk3r
Copy link
Member Author

tikk3r commented Mar 25, 2026

I'm wondering if it makes sense to bundle outputs such as these into a record or perhaps a JSON file. It seems more like metadata; the user is not interested in these output per se. It is definitely a good idea to store them, but bundling it up could perhaps simplify the outputs that we have in the workflows. What do you think?

I'm not sure I fully understand. Do you mean in the sense of the contents of these files in a JSON file?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants