owlplanner 2025.12.3__tar.gz → 2025.12.20__tar.gz

{owlplanner-2025.12.3 → owlplanner-2025.12.20}/.gitignore

@@ -8,3 +8,4 @@ dist
 otherFiles
 myfiles
 secrets
+uv.lock

owlplanner-2025.12.20/INSTALL.md

@@ -0,0 +1,132 @@
+# Owl - Optimal Wealth Lab
+
+## 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">
+
+------------------------------------------------------------------------------------
+### About
+This document is aimed at software developers desiring to install the Owl source code
+and run it locally on their computer.
+
+For end-users, we suggest accessing Owl from the
+[Streamlit Community Server](http://owlplanner.streamlit.app)
+or, if one prefers to have everything on their own computer,
+to install and run a Docker image as described in these [instructions](docker/README.md).
+
+### Requirements
+You will need a Python environment, and the `pip` module installed on your
+computer for completing the installation. The `build` module will be required
+for developers. You will also need `git` to manage the source code from GitHub
+which is found [here](https://git-scm.com/install/windows) for Windows,
+and by installing developer tools on MacOS and Linux.
+
+
+A good option for a comprehensive Python environment is to use the *Anaconda* distribution
+that can be found [here](https://repo.anaconda.com/archive/) for various operating systems.
+Installation of *Anaconda* can be done by downloading and running the installation
+file corresponding to your operating system and hardware.
+
+Instructions given here are command-line instructions to be entered from a terminal window.
+
+If using *Anaconda*, `pip` can be installed as follows
+```
+conda install pip
+```
+otherwise, your distribution will most likely include `pip` already.
+
+The `build` module is included in *Anaconda*.
+Command `pip install build` will install it in other distributions.
+
+### Creating a virtual environment
+It is common practice to create a virtual environment for a specific project.
+This is to avoid making changes in the base ditribution that could break dependencies.
+Creating and activating a new environment called *owlenv* in *Anaconda*
+is achieved by the following commands: 
+```
+conda create --name owlenv
+conda activate owlenv
+```
+A cheat sheet for *Anaconda* can be found
+[here](https://docs.conda.io/projects/conda/en/latest/user-guide/cheatsheet.html).
+
+When not using `conda`, creating and activating an environment can be done by
+using the module `venv` as follows:
+```
+python -m venv owlenv
+```
+This will create subdirectory *owlenv* in the current directory.
+For activating this environment:
+```
+# in MS command
+.\owlenv\Scripts\activate.bat
+
+# in MS PowerShell
+./owlenv/Scripts/activate.ps1
+
+# MacOS or Linux
+source ./owlenv/Scripts/activate
+```
+More details on how to create a virtual environment using *venv* can be found
+[here](https://python.land/virtual-environments/virtualenv).
+
+### Obtaining Owl's source code
+We assume that you have created and activated a virtual environment
+at this point. From there, we install the latest version of Owl from GitHub.
+```shell
+git clone https://github.com/mdlacasse/Owl.git
+
+```
+Then go (`cd`) to the directory where you installed Owl.
+```
+cd Owl
+```
+From the top directory of the source code run:
+The following command will install the current version of Owl and all its dependencies:
+```shell
+pip install --upgrade -r requirements.txt
+```
+You can also install the Owl package directly from the [Python Package Index](http://pypi.org).
+
+### Running the Streamlit frontend locally
+Once Owl's source code and all its dependencies as been installed,
+one can run the Owl user interface locally:
+```shell
+# From Windows
+./owlplanner.cmd
+
+# From MacOS or Linux
+./owlplanner.sh
+```
+This will open a tab on your default browser.
+
+### Installation steps for developers
+First use the same steps as above to create and activate a virtual environment
+and install the source code from GitHub.
+Then make sure that the `build` module is installed (`pip install build`).
+
+The next commands will build and install the Owl module in "edit mode"
+```shell
+python -m build
+pip install -e .
+```
+The -e instructs `pip` to install in *editable* mode and use the live version
+in the current directory tree.
+
+### Publishing a version (for reference only)
+Run checks before all commits:
+```
+flake8 ui src tests
+pytest
+```
+To update version, edit number in `src/owlplanner/version.py`.
+
+To update package on pypi or testpypi,
+
+```shell
+rm dist/*
+python -m build
+twine upload --repository [repo] dist/*
+```
+where [repo] is *testpypi* or *pypi* depending on the type of release.
+

{owlplanner-2025.12.3 → owlplanner-2025.12.20}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: owlplanner
-Version: 2025.12.3
+Version: 2025.12.20
 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
@@ -692,6 +692,7 @@ Classifier: Programming Language :: Python :: 3
 Classifier: Topic :: Office/Business :: Financial :: Investment
 Requires-Python: >=3.10
 Requires-Dist: highspy
+Requires-Dist: jupyter>=1.1.1
 Requires-Dist: matplotlib
 Requires-Dist: numpy
 Requires-Dist: odfpy
@@ -699,6 +700,7 @@ Requires-Dist: openpyxl
 Requires-Dist: pandas
 Requires-Dist: plotly>=6.3
 Requires-Dist: pulp
+Requires-Dist: pyyaml>=6.0.3
 Requires-Dist: scipy
 Requires-Dist: seaborn
 Requires-Dist: streamlit
@@ -733,154 +735,6 @@ Follow these [instructions](docker/README.md) for using this option.
 - **Self-hosting:** Run Owl locally on your computer using Python code and libraries.
 Follow these [instructions](INSTALL.md) to install from the source code and self-host on your own computer.
 
--------------------------------------------------------------------------------------
-## Overview
-This package is a modeling framework for exploring the sensitivity of retirement financial decisions.
-Strictly speaking, it is not a planning tool, but more an environment for exploring *what if* scenarios.
-It provides different realizations of a financial strategy through the rigorous
-mathematical optimization of relevant decision variables. Two major objective goals can be set: either
-maximize net spending, or after-tax bequest under various constraints.
-Look at the *Capabilities* section below for more detail.
-
-One can certainly have a savings plan, but due to the volatility of financial investments,
-it is impossible to have a certain asset earnings plan. This does not mean one cannot make decisions.
-These decisions need to be guided with an understanding of the sensitivity of the parameters.
-This is exactly where this tool fits in. Given your savings capabilities and spending desires,
-it can generate different future realizations of
-your strategy under different market assumptions, helping to better understand your financial situation.
-
--------------------------------------------------------------------------------------
-## Purpose and vision
-One goal of Owl is to provide a free and open-source ecosystem that has cutting-edge optimization capabilities,
-allowing for the next generation of Python-literate retirees to experiment with their own financial future
-while providing a codebase where they can learn and contribute. At the same time, an intuitive and easy-to-use
-user interface based on Streamlit allows a broad set of users to benefit from the application as it only requires basic financial knowledge.
-
-There are and were
-good retirement optimizers in the recent past, but the vast majority of them are either proprietary platforms
-collecting your data, or academic papers that share the results without really sharing the details of
-the underlying mathematical models.
-The algorithms in Owl rely on the open-source HiGHS linear programming solver but they have also been ported and tested on
-other platforms such as Mosek and COIN-OR. The complete formulation and
-detailed description of the underlying
-mathematical model can be found [here](https://github.com/mdlacasse/Owl/blob/main/docs/owl.pdf).
-
-It is anticipated that most end users will use Owl through the graphical interface
-either at [owlplanner.streamlit.app](https://owlplanner.streamlit.app)
-or [installed](INSTALL.md) on their own computer.
-The underlying Python package can also be used directly through Python scripts or Jupyter Notebooks
-as described [here](USER_GUIDE.md).
-
-Not every retirement decision strategy can be framed as an easy-to-solve optimization problem.
-In particular, if one is interested in comparing different withdrawal strategies,
-[FI Calc](https://ficalc.app) is an elegant application that addresses this need.
-If, however, you also want to optimize spending, bequest, and Roth conversions, with
-an approach also considering Medicare and federal income tax over the next few years,
-then Owl is definitely a tool that can help guide your decisions.
-
---------------------------------------------------------------------------------------
-## Capabilities
-Owl can optimize for either maximum net spending under the constraint of a given bequest (which can be zero),
-or maximize the after-tax value of a bequest under the constraint of a desired net spending profile,
-and under the assumption of a heirs marginal tax rate.
-Roth conversions are also considered, subject to an optional maximum conversion amount,
-and optimized to suit the goals of the selected objective function.
-All calculations are indexed for inflation, which is either provided as a fixed rate,
-or through historical values, as are all other rates used for the calculations.
-These rates can be used for backtesting different scenarios by choosing
-*historical* rates, or by choosing *historical average* rates over a historical year range,
-or what I coined "*histochastic*" rates which are
-generated using the statistical distribution of observed historical rates.
-
-Portfolios available for experimenting include assets from the S&P 500, Corporate Bonds Baa, Treasury 10-y Notes,
-and cash assets assumed to just follow inflation which is represented by the Consumer Price Index.
-Other asset classes can easily be added, but would add complexity while only providing diminishing insights.
-Historical data used are from
-[Aswath Damodaran](https://pages.stern.nyu.edu/~adamodar/) at the Stern School of Business.
-Asset allocations are selected for the duration of the plan, and these can glide linearly
-or along a configurable s-curve over the lifespan of the individual.
-
-Spending profiles are adjusted for inflation, and so are all other indexable quantities. Proflies can be
-flat or follow a *smile* curve which is also adjustable through three simple parameters.
-
-Available rates are from 1928 to last year and can be used to test historical performance.
-Fixed rates can also be provided, as well as *histochastic* rates, which are generated using
-the statistical characteristics (means and covariance matrix) of
-a selected historical year range. Pure *stochastic* rates can also be generated
-if the user provides means, volatility (expressed as standard deviation), and optionally
-the correlations between the different assets return rates provided as a matrix, or a list of
-the off-diagonal elements (see documentation for details).
-Average rates calculated over a historical data period can also be chosen.
-
-Monte Carlo simulations capabilities are included and provide a probability of success and a histogram of
-outcomes. These simulations can be used for either determining the probability distribution of the
-maximum net spending amount under
-the constraint of a desired bequest, or the probability distribution of the maximum
-bequest under the constraint of a desired net spending amount. Unlike discrete-event
-simulators, Owl uses an optimization algorithm for every new scenario, which results in more
-calculations being performed. As a result, the number of cases to be considered should be kept
-to a reasonable number. For a few hundred cases, a few minutes of calculations can provide very good estimates
-and reliable probability distributions.
-
-Optimizing each solution is more representative than event-base simulators
-in the sense that optimal solutions
-will naturally adjust to the return scenarios being considered.
-This is more realistic as retirees would certainly re-evaluate
-their expectations under severe market drops or gains.
-This optimal approach provides a net benefit over event-based simulators,
-which maintain a distribution strategy either fixed, or within guardrails for capturing the
-retirees' reactions to the market.
-
-Basic input parameters can be entered through the user interface
-while optional additional time series can be read from
-an Excel spreadsheet that contains future wages, contributions
-to savings accounts, and planned *big-ticket items* such as the purchase of a lake house,
-the sale of a boat, large gifts, or inheritance.
-
-Three types of savings accounts are considered: taxable, tax-deferred, and tax-free,
-which are all tracked separately for married individuals. Asset transition to the surviving spouse
-is done according to beneficiary fractions for each type of savings account.
-Tax status covers married filing jointly and single, depending on the number of individuals reported.
-
-Maturation rules for Roth contributions and conversions are implemented as constraints
-limiting withdrawal amounts to cover Roth account balances for 5 years after the events.
-Medicare and IRMAA calculations are performed through a self-consistent loop on cash flow constraints.
-They can also be optimized explicitly as an option, but this choice can lead to longer calculations
-due to the use of the many additional binary variables required by the formulation.
-Future Medicare and IRMAA values are simple projections of current values with the assumed inflation rates.
-
-Owl has a basic social security calculator that determines the actual benefits based on the individual's
-primary insurance amount (PIA), full retirement age (FRA), and claiming age. Both
-spousal's benefits and survivor's benefits are calculated for non-complex cases.
-
-### Limitations
-Owl is work in progress. At the current time:
-- Only the US federal income tax is considered (and minimized through the optimization algorithm).
-Head of household filing status has not been added but can easily be.
-- Required minimum distributions are calculated, but tables for spouses more than 10 years apart are not included.
-These cases are detected and will generate an error message.
-- Current version has no optimization of asset allocations between individuals and/or types of savings accounts.
-If there is interest, that could be added in the future.
-- In the current implementation, social securiy is always taxed at 85%, assuming that your taxable income will be larger than 34 k$ (single) or 44 k$ (married filing jointly).
-- When Medicare calculations are done through a self-consistent loop,
-the Medicare premiums are calculated after an initial solution is generated,
-and then a new solution is re-generated with these premiums as a constraint.
-In some situations, when the income (MAGI) is near an IRMAA bracket, oscillatory solutions can arise.
-While the solutions generated are very close to one another, Owl will pick the smallest solution
-for being conservative. While sometimes computationally costly,
-a comparison with a full Medicare optimization should always be performed.
-- Part D is not included in the IRMAA calculations. Only Part B is taken into account, 
-which is considerably more significant.
-- Future tax brackets are pure speculations derived from the little we know now and projected to the next 30 years.
-Your guesses are as good as mine.
-
-The solution from an optimization algorithm has only two states: feasible and infeasible.
-Therefore, unlike event-driven simulators that can tell you that your distribution strategy runs
-out of money in year 20, an optimization-based solver can only tell you that a solution does or does not
-exist for the plan being considered. Examples of infeasible solutions include requesting a bequeathed
-estate value too large for the savings assets to support, even with zero net spending basis,
-or maximizing the bequest subject to a net spending basis that is already too large for the savings
-assets to support, even with no estate being left.
 
 ---------------------------------------------------------------
 ## Documentation
@@ -892,16 +746,46 @@ assets to support, even with no estate being left.
 ---------------------------------------------------------------------
 
 ## Credits
-- Historical rates from [Aswath Damodaran](https://pages.stern.nyu.edu/~adamodar/)
-- Image from [freepik](https://freepik.com)
-- Optimization solver from [HiGHS](https://highs.dev)
-- Streamlit Community Cloud [Streamlit](https://streamlit.io)
-- Contributors: Josh (noimjosh@gmail.com) for Docker image code,
- kg333 for fixing an error in Docker's instructions,
- Dale Seng (sengsational) for great insights and suggestions,
+- Contributors:
  Robert E. Anderson (NH-RedAnt) for bug fixes and suggestions,
  Clark Jefcoat (hubcity) for fruitful interactions,
- Benjamin Quinn (blquinn) and Gene Wood (gene1wood) for improvements and bug fixes.
+ kg333 for fixing an error in Docker's instructions,
+ John Leonard (jleonard99) for great suggestions, website, and more to come,
+ Benjamin Quinn (blquinn) for improvements and bug fixes,
+ Dale Seng (sengsational) for great insights, testing, and suggestions,
+ Josh Williams (noimjosh) for Docker image code,
+ Gene Wood (gene1wood) for improvements and bug fixes.
+- Greg Grothaus for developing [ssa.tools](https://ssa.tools) and providing an integration with Owl.
+- Owl image is from [freepik](https://freepik.com).
+- Historical rates are from [Aswath Damodaran](https://pages.stern.nyu.edu/~adamodar/).
+- Linear programming optimization solvers are from
+[HiGHS](https://highs.dev) and [PuLP](https://coin-or.github.io/pulp/).
+It can also run on [MOSEK](https://mosek.com) if available on your computer.
+- Owl planner relies on the following [Python](https://python.org) packages:
+    - [highspy](https://highs.dev),
+    [Matplotlib](https://matplotlib.org),
+    [Numpy](https://numpy.org),
+    [odfpy](https://https://pypi.org/project/odfpy),
+    [openpyxl](https://openpyxl.readthedocs.io),
+    [Pandas](https://pandas.pydata.org),
+    [Plotly](https://plotly.com),
+    [PuLP](https://coin-or.github.io/pulp),
+    [Scipy](https://scipy.org),
+    [Seaborn](https://seaborn.pydata.org),
+    [toml](https://toml.io),
+ and [Streamlit](https://streamlit.io) for the front-end.
+
+## Bugs and Feature Requests
+Please submit bugs and feature requests through
+[GitHub](https://github.com/mdlacasse/owl/issues) if you have a GitHub account
+or directly by [email](mailto:martin.d.lacasse@gmail.com).
+Or just drop me a line to report your experience with the tool.
+
+## Privacy
+This app does not store or forward any information. All data entered is lost
+after a session is closed. However, you can choose to download selected parts of your
+own data to your computer before closing the session. These data will be stored strictly on
+your computer and can be used to reproduce a case at a later time.
 
 ---------------------------------------------------------------------
 

owlplanner-2025.12.20/README.md

@@ -0,0 +1,91 @@
+
+# Owl - Optimal Wealth Lab
+
+## 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">
+
+-------------------------------------------------------------------------------------
+
+### TL;DR
+Owl is a retirement financial planning tool that uses a linear programming
+optimization algorithm to provide guidance on retirement decisions
+such as contributions, withdrawals, Roth conversions, and more.
+Users can select varying return rates to perform historical back testing,
+stochastic rates for performing Monte Carlo analyses,
+or fixed rates either derived from historical averages, or set by the user.
+
+There are three ways to run Owl:
+
+- **Streamlit Hub:** Run Owl remotely as hosted on the Streamlit Community Server at
+[owlplanner.streamlit.app](https://owlplanner.streamlit.app).
+
+- **Docker Container:** Run Owl locally on your computer using a Docker image.
+Follow these [instructions](docker/README.md) for using this option.
+
+- **Self-hosting:** Run Owl locally on your computer using Python code and libraries.
+Follow these [instructions](INSTALL.md) to install from the source code and self-host on your own computer.
+
+
+---------------------------------------------------------------
+## Documentation
+
+- Documentation for the app user interface is available from the interface [itself](https://owlplanner.streamlit.app/Documentation).
+- Installation guide and software requirements can be found [here](INSTALL.md).
+- User guide for the underlying Python package as used in a Jupyter notebook can be found [here](USER_GUIDE.md).
+
+---------------------------------------------------------------------
+
+## Credits
+- Contributors:
+ Robert E. Anderson (NH-RedAnt) for bug fixes and suggestions,
+ Clark Jefcoat (hubcity) for fruitful interactions,
+ kg333 for fixing an error in Docker's instructions,
+ John Leonard (jleonard99) for great suggestions, website, and more to come,
+ Benjamin Quinn (blquinn) for improvements and bug fixes,
+ Dale Seng (sengsational) for great insights, testing, and suggestions,
+ Josh Williams (noimjosh) for Docker image code,
+ Gene Wood (gene1wood) for improvements and bug fixes.
+- Greg Grothaus for developing [ssa.tools](https://ssa.tools) and providing an integration with Owl.
+- Owl image is from [freepik](https://freepik.com).
+- Historical rates are from [Aswath Damodaran](https://pages.stern.nyu.edu/~adamodar/).
+- Linear programming optimization solvers are from
+[HiGHS](https://highs.dev) and [PuLP](https://coin-or.github.io/pulp/).
+It can also run on [MOSEK](https://mosek.com) if available on your computer.
+- Owl planner relies on the following [Python](https://python.org) packages:
+    - [highspy](https://highs.dev),
+    [Matplotlib](https://matplotlib.org),
+    [Numpy](https://numpy.org),
+    [odfpy](https://https://pypi.org/project/odfpy),
+    [openpyxl](https://openpyxl.readthedocs.io),
+    [Pandas](https://pandas.pydata.org),
+    [Plotly](https://plotly.com),
+    [PuLP](https://coin-or.github.io/pulp),
+    [Scipy](https://scipy.org),
+    [Seaborn](https://seaborn.pydata.org),
+    [toml](https://toml.io),
+ and [Streamlit](https://streamlit.io) for the front-end.
+
+## Bugs and Feature Requests
+Please submit bugs and feature requests through
+[GitHub](https://github.com/mdlacasse/owl/issues) if you have a GitHub account
+or directly by [email](mailto:martin.d.lacasse@gmail.com).
+Or just drop me a line to report your experience with the tool.
+
+## Privacy
+This app does not store or forward any information. All data entered is lost
+after a session is closed. However, you can choose to download selected parts of your
+own data to your computer before closing the session. These data will be stored strictly on
+your computer and can be used to reproduce a case at a later time.
+
+---------------------------------------------------------------------
+
+Copyright &copy; 2024 - Martin-D. Lacasse
+
+Disclaimers: This code is for educatonal purposes only and does not constitute financial advice.
+
+Code output has been verified with analytical solutions when applicable, and comparative approaches otherwise.
+Nevertheless, accuracy of results is not guaranteed.
+
+--------------------------------------------------------
+

{owlplanner-2025.12.3 → owlplanner-2025.12.20}/RELEASE_NOTES.md

@@ -1,3 +1,36 @@
+### Version 2025.12.20
+- Implemented Debts and Fixed Assets capabilities
+    - Mortgages, loans, restricted stocks, etc. and fixed lump-sum annuities can now be modeled
+    - Debts and fixed assets at end of plan included in bequest
+- Extended Wages and Contributions page which was renamed Household Financial Profile
+- Added debt payment and fixed assets bequest reporting to Synopsis
+- Improved user interface
+- Improved integration with ssa.tools
+
+### Version 2025.12.16
+- Fix error message when dates are empty in Create_Case
+- Carry minor fixes from dev version
+
+### Version 2025.12.11
+- Add more bubble help messages in Create Case
+- Fixed bug in rates selection UI
+- Remove reliance on GitHub for graphics and example files
+
+### Version 2025.12.10
+- Added date of birth due to funny social security rules when birthday on 1st and 2nd
+- Modified FRA calculations accordingly 
+- Added integration to ssa.tools
+
+### Version 2025.12.09
+- Improved instructions for developers
+- Added link to ssa.tools on `Fixed Income` page
+- Fixed bug on max age range for SS when month != 0
+- Added table of federal income tax itemized by bracket
+
+### Version 2025.12.05
+- Added instructions for obtaining PIA
+- Bug fix in Fixed Income UI
+
 ### Version 2025.12.03
 - Coded social security to use monthly PIA instead of annual amount
     - Added exact routines for FRA and increase/decrease factors due to claiming age

owlplanner-2025.12.20/awi.txt

@@ -0,0 +1,75 @@
+# https://www.ssa.gov/OACT/COLA/awiseries.html		
+1951	"2,799.16"	�  
+1952	"2,973.32"	6.22%
+1953	"3,139.44"	5.59%
+1954	"3,155.64"	0.52%
+1955	"3,301.44"	4.62%
+1956	"3,532.36"	6.99%
+1957	"3,641.72"	3.10%
+1958	"3,673.80"	0.88%
+1959	"3,855.80"	4.95%
+1960	"4,007.12"	3.92%
+1961	"4,086.76"	1.99%
+1962	"4,291.40"	5.01%
+1963	"4,396.64"	2.45%
+1964	"4,576.32"	4.09%
+1965	"4,658.72"	1.80%
+1966	"4,938.36"	6.00%
+1967	"5,213.44"	5.57%
+1968	"5,571.76"	6.87%
+1969	"5,893.76"	5.78%
+1970	"6,186.24"	4.96%
+1971	"6,497.08"	5.02%
+1972	"7,133.80"	9.80%
+1973	"7,580.16"	6.26%
+1974	"8,030.76"	5.94%
+1975	"8,630.92"	7.47%
+1976	"9,226.48"	6.90%
+1977	"9,779.44"	5.99%
+1978	"10,556.03"	7.94%
+1979	"11,479.46"	8.75%
+1980	"12,513.46"	9.01%
+1981	"13,773.10"	10.07%
+1982	"14,531.34"	5.51%
+1983	"15,239.24"	4.87%
+1984	"16,135.07"	5.88%
+1985	"16,822.51"	4.26%
+1986	"17,321.82"	2.97%
+1987	"18,426.51"	6.38%
+1988	"19,334.04"	4.93%
+1989	"20,099.55"	3.96%
+1990	"21,027.98"	4.62%
+1991	"21,811.60"	3.73%
+1992	"22,935.42"	5.15%
+1993	"23,132.67"	0.86%
+1994	"23,753.53"	2.68%
+1995	"24,705.66"	4.01%
+1996	"25,913.90"	4.89%
+1997	"27,426.00"	5.84%
+1998	"28,861.44"	5.23%
+1999	"30,469.84"	5.57%
+2000	"32,154.82"	5.53%
+2001	"32,921.92"	2.39%
+2002	"33,252.09"	1.00%
+2003	"34,064.95"	2.44%
+2004	"35,648.55"	4.65%
+2005	"36,952.94"	3.66%
+2006	"38,651.41"	4.60%
+2007	"40,405.48"	4.54%
+2008	"41,334.97"	2.30%
+2009	"40,711.61"	-1.51%
+2010	"41,673.83"	2.36%
+2011	"42,979.61"	3.13%
+2012	"44,321.67"	3.12%
+2013	"44,888.16"	1.28%
+2014	"46,481.52"	3.55%
+2015	"48,098.63"	3.48%
+2016	"48,642.15"	1.13%
+2017	"50,321.89"	3.45%
+2018	"52,145.80"	3.62%
+2019	"54,099.99"	3.75%
+2020	"55,628.60"	2.83%
+2021	"60,575.07"	8.89%
+2022	"63,795.13"	5.32%
+2023	"66,621.80"	4.43%
+2024	"69,846.57"	4.84%

owlplanner-2025.12.20/docker/buildPackage.cmd

@@ -0,0 +1,10 @@
+::
+:: A simple script to build Python package
+::
+cd ..
+del /Q dist\*
+type nul > uv.lock
+python -m build .
+del uv.lock
+
+twine upload --repository pypi dist\*

owlplanner-2025.12.20/docker/buildPackage.sh

@@ -0,0 +1,10 @@
+## !/bin/bash or similar
+
+cd ..
+rm dist/*.whl dist/*.tar.gz
+
+touch uv.lock
+python -m build .
+rm uv.lock
+
+twine upload --repository pypi dist/*