Is your feature request related to a problem? Please describe.
When creating new components, the corresponding script from common gets called without any task-specific parameters
https://github.com/openproblems-bio/task_batch_integration/tree/main/scripts/create_component
However, there are crucial parameters should would be missed for users adding new methods or metrics.
Describe the solution you'd like
A way to set up default info parameters (or prompting the user) so that important parameters are instantiated from the beginning
e.g. parameters from combat
|
info: |
|
method_types: [feature] |
|
preferred_normalization: log_cp10k |
|
variants: |
|
combat_full_unscaled: |
|
combat_full_scaled: |
|
preferred_normalization: log_cp10k_scaled |
most often, method_types is missing and the use of variants remains unknown
Is your feature request related to a problem? Please describe.
When creating new components, the corresponding script from
commongets called without any task-specific parametershttps://github.com/openproblems-bio/task_batch_integration/tree/main/scripts/create_component
However, there are crucial parameters should would be missed for users adding new methods or metrics.
Describe the solution you'd like
A way to set up default info parameters (or prompting the user) so that important parameters are instantiated from the beginning
e.g. parameters from combat
task_batch_integration/src/methods/combat/config.vsh.yaml
Lines 18 to 24 in 4e9ebb6
most often,
method_typesis missing and the use ofvariantsremains unknown