Remove extra_params altogether from Core. This puts all formulas on an equal footing and simplifies simulation and data storage code.
Migration notes
For almost all users, no migration is needed.
You may be impacted only if you were computing (for instance in a notebook) one of the two variables from France that used this non-standard extension to the `calculate(variable, period)` API: `rsa_fictif` or `ppa_fictive`. In that case you had to supply the additional parameter `mois_demande`. Use `rsa` or `ppa` directly, and go back to the standard API.
27.0.2
> Note: Versions `27.0.0` and `27.0.1` have been unpublished as the former accidentally introduced a bug affecting test inputs. Please use version `27.0.2` or more recent.
- Fix a bug introduced in 27.0.0, affecting YAML tests; because of an incorrect date comparison, input variables would be ignored if they had an end date.
27.0.1
Technical changes
- Provide three levels of information when running tests depending on context: - when running `pytest`, all failures are reported, coverage is omitted - when running `make test`, all failures are reported, with coverage also reported - in continuous integration, exit on first failure, but report coverage always
27.0.0
Breaking changes
- No longer honor calls to `set_input` for variables which have an end date and for periods after that date.
Migration guide
This change is not expected to actually break much reusing code (if any), as it is unlikely that one would deliberately specify an end date for a variable and use it in computations for periods past that date. However, nothing has previously ruled out relying on that behaviour and it may have been introduced by accident. In particular, it can happen that a variable with a formula and an end date is also, in some applications, used as an input.
26.2.0
- Introduce a way to build a simulation for tabular inputs
New features
- Allow to create a simulation step by step: 1. Create entities with `SimulationBuilder.create_entities(...)` 2. Declare your population with `SimulationBuilder.declare_person_entity(...)` and `SimulationBuilder.declare_entity(...)` 3. Link between persons in population definition with `SimulationBuilder.join_with_persons(...)` 4. Build a simulation with `SimulationBuilder.build(...)` 5. Set variable values with the already existing `Simulation.set_input(...)` method
26.1.0
- No longer raise an error when a group entity is not specified in a test case, or partially specified. - Instead, each person is by default allocated to a group of which they are the sole member, with the default role in that group.