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
Original comment by Pascal Lesage (Bitbucket: MPa, ).
This assumes that the array is stored in the amount field. This makes it impossible to store both the deterministic value and a sampled array. Perhaps the Numpy array needs to be stored in a new field, but then we'd have to make sure that these sampled arrays can be passed to the Interpreter.
Sure; we currently assume that a variable can only have a single numeric value, but for computational efficiency it would be nice if they could have an array of values so that we would only need to evaluate the string formulas once to get e.g. 1000 results. But this is a bit tricky, you need a convention to make sure the numpy arrays broadcast correctly, and write the formulas so that they can accept numpy arrays with leading to everything being NaN if there is an error with one value in the whole array (e.g. if you would normalize by the sum or average).
Original report by Chris Mutel (Bitbucket: cmutel, GitHub: cmutel).
Don't only validate against Number
The text was updated successfully, but these errors were encountered: