-
Notifications
You must be signed in to change notification settings - Fork 11
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
Set notated input parameters not being recognized #248
Comments
The config worked fine for me, creating a single job with the specified parameters. pyDeltaRCM_20220518-143617.log Can you confirm you are passing the yaml file to the high-level API? Either from the terminal as |
We are using the low level processor, so using
|
cool yeah, that is not supported, but I agree I jsut looked at the docs, and I agree it's totally not clear that you can't do that. I'll leave this open until I can update the docs. Thanks for pointing this out!! |
Going to re-open this issue as I got the below warning when using the high-level API and specifying
Understandably this is from the if-else clause in |
Hm, can you confirm you're on the latest version / the development version? I thought I fixed this by not writing the time variables out to the job yamls here. Can you write a test to reproduce the warning? |
actually #259 that I never finished was supposed to add the |
We've been using set notation but find that the model is not recognizing these. This may be an edge case as this is an unnecessary scenario where only 1 set of alternatives is provided, not multiple.
The input yaml:
The resulting log file:
The text was updated successfully, but these errors were encountered: