owlplanner 2026.1.26__tar.gz → 2026.2.2__tar.gz

{owlplanner-2026.1.26 → owlplanner-2026.2.2}/INSTALL.md

@@ -2,7 +2,7 @@
 
 ## A retirement exploration tool based on linear programming
 
-<img align=right src="https://github.com/mdlacasse/Owl/blob/main/docs/images/owl.png?raw=true" width="250">
+<img align=right src="https://github.com/mdlacasse/Owl/blob/main/papers/images/owl.png?raw=true" width="250">
 
 ------------------------------------------------------------------------------------
 ### About

{owlplanner-2026.1.26 → owlplanner-2026.2.2}/PARAMETERS.md

@@ -107,7 +107,13 @@ Investment return rates and inflation assumptions.
 | `from` | integer | Starting year for historical data range (must be between 1928 and 2025) |
 | `to` | integer | Ending year for historical data range (must be between 1928 and 2025, and greater than `from`) |
 
-**Note:** `from`/`to` are stored for all methods in saved case files. Methods that do not use them ignore these fields.
+#### For `method = "historical"`, `"histochastic"`, or `"stochastic"` (varying rates only):
+| Parameter | Type | Description |
+|-----------|------|-------------|
+| `reverse_sequence` | boolean | If true, reverse the rate sequence along the time axis (e.g. last year first). Default is `false`. Ignored for fixed/constant rate methods. Used for both single-scenario and Historical Range runs. |
+| `roll_sequence` | integer | Number of years to roll (shift) the rate sequence; positive shifts toward the end, values wrap. Default is `0`. Ignored for fixed/constant rate methods. Used for both single-scenario and Historical Range runs. |
+
+**Note:** `from`/`to` are stored for all methods in saved case files. Methods that do not use them ignore these fields. When running Historical Range, each year in the range uses the historical rate sequence starting at that year, with `reverse_sequence` and `roll_sequence` applied to each sequence.
 
 ---
 
@@ -172,8 +178,8 @@ Options controlling the optimization solver and constraints.
 | `amoRoth` | boolean | *(Advanced)* Whether to enforce at-most-one (AMO) constraints preventing simultaneous Roth conversions and tax-free withdrawals. | `true` |
 | `amoSurplus` | boolean | *(Advanced)* Whether to enforce XOR constraints preventing simultaneous surplus deposits and withdrawals from taxable or tax-free accounts. | `true` |
 | `bequest` | float | Target bequest value in today's dollars (in `units`). Used when `objective = "maxSpending"`. | `1` (if omitted with `maxSpending`) |
-| `bigMirmaa` | float | *(Advanced)* Big-M value for Medicare IRMAA bracket constraints (used when `withMedicare = "optimize"`). Should exceed any plausible aggregate MAGI. | `5e7` |
 | `bigMamo` | float | *(Advanced)* Big-M value for at-mot-one (AMO) constraints (mutually exclusive operations). Should exceed any individual withdrawal, conversion, or surplus deposit. | `5e7` |
+| `epsilon` | float | *(Advanced)* Lexicographic weight added to the objective to break ties. Adds a small penalty to Roth conversions, and when `N_i = 2`, also penalizes withdrawals of spouse 2 to favor withdrawals from spouse 1. Use a very small value so the primary objective dominates. | `0` |
 | `gap` | float | *(Advanced)* Relative MILP gap used by solvers and to scale convergence tolerances. | `1e-4` (default); if `withMedicare = "optimize"` and unset, set to `1e-3` (or `1e-2` when `maxRothConversion <= 15`) |
 | `maxIter` | integer | *(Advanced)* Maximum number of iterations for the self-consistent loop. Must be at least 1. | `29` |
 | `maxRothConversion` | float or string | Maximum annual Roth conversion amount (in `units`). Use `"file"` to take per-year limits from time lists; omit for no cap (except last year). | No cap unless provided |

{owlplanner-2026.1.26 → owlplanner-2026.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: owlplanner
-Version: 2026.1.26
+Version: 2026.2.2
 Summary: Owl - Optimal Wealth Lab: Retirement planner with great wisdom
 Project-URL: HomePage, https://github.com/mdlacasse/owl
 Project-URL: Repository, https://github.com/mdlacasse/owl
@@ -797,7 +797,7 @@ your computer and can be used to reproduce a case at a later time.
 
 ---------------------------------------------------------------------
 
-Copyright © 2024 - Martin-D. Lacasse
+Copyright © 2024-2026 - Martin-D. Lacasse
 
 Disclaimers: This code is for educatonal purposes only and does not constitute financial advice.
 

{owlplanner-2026.1.26 → owlplanner-2026.2.2}/README.md

@@ -85,7 +85,7 @@ your computer and can be used to reproduce a case at a later time.
 
 ---------------------------------------------------------------------
 
-Copyright © 2024 - Martin-D. Lacasse
+Copyright © 2024-2026 - Martin-D. Lacasse
 
 Disclaimers: This code is for educatonal purposes only and does not constitute financial advice.
 

{owlplanner-2026.1.26 → owlplanner-2026.2.2}/RELEASE_NOTES.md

@@ -1,13 +1,50 @@
-### Version 2026.01.26
-- Updated Jupyter notebooks
-- Improved logging
+# Owl Release Notes
 
-### Version 2026.01.21
-- Move "optimize" Medicare option to advanced section
-- Add solver option to disable surpluses in late years
-- Rename XOR -> AMO as correct term
+---
 
-### Version 2026.01.20
+## Version 2026.02.02
+
+### Rates
+- **Rate sequence modifiers** (issue #77): Add reverse and roll options for varying rate methods.
+  - New `reverse_sequence` (boolean) and `roll_sequence` (integer) in `setRates`, config, and TOML.
+  - UI: Reverse toggle and Roll (years) in Rates Selection → Advanced Options.
+  - Historical Range: same reverse/roll options in Advanced Options; `runHistoricalRange` accepts `reverse` and `roll` and applies them to each year’s historical sequence.
+  - Ignored for fixed/constant rate methods (with warning). Documented in PARAMETERS.md and Documentation.
+
+### Landing page and Quick Start
+- Update landing page (layout, link to repo, instructions for beginners).
+- Add short description of what optimization is performed.
+- Fix Quick Start line length (flake8).
+
+### UI and examples
+- Highlight current year in timelist and in worksheets (this year’s accounts).
+- Fix case status incorrectly set to modified when visiting Create Case page (getDate/sskeys).
+- Fix Joe’s example missing `withMedicare` option.
+- Fix Social Security URL on Fixed Income page.
+
+### Documentation and parameters
+- Sync Documentation.py with UI: TOC (Parameters Reference, Quick Start icon), Create Case labels, Output Files button names, Roth conversion toggle wording, Resources link, case file naming.
+- Update owl.tex description.
+- Document lexicographic weight and self-consistent loop default tolerance in docs.
+- PARAMETERS.md: document `reverse_sequence` and `roll_sequence`.
+
+---
+
+## Version 2026.01.28
+- Recoded Medicare optimization algorithm for SOS1 formulation.
+- Updated documents and parameters.
+- Added lexicographic weight epsilon in solver options.
+
+## Version 2026.01.26
+- Updated Jupyter notebooks.
+- Improved logging.
+
+## Version 2026.01.21
+- Move "optimize" Medicare option to advanced section.
+- Add solver option to disable surpluses in late years.
+- Rename XOR → AMO as correct term.
+
+## Version 2026.01.20
 - Fix negative taxable gains in years of negative returns
 - Fix limits in UI not allowing negative rates
 - Add more control hooks on solver (xor, maxIter)
@@ -17,37 +54,30 @@
 - Enable Python 3.14 in GH CI
 - Investigate tests on GH failing due to different linear solver
 - Disallow conversions and surplus in last 2 years
-- Connect MOSEK logger with verbose keyword
+- Connect MOSEK logger with verbose keyword.
 
-### Version 2026.01.17
+## Version 2026.01.17
 - Add more parameters to control solver
 - Add capability to specify years from last in fixed assets
 - Document negative/zero fixed-asset disposition years and update UI tooltip
 - Add tests for negative/zero fixed-asset disposition years
-- Improved default values for broader case applicability
-
-### Version 2026.01.15
-- Fix LTCG tax computation (self-consistent stacking accuracy)
-- Add non-taxable portion of SS to MAGI
-- Fix cash flow to include all fixed-asset proceeds
-- Apply max Roth conversion cap across both spouses
-- Clarify SS tax fraction vs LTCG effective rate
-
-### Version 2026.01.16
-- Extend longevity table to 120yo and add safety checks
-- Add 15% of untaxed SS back to MAGI
-- Update documentation (TeX)
-- Adjust reproducibility tests
-
-### Version 2026.01.15
-- Fix LTCG tax computation (self-consistent stacking accuracy)
-- Add non-taxable portion of SS to MAGI
-- Fix cash flow to include all fixed-asset proceeds
-- Apply max Roth conversion cap across both spouses
-- Clarify SS tax fraction vs LTCG effective rate
-- Align documentation and reproducibility baselines with code
-
-### Version 2026.01.12
+- Improved default values for broader case applicability.
+
+## Version 2026.01.16
+- Extend longevity table to 120 and add safety checks.
+- Add 15% of untaxed SS back to MAGI.
+- Update documentation (TeX).
+- Adjust reproducibility tests.
+
+## Version 2026.01.15
+- Fix LTCG tax computation (self-consistent stacking accuracy).
+- Add non-taxable portion of SS to MAGI.
+- Fix cash flow to include all fixed-asset proceeds.
+- Apply max Roth conversion cap across both spouses.
+- Clarify SS tax fraction vs LTCG effective rate.
+- Align documentation and reproducibility baselines with code.
+
+## Version 2026.01.12
 - Merge binary exclusion constraints for both spouses (one set per year instead of per individual)
   - Update paper to reflect binary variables $z_{nz}$ shared across both spouses
   - Reduce binary variable count from $4N_iN_n$ to $4N_n$ for married couples
@@ -56,9 +86,9 @@
 - Add 15-minute time limit for solution
 - Fix rare UI condition when starting Upload Case and hopping to Logs
 - Change convergence criteria to only consider objective function (not solution vector)
-- Split bigM between XOR exclusion constraints and IRMAA Medicare conditions
+- Split bigM between XOR exclusion constraints and IRMAA Medicare conditions.
 
-### Version 2026.01.08
+## Version 2026.01.08
 - Fix dividends being taxed twice on taxable account withdrawals
 - Remove int32 normalization of seed (reverted from 2026.01.07)
 - Remove unused file-based rates parameters (rateFile, rateSheetName, workbook_file, worksheet_name)
@@ -69,16 +99,16 @@
 - Update paper PDF to reflect change in dividend tax calculation
 - Replace duplicate owl.tex and images with symlinks to avoid duplication
 - Refactor code in config.py, debts.py, fixedassets.py, and utils.py
-- Add tests to increase coverage and harden code
+- Add tests to increase coverage and harden code.
 
-### Version 2026.01.07
+## Version 2026.01.07
 - Normalize seed to fit in signed int32 (issue #59)
 - Remove animation
 - Update Adamodar rates for 2025
 - Make Kim+Sam cases consistent
-- Make minor edits in About page
+- Make minor edits in About page.
 
-### Version 2026.01.05
+## Version 2026.01.05
 - Migrate examples and TOML configuration to snake_case (closing issue #52)
     - Optimizer still uses camelCase for distinction
 - Add reproducibility flag and merge reproducibility branch
@@ -100,7 +130,7 @@
 - Clean license and authorship
 - Improve Summary output styling
 
-### Version 2025.12.29
+## Version 2025.12.29
 - Integrate loguru logging system with global log and filters
     - Split logger per object
     - Add persistence in TOML file
@@ -124,7 +154,7 @@
 - Make OBBBA expiration year idiot-proof
 - Fix typo (issue #47)
 
-### Version 2025.12.20
+## Version 2025.12.20
 - Implement Debts and Fixed Assets capabilities
     - Mortgages, loans, restricted stocks, etc. and fixed lump-sum annuities can now be modeled
     - Include debts and fixed assets at end of plan in bequest
@@ -137,7 +167,7 @@
 - Improve UI
 - Improve integration with ssa.tools
 
-### Version 2025.12.16
+## Version 2025.12.16
 - Fix error message when dates are empty in Create_Case
 - Add fix to prevent stored TOML age from being out of range
 - Rename duplicate to copy
@@ -145,27 +175,27 @@
 - Prepare for new tax season
 - Carry minor fixes from dev version
 
-### Version 2025.12.11
+## Version 2025.12.11
 - Add more bubble help messages in Create Case
 - Fix bug in rates selection UI
 - Remove reliance on GitHub for graphics and example files
 - Update UI to use new file locations
 - Add new owl.png logo
 
-### Version 2025.12.10
+## Version 2025.12.10
 - Add date of birth due to social security rules when birthday on 1st and 2nd
 - Modify FRA calculations accordingly
 - Add integration to ssa.tools
 - Add Dale's help message for date of birth
 
-### Version 2025.12.09
+## Version 2025.12.09
 - Improve instructions for developers
 - Add link to ssa.tools on Fixed Income page
 - Fix bug on max age range for SS when month != 0
 - Add table of federal income tax itemized by bracket
 - Improve instructions for ssa.tools
 
-### Version 2025.12.05
+## Version 2025.12.05
 - Add instructions for obtaining PIA
 - Enhance documentation for obtaining PIA
 - Add generic reference for PIA calculation
@@ -173,7 +203,7 @@
 - Fix error in month input
 - Add hint for birth month
 
-### Version 2025.12.03
+## Version 2025.12.03
 - Code Social Security to use monthly PIA instead of annual amount
     - Add exact routines for FRA and increase/decrease factors due to claiming age
     - Add exact spousal benefits
@@ -187,7 +217,7 @@
 - Add caveat on account allocation ratios in documentation
 - Fix typo in documentation
 
-### Version 2025.11.09
+## Version 2025.11.09
 - Move development status to production/stable in pyproject
 - Make version propagate everywhere needed
 - Add node limit on MILP to avoid Streamlit server shutdown on memory consumption
@@ -209,7 +239,7 @@
 - Fix graph settings
 - Make case naming consistent
 
-### Version 2025.07.01
+## Version 2025.07.01
 - Add settings option for menu position (top or sidebar) thanks to Streamlit 1.46
     - Default is top menu
 - Add Net Investment Income Tax calculations in self-consistent loop

{owlplanner-2026.1.26 → owlplanner-2026.2.2}/USER_GUIDE.md

@@ -2,7 +2,7 @@
 
 ## A retirement exploration tool based on linear programming
 
-<img align=right src="https://github.com/mdlacasse/Owl/blob/main/docs/images/owl.png?raw=true" width="250">
+<img align=right src="https://github.com/mdlacasse/Owl/blob/main/papers/images/owl.png?raw=true" width="250">
 
 ------------------------------------------------------------------------------------
 ### About

{owlplanner-2026.1.26 → owlplanner-2026.2.2}/docker/README.md

@@ -2,7 +2,7 @@
 
 ## A retirement exploration tool based on linear programming
 
-<img align=right src="https://raw.github.com/mdlacasse/Owl/main/docs/images/owl.png" width="250">
+<img align=right src="https://raw.github.com/mdlacasse/Owl/main/papers/images/owl.png" width="250">
 
 ------------------------------------------------------------------------------------
 ### About

owlplanner-2026.2.2/examples/Case_alex+jamie.toml

@@ -0,0 +1,64 @@
+case_name = "Alex+Jamie"
+description = "A case where there is big difference in longevity."
+
+[basic_info]
+status = "married"
+names = [ "Alex", "Jamie",]
+date_of_birth = [ "1960-01-15", "1961-01-17",]
+life_expectancy = [ 72, 90,]
+start_date = "2026-01-01"
+
+[savings_assets]
+taxable_savings_balances = [ 500.0, 200.0,]
+tax_deferred_savings_balances = [ 1500.0, 400.0,]
+tax_free_savings_balances = [ 50.0, 40.0,]
+beneficiary_fractions = [ 1.0, 1.0, 1.0,]
+spousal_surplus_deposit_fraction = 0.5
+
+[household_financial_profile]
+HFP_file_name = "dictionary of DataFrames"
+
+[fixed_income]
+pension_monthly_amounts = [ 0, 0,]
+pension_ages = [ 65.0, 65.0,]
+pension_indexed = [ false, false,]
+social_security_pia_amounts = [ 3000, 1200,]
+social_security_ages = [ 69.0, 62.083333333333336,]
+
+[rates_selection]
+heirs_rate_on_tax_deferred_estate = 30.0
+dividend_rate = 1.72
+obbba_expiration_year = 2032
+method = "user"
+values = [ 7.000000000000001, 4.0, 3.3000000000000003, 2.8,]
+from = 1928
+to = 2025
+
+[asset_allocation]
+interpolation_method = "linear"
+interpolation_center = 15.0
+interpolation_width = 5.0
+type = "individual"
+generic = [ [ [ 60, 40, 0, 0,], [ 60, 40, 0, 0,],], [ [ 60, 40, 0, 0,], [ 60, 40, 0, 0,],],]
+
+[optimization_parameters]
+spending_profile = "flat"
+surviving_spouse_spending_percent = 60
+objective = "maxSpending"
+
+[solver_options]
+maxRothConversion = 400.0
+noRothConversions = "None"
+startRothConversions = 2026
+bequest = 0
+solver = "HiGHS"
+spendingSlack = 0
+amoRoth = true
+amoSurplus = true
+withSCLoop = true
+withMedicare = "loop"
+noLateSurplus = false
+previousMAGIs = [ 200.0, 200.0,]
+
+[results]
+default_plots = "today"

{owlplanner-2026.1.26 → owlplanner-2026.2.2}/examples/Case_drawdowncalc-comparison-1.toml

@@ -48,10 +48,10 @@ objective = "maxBequest"
 netSpending = 80.0
 maxRothConversion = 50
 startRothConversions = 2025
-withMedicare = "None"
 solver = "HiGHS"
 spendingSlack = 0
 withSCLoop = false
+withMedicare = "None"
 
 [results]
 default_plots = "today"

{owlplanner-2026.1.26 → owlplanner-2026.2.2}/examples/Case_jack+jill.toml

@@ -1,5 +1,5 @@
 case_name = "jack+jill"
-description = "This example aims to demonstrate some of Owl's capabilities. Jack and Jill are a married couple a few years from retirement. A wages and contributions file called 'jack+jill.xlsx' is associated with this case. This case uses the historical rate sequence of 1969 as a test case for guiding spending amounts from a near worst-case historical scenario. This case also demonstrates that the optimal strategy for Roth conversions does not necessarily involve surfing a tax bracket.  \nA good exercise for learning Owl's capabilities is to duplicate this case and compare two scenarios: one with optimized Roth conversions and one without. Another possible exercise could involve comparing a historical retirement in 1969 vs. one taken in 1966. Or anything else you can think of..."
+description = "This example aims to demonstrate some of Owl's capabilities. Jack and Jill are a married couple a few years from retirement. A Household Financial Profile called 'HFP_jack+jill.xlsx' is associated with this case. This case uses the historical rate sequence of 1969 as a test case for guiding spending amounts from a near worst-case historical scenario. This case also demonstrates that the optimal strategy for Roth conversions does not necessarily involve surfing a tax bracket.  \nA good exercise for learning Owl's capabilities is to duplicate this case and compare two scenarios: one with optimized Roth conversions and one without. Another possible exercise could involve comparing a historical retirement in 1969 vs. one taken in 1966. Or anything else you can think of..."
 
 [basic_info]
 status = "married"
@@ -52,11 +52,11 @@ objective = "maxSpending"
 maxRothConversion = 100
 noRothConversions = "Jill"
 startRothConversions = 2025
+withSCLoop = true
 withMedicare = "loop"
 bequest = 400
 solver = "HiGHS"
 spendingSlack = 0
-withSCLoop = true
 
 [results]
 default_plots = "today"

{owlplanner-2026.1.26 → owlplanner-2026.2.2}/examples/Case_joe.toml

@@ -1,5 +1,5 @@
 case_name = "joe"
-description = "This is an example of a case involving a single individual. Joe is single and will retire in a few years. His wages and contributions are contained in the 'joe.xlsx' spreadsheet."
+description = "This is an example of a case involving a single individual. Joe is single and will retire in a few years. His wages and contributions are contained in the 'HFP_joe.xlsx' Household Financial Profile."
 
 [basic_info]
 status = "single"
@@ -50,6 +50,8 @@ objective = "maxSpending"
 maxRothConversion = 50
 startRothConversions = 2025
 bequest = 300
+withSCLoop = true
+withMedicare = "loop"
 
 [results]
 default_plots = "nominal"

{owlplanner-2026.1.26 → owlplanner-2026.2.2}/examples/Case_john+sally.toml

@@ -1,5 +1,5 @@
 case_name = "john+sally"
-description = "This example reproduces the case of John and Sally, discussed by Eric Sajdak. This case can be used to compare the heuristic strategy of surfing a tax bracket for performing Roth conversions to a solution optimized by linear programming. The former is a good approach when one assumes fixed rates. When rates are varying, and the market drops, an optimized solution shows that it is sometime advantageous to convert above the target tax bracket. File 'john+sally.xlsx' contains wages and contributions associated with this case. Run this case with different rates to see the effects on Roth conversions."
+description = "This example reproduces the case of John and Sally, discussed by Eric Sajdak. This case can be used to compare the heuristic strategy of surfing a tax bracket for performing Roth conversions to a solution optimized by linear programming. The former is a good approach when one assumes fixed rates. When rates are varying, and the market drops, an optimized solution shows that it is sometime advantageous to convert above the target tax bracket. File 'HFP_john+sally.xlsx' contains wages and contributions associated with this case. Run this case with different rates to see the effects on Roth conversions."
 
 [basic_info]
 status = "married"
@@ -50,10 +50,10 @@ netSpending = 100
 maxRothConversion = 200
 noRothConversions = "None"
 startRothConversions = 2025
+withSCLoop = true
 withMedicare = "loop"
 solver = "HiGHS"
 spendingSlack = 0
-withSCLoop = true
 
 [results]
 default_plots = "today"

{owlplanner-2026.1.26 → owlplanner-2026.2.2}/examples/Case_jon+jane.toml

@@ -1,5 +1,5 @@
 case_name = "Jon+Jane"
-description = "This case reproduces a similar case discussed a while back on i-orp. It involves Jon and Jane close to retirement, and assumes a base case of optimistic returns of 10% with an inflation of 3.5%. A wages and contributions file called 'jon+jane.xlsx' is associated with this case."
+description = "This case reproduces a similar case discussed a while back on i-orp. It involves Jon and Jane close to retirement, and assumes a base case of optimistic returns of 10% with an inflation of 3.5%. A Household Financial Profile called 'HFP_jon+jane.xlsx' is associated with this case."
 
 [basic_info]
 status = "married"
@@ -50,11 +50,11 @@ objective = "maxSpending"
 maxRothConversion = 0.0
 noRothConversions = "None"
 startRothConversions = 2025
-withMedicare = "loop"
 bequest = 30.0
 solver = "HiGHS"
 spendingSlack = 0
 withSCLoop = true
+withMedicare = "loop"
 
 [results]
 default_plots = "today"

{owlplanner-2026.1.26 → owlplanner-2026.2.2}/examples/Case_kim+sam-bequest.toml

@@ -1,5 +1,5 @@
 case_name = "kim+sam-bequest"
-description = "This is the case of Kim and Sam used as an example case for optimizing bequest and Roth conversions. A HFP file is associated with this case."
+description = "This is the case of Kim and Sam used as an example case for optimizing bequest and Roth conversions. A Household Financial Profile called 'HFP_kim+sam.xslx' is associated with this case."
 
 [basic_info]
 status = "married"
@@ -54,10 +54,10 @@ netSpending = 145
 maxRothConversion = 100
 noRothConversions = "None"
 startRothConversions = 2026
-withMedicare = "loop"
 solver = "HiGHS"
 spendingSlack = 0
 withSCLoop = true
+withMedicare = "loop"
 
 [results]
 default_plots = "today"

{owlplanner-2026.1.26 → owlplanner-2026.2.2}/examples/Case_kim+sam-spending.toml

@@ -1,5 +1,5 @@
 case_name = "kim+sam-spending"
-description = "This is the case of Kim and Sam used as an example case for optimizing spending and Roth conversions. An HFP file is associated with this case."
+description = "This is the case of Kim and Sam used as an example case for optimizing spending and Roth conversions. A Household Financial Profile called 'HFP-kim+sam.xslx' is associated with this case."
 
 [basic_info]
 status = "married"
@@ -53,11 +53,11 @@ objective = "maxSpending"
 maxRothConversion = 100
 noRothConversions = "None"
 startRothConversions = 2026
-withMedicare = "loop"
 bequest = 0
 solver = "HiGHS"
 spendingSlack = 0
 withSCLoop = true
+withMedicare = "loop"
 
 [results]
 default_plots = "today"