-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Difficulty passing multiple tuple arguments via stimela cab interface #327
Comments
Ah I see the problem. Try I'm a little puzzled/bothered that the error message looks so ugly for you. When I tried a reproducer, I got a much neater error, which immediately made the problem apparent: |
Ah ok I get the "ugly" error when I try to doc your cab myself. So let's keep this issue open until I fix the error message. |
Missed that in the documentation, apologies. Perhaps this requires a new issue (I see there is issue #219 that perhaps points to it), but my script accepts a path for output products to be saved to. If the folder does not exist it is created. However, parameter validation by stimela complains about the path not existing and I don't see any policy or parameter option to stop validation checks. Should I omit this folder creation step in my script and let stimela do it (if it does)? |
Oh wait I see parameter That worked :D |
There's |
Will try that route, thanks. |
@talonmyburgh has this been solved, or is there still something for me to fix? |
This has been solved, thanks. |
The script I wrote for Dynamic Spectra Normalisation and Smoothing requires passing one or more smoothing kernel sizes to the script.
Below is an extract from inspect_dynspec.py which shows the
@click
interface I used to set this up:This allowed for kernels to be passed as
python inspect_dynspec.py <blah> --kernel '(3,4)' --kernel '(10,20)'
...To get similar behaviour via the stimela wrapper I wrote this cab. However input:
does not work and gives error:
I changed bracketing in the
default
key fromdefault: (1,1)
todefault: [1,1]
but this made no difference.This is using the latest stimela version available on
master
branch though I found the same issue onvenv-activation
that was merged into master a little while back.The text was updated successfully, but these errors were encountered: