You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It's not uncommon for modules to only accept "quantized" inputs, e.g. maybe your module uses finite-difference formulas and you've coded up the 1 and 3 point stencils. In this example the input which selects the stencil size is probably an integer, but it can only take on values of 1 and 3. With the current bounds checks there's no way to make sure the user only provided you one of those two values.
Describe the solution you'd like
Ultimately, I'd like an additional bounds check class which stores a list of approved values.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It's not uncommon for modules to only accept "quantized" inputs, e.g. maybe your module uses finite-difference formulas and you've coded up the 1 and 3 point stencils. In this example the input which selects the stencil size is probably an integer, but it can only take on values of 1 and 3. With the current bounds checks there's no way to make sure the user only provided you one of those two values.
Describe the solution you'd like
Ultimately, I'd like an additional bounds check class which stores a list of approved values.
The text was updated successfully, but these errors were encountered: