-
Notifications
You must be signed in to change notification settings - Fork 75
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
Document value inference mechanisms #458
Comments
I'm being told there's also something about “suggestions” — can @cbenz detail the current behaviour, in the same format as above? Any other known inference behaviours should be listed here. Please refrain from debating about them for the moment. |
There is also the |
From #460 (comment):
@benjello is this the same as the |
Yes it is, sorry for not using the right term |
Ok, it's been about 2 weeks that this reference issue was open. The time for collecting known inferences seems to be over. I updated the original post to include |
There are currently a few places where inferences take place:
fuzzy
attribute, which artificially extends the validity period of a value — Do not crash when asked for a parameter after end date #437.calculate_output
, which can automatically sum or divide values over periods to match the requested period.set_input
, which can automatically sum or divide input values over periods to match the computable period.base_function
, which can yield values that the original requested formula could not compute on its own — Make explicit input variables temporal inferences #460.max_nb_cycles
, which can block the computation toward the past and thus doesn't allow some values to be computed.We need to agree on a common, systematic way of doing inferences, to avoid conflicting views such as in #437 or in branch
extrapolate-intensive-variables-to-past
.The minimal output is a complete list of inferences and expected usage in the documentation, which could be based upon the above list.
The expected output is a set of helper functions, architectural changes and documentation that support a consistent way of inferring values in OpenFisca.
The text was updated successfully, but these errors were encountered: