dairy-data-tools 0.2.0__tar.gz

dairy_data_tools-0.2.0/.gitignore

@@ -0,0 +1,6 @@
+__pycache__/
+.pytest_cache/
+*.pyc
+.venv/
+dist/
+docs/private/

dairy_data_tools-0.2.0/CITATION.cff

@@ -0,0 +1,23 @@
+cff-version: 1.2.0
+message: "If you use this software, please cite it as below."
+type: software
+title: "Dairy Data Tools: a dairy farm's DairyComp and EZfeed exports, read for consultants and their AI agents"
+abstract: >-
+  Agent skills and standard-library Python scripts that read a dairy farm's own DairyComp 305 and EZfeed exports:
+  the DairyComp commands to export with, the herd and each pen and cow, pen cows joined to pen feed (intake, ECM per
+  lb DM, feed cost per cwt, IOFC, NASEM predicted intake), a weekly or visit review, and a ration change with the
+  season taken out. Read-only, no network.
+authors:
+  - family-names: Lucey
+    given-names: Pádraig
+    orcid: "https://orcid.org/0000-0003-3885-2439"
+version: 0.2.0
+license: Apache-2.0
+repository-code: "https://github.com/padge01/dairy-data-tools"
+keywords:
+  - dairy
+  - DairyComp
+  - EZfeed
+  - herd management
+  - feed efficiency
+  - AI agents

dairy_data_tools-0.2.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

dairy_data_tools-0.2.0/LICENSE-skills.md

@@ -0,0 +1,8 @@
+# The skills' text: CC BY 4.0
+
+The text of each skill (`plugins/dairy-data-tools/skills/*/SKILL.md`) is licensed under the Creative Commons
+Attribution 4.0 International licence: https://creativecommons.org/licenses/by/4.0/
+
+You may share and adapt it for any purpose, as long as you give credit ("Dairy Data Tools, by Pádraig Lucey, Dairy Data
+Science"), link to the licence, and say if you changed it. The scripts beside the skills are code, under Apache-2.0
+(LICENSE).

dairy_data_tools-0.2.0/NOTICE

@@ -0,0 +1,15 @@
+Dairy Data Tools
+Copyright 2026 Pádraig Lucey (Dairy Data Science, https://dairydatascience.com)
+
+The code (Python scripts, tools and tests) is licensed under the Apache License, Version 2.0 (LICENSE).
+The skills' text (every SKILL.md) is licensed under Creative Commons Attribution 4.0 International (LICENSE-skills.md).
+The sample herd is made up, by the author's own herd simulator; no real farm's records are in this repository.
+
+Figures and their sources:
+- Energy-corrected milk: 0.327 x milk + 12.95 x fat + 7.65 x protein, in lb (Tyrrell and Reid, 1965; Orth, 1992).
+- Predicted dry matter intake: National Academies of Sciences, Engineering, and Medicine (2021), Nutrient
+  Requirements of Dairy Cattle, 8th revised edition, equation 2-1.
+- 21-day pregnancy rate: counted the way DairyComp 305's BREDSUM report counts it.
+
+DairyComp 305 and EZfeed are products of Valley Ag Software. This project is not affiliated with or endorsed
+by Valley Ag Software. It reads only export files that the programs write for their users.

dairy_data_tools-0.2.0/PKG-INFO

@@ -0,0 +1,119 @@
+Metadata-Version: 2.5
+Name: dairy-data-tools
+Version: 0.2.0
+Summary: Read a dairy farm's DairyComp and EZfeed exports: the herd, each pen and cow, pen cows joined to pen feed, a weekly or visit review, and a ration change with the season taken out.
+Project-URL: Homepage, https://github.com/padge01/dairy-data-tools
+Project-URL: Issues, https://github.com/padge01/dairy-data-tools/issues
+Author: Pádraig Lucey
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: LICENSE-skills.md
+License-File: NOTICE
+Keywords: DairyComp,ECM,EZfeed,IOFC,dairy,feed efficiency,herd management,nutrition,veterinary
+Classifier: Intended Audience :: Science/Research
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Scientific/Engineering
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+
+# Dairy Data Tools
+
+Free tools for dairy nutritionists and their AI agents. Give your agent a farm's own **DairyComp** and **EZfeed**
+exports and ask about a pen: how it's doing, what a ration change did, and whether it's just the season. The numbers
+come from small, tested scripts, not from the AI's guesswork.
+
+By Pádraig Lucey, MVB, MPVM, Ph.D. ([Dairy Data Science](https://dairydatascience.com)).
+
+## Get it
+
+**In the Claude app** (desktop or claude.ai, a paid plan with code execution on): Customize > Plugins > Add marketplace >
+`padge01/dairy-data-tools`, then Add **Dairy Data Tools**. Attach the farm's export files to a chat and ask.
+
+**In Claude Code:**
+
+```bash
+claude plugin marketplace add padge01/dairy-data-tools
+```
+
+```bash
+claude plugin install dairy-data-tools@dairy-data-tools
+```
+
+**In other agents** (Codex, Cursor, Gemini CLI and others that read Agent Skills):
+
+```bash
+npx skills add padge01/dairy-data-tools
+```
+
+**In Python, without an agent** (Python 3.10 or later; nothing else to install):
+
+```bash
+pip install dairy-data-tools
+```
+
+```bash
+dairy-data-tools pen --folder "Farm Exports" --pen 21
+```
+
+Every question has a command: `dairy-data-tools --help` lists them. The ration change is `dairy-ration-change`.
+
+## What's in it
+
+Ask in plain words; the right skill picks itself. No commands to learn.
+
+| Skill | Ask it | What it does |
+| --- | --- | --- |
+| dairycomp-exports | "How do I get my cow list out of DairyComp?" "Write me a list of fresh cows in pen 1." "Which of these items shouldn't I use?" | The reports to save for this farm; DairyComp commands from plain English, checked against the farm's own items (SHOW, never LIST, which prints); what each item is |
+| ezfeed-exports | "Which EZfeed reports do you need?" | The reports to save and how they're read |
+| herd-explorer | "How is pen 21 doing?" "What happened to cow 1100?" | The herd, every pen, one pen, one cow: milk and ECM as a spread, events, lactations |
+| pen-feed | "What's pen 21's feed efficiency and IOFC?" "Is the feed loaded as called for?" | Each pen's cows joined to its feed: intake per cow, ECM per lb DM, cost per cwt, IOFC, NASEM's predicted intake; loading accuracy, refusals, consistency |
+| weekly-review | "Get me ready for Thursday's visit." "How are the fresh cows doing?" | Fresh cows, components and MUN, udder health, reproduction, who left, the pens' feed, and actions for the next visit |
+| ration-change | "Did pen 21's ration change work, or is it the season?" | The week before against the latest week, with the same weeks last year or another pen taken out |
+| balance-ration | "Balance pen 21's ration" | The free Dairy Ration Lab when it's connected; this kit never makes up a ration |
+
+Plain Python, checked number for number against the author's earlier R version: every count says what it's out of,
+milk is shown as a spread, and the farm is compared with itself, never with published targets.
+
+**A sample herd** (`sample-herd/`): a made-up California dairy's exports, to try every skill before using a real farm's.
+
+**Its neighbours**, separate tools from the same place: **BESTPRED** (USDA's best prediction of 305-day and
+mature-equivalent milk; in this marketplace, and at `https://bestpred.dairydatascience.com/mcp`) and the **Dairy Ration
+Lab** (a free ration balancer).
+
+## What it does with your files
+
+- The scripts read the export files where they are. They change nothing, keep nothing, and send nothing over the
+  internet. They use Python's standard library only.
+- In Claude's chat the files you attach and the scripts run in Claude's own code sandbox. What the agent reads goes to
+  the AI company as part of the conversation, as anything you attach does, unless you run a model on your own computer.
+- Event remarks, protocols and technician names are left out of what the scripts report, because they are free text
+  typed on the farm and could contain anything, including instructions aimed at an agent.
+- Nothing reads DairyComp's own files or backups, and no figure DairyComp calculates for itself (such as 305-day or
+  mature-equivalent milk) is used: the kit works from raw records.
+
+## Good to know
+
+- Weights are in pounds. Pens are compared with themselves and with the farm's other pens, never with published
+  targets.
+- It's a teaching and planning tool, not veterinary or nutrition advice: check anything before it changes what cows are
+  fed.
+- DairyComp 305 and EZfeed are Valley Ag Software's products; this project isn't affiliated with them.
+
+## Cite it
+
+If it helps your work, please cite it: GitHub's "Cite this repository" button gives the reference (`CITATION.cff`).
+
+## Licence
+
+Code under Apache-2.0 (`LICENSE`); the skills' text under CC BY 4.0 (`LICENSE-skills.md`). Questions and fixes:
+[issues](https://github.com/padge01/dairy-data-tools/issues).
+
+## Working on it
+
+- `plugins/dairy-data-tools/`: the plugin people install (skills, sample herd, README, licences).
+- `tools/dairy.py`, `tools/dairytools/` and the ration-change scripts in `tools/`: the one copy of the code;
+  `python tools/sync_scripts.py` copies it into each skill and writes this README. `pyproject.toml` builds the same
+  code as the `dairy-data-tools` package on PyPI.
+- `tools/make_sample_herd.py`: writes the sample herd (fixed seeds, same files every run).
+- `tests/`: `python -m pytest -q tests` (made-up files with known answers, the sample herd, the directory's file limits).

dairy_data_tools-0.2.0/README.md

@@ -0,0 +1,100 @@
+# Dairy Data Tools
+
+Free tools for dairy nutritionists and their AI agents. Give your agent a farm's own **DairyComp** and **EZfeed**
+exports and ask about a pen: how it's doing, what a ration change did, and whether it's just the season. The numbers
+come from small, tested scripts, not from the AI's guesswork.
+
+By Pádraig Lucey, MVB, MPVM, Ph.D. ([Dairy Data Science](https://dairydatascience.com)).
+
+## Get it
+
+**In the Claude app** (desktop or claude.ai, a paid plan with code execution on): Customize > Plugins > Add marketplace >
+`padge01/dairy-data-tools`, then Add **Dairy Data Tools**. Attach the farm's export files to a chat and ask.
+
+**In Claude Code:**
+
+```bash
+claude plugin marketplace add padge01/dairy-data-tools
+```
+
+```bash
+claude plugin install dairy-data-tools@dairy-data-tools
+```
+
+**In other agents** (Codex, Cursor, Gemini CLI and others that read Agent Skills):
+
+```bash
+npx skills add padge01/dairy-data-tools
+```
+
+**In Python, without an agent** (Python 3.10 or later; nothing else to install):
+
+```bash
+pip install dairy-data-tools
+```
+
+```bash
+dairy-data-tools pen --folder "Farm Exports" --pen 21
+```
+
+Every question has a command: `dairy-data-tools --help` lists them. The ration change is `dairy-ration-change`.
+
+## What's in it
+
+Ask in plain words; the right skill picks itself. No commands to learn.
+
+| Skill | Ask it | What it does |
+| --- | --- | --- |
+| dairycomp-exports | "How do I get my cow list out of DairyComp?" "Write me a list of fresh cows in pen 1." "Which of these items shouldn't I use?" | The reports to save for this farm; DairyComp commands from plain English, checked against the farm's own items (SHOW, never LIST, which prints); what each item is |
+| ezfeed-exports | "Which EZfeed reports do you need?" | The reports to save and how they're read |
+| herd-explorer | "How is pen 21 doing?" "What happened to cow 1100?" | The herd, every pen, one pen, one cow: milk and ECM as a spread, events, lactations |
+| pen-feed | "What's pen 21's feed efficiency and IOFC?" "Is the feed loaded as called for?" | Each pen's cows joined to its feed: intake per cow, ECM per lb DM, cost per cwt, IOFC, NASEM's predicted intake; loading accuracy, refusals, consistency |
+| weekly-review | "Get me ready for Thursday's visit." "How are the fresh cows doing?" | Fresh cows, components and MUN, udder health, reproduction, who left, the pens' feed, and actions for the next visit |
+| ration-change | "Did pen 21's ration change work, or is it the season?" | The week before against the latest week, with the same weeks last year or another pen taken out |
+| balance-ration | "Balance pen 21's ration" | The free Dairy Ration Lab when it's connected; this kit never makes up a ration |
+
+Plain Python, checked number for number against the author's earlier R version: every count says what it's out of,
+milk is shown as a spread, and the farm is compared with itself, never with published targets.
+
+**A sample herd** (`sample-herd/`): a made-up California dairy's exports, to try every skill before using a real farm's.
+
+**Its neighbours**, separate tools from the same place: **BESTPRED** (USDA's best prediction of 305-day and
+mature-equivalent milk; in this marketplace, and at `https://bestpred.dairydatascience.com/mcp`) and the **Dairy Ration
+Lab** (a free ration balancer).
+
+## What it does with your files
+
+- The scripts read the export files where they are. They change nothing, keep nothing, and send nothing over the
+  internet. They use Python's standard library only.
+- In Claude's chat the files you attach and the scripts run in Claude's own code sandbox. What the agent reads goes to
+  the AI company as part of the conversation, as anything you attach does, unless you run a model on your own computer.
+- Event remarks, protocols and technician names are left out of what the scripts report, because they are free text
+  typed on the farm and could contain anything, including instructions aimed at an agent.
+- Nothing reads DairyComp's own files or backups, and no figure DairyComp calculates for itself (such as 305-day or
+  mature-equivalent milk) is used: the kit works from raw records.
+
+## Good to know
+
+- Weights are in pounds. Pens are compared with themselves and with the farm's other pens, never with published
+  targets.
+- It's a teaching and planning tool, not veterinary or nutrition advice: check anything before it changes what cows are
+  fed.
+- DairyComp 305 and EZfeed are Valley Ag Software's products; this project isn't affiliated with them.
+
+## Cite it
+
+If it helps your work, please cite it: GitHub's "Cite this repository" button gives the reference (`CITATION.cff`).
+
+## Licence
+
+Code under Apache-2.0 (`LICENSE`); the skills' text under CC BY 4.0 (`LICENSE-skills.md`). Questions and fixes:
+[issues](https://github.com/padge01/dairy-data-tools/issues).
+
+## Working on it
+
+- `plugins/dairy-data-tools/`: the plugin people install (skills, sample herd, README, licences).
+- `tools/dairy.py`, `tools/dairytools/` and the ration-change scripts in `tools/`: the one copy of the code;
+  `python tools/sync_scripts.py` copies it into each skill and writes this README. `pyproject.toml` builds the same
+  code as the `dairy-data-tools` package on PyPI.
+- `tools/make_sample_herd.py`: writes the sample herd (fixed seeds, same files every run).
+- `tests/`: `python -m pytest -q tests` (made-up files with known answers, the sample herd, the directory's file limits).