Replies: 2 comments 5 replies
-
I was about to suggest the same thing! |
Beta Was this translation helpful? Give feedback.
1 reply
-
I should probably do the same for aliases. Where my recipe now says inputs:
...
aliases:
sol_k_tint: [selfcal.k_time_int, selfcal_res.k_time_int]
sol_k_fint: [selfcal.k_freq_int, selfcal_res.k_freq_int]
defaults:
sol_k_tint: 1
sol_k_fint: 1024 it could say inputs:
...
sol_k_tint:
aliases: [selfcal.k_time_int, selfcal_res.k_time_int]
default: 1
sol_k_fint:
aliases: [selfcal.k_freq_int, selfcal_res.k_freq_int]
default: 1024 |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Looking at this chunk of my recipe:
...I find myself slightly offended by the repetition. And yes, I remember that making a separate
defaults
section was my suggestion. And I still think this is a good idea to have all the defaults in one place when many inputs are involved.However, in the spirit of democracy and pluralistic ways of skinning felines, it occurs to me that we could have our cake and eat it. Reinstate an optional
default
keyword in the Parameter schema, and keep thedefaults
section at parent level. The outer defaults then override the internal defaults if provided. What do you think @SpheMakh?Beta Was this translation helpful? Give feedback.
All reactions