8000 Ship the grower report, batch sheet and tank grouping in the package (#79) by rafatahmed · Pull Request #83 · rafatahmed/Flahax · GitHub
[go: up one dir, main page]

Skip to content

Ship the grower report, batch sheet and tank grouping in the package (#79) - #83

Merged
rafatahmed merged 1 commit into
mainfrom
feat/grower-outputs
Oct 22, 2026
Merged

rafatahmed merged 1 commit into
mainfrom
feat/grower-outputs

Conversation

@rafatahmed
Copy link
Copy Markdown
Owner

Closes #79.

What ships

  • flahax batch: one formula (packaged, or --targets) and one water (ro or a measured analysis JSON, closed at its measured pH) produce report.html, batch-sheet.html and summary.json. The pH plan is coupled to the recipe: acids come from your certificate values via --acid HNO3:0.60:1.37, and the packaged bases are always evaluated. Exit codes: 0 ready or review, 3 blocked, 1 input error.
  • summarize_batch, render_report and render_batch_sheet do the same from any plan_fertilizer_workflow result. When a reagent is selected, the sheet weighs the refitted recipe that counts the reagent's nutrients. A blocked plan shows the acid-free recipe and the phases that block it.
  • group_tanks applies Yara p. 65 (read with p. 63) as three composition rules: Ca with phosphate, Ca with sulfate, Mg with phosphate. A test shows these reproduce the table's 12 incompatible pairs exactly.
  • Owner rule: micronutrients and chelates go to tank A with calcium and stay out of phosphate concentrates. Tank A is never acidified, and pH reagents get their own channel. Your own compatibilityRule records apply on top.
  • default_compatibility_rules gives plan_stocks the same rules as records.
  • The tomato examples (Add simple and advanced tomato examples with a report and grower batch sheets #73) now use the packaged grouping, so micronutrients no longer show as "Not in table". Their acid wording is updated for Positive SI of slow-forming phases (hydroxylapatite, MnHPO4) blocks every acid plan #78: nitric needs review, phosphoric is refused for its P.
  • New docs page: Batch report, sheet and tanks.

Not covered

Concentrate solubility is still not checked, and the outputs say so.

Validation

  • FLAHAX_REQUIRE_PHREEQC=1 unittest: 405 tests OK (1 skip, the built-docs test, which passes after the build)
  • verify_distribution: PASS
  • sphinx -W: clean
  • API reference --check: ok
  • No CRLF line endings

…79)

An installed FlahaX gave growers JSON: the report, the batch sheet and the
concentrate-tank grouping existed only as example code (#73).

- flahax batch: one formula (packaged, or your targets) and one water (ro, or a
  measured analysis closed at its pH) to report.html, batch-sheet.html and
  summary.json, with the coupled pH plan (acids from certificate values, plus
  the packaged bases). Exit 0 ready/review, 3 blocked, 1 input error.
- summarize_batch, render_report, render_batch_sheet: the same from any
  plan_fertilizer_workflow result. With a selected reagent the sheet weighs the
  refitted recipe that counts its nutrients; a blocked plan shows the acid-free
  recipe and the phases that block it. Offline HTML, no script.
- group_tanks: the Yara p. 65 compatibility table (read with p. 63) as three
  composition rules (Ca-phosphate, Ca-sulfate, Mg-phosphate), which reproduce
  its twelve incompatible pairs exactly. Owner rule: micronutrients and
  chelates go to tank A with calcium and stay out of phosphate concentrates;
  tank A is never acidified; pH reagents get their own channel. User
  compatibilityRule records apply on top. default_compatibility_rules gives
  plan_stocks the same rules.
- Tomato examples use the packaged grouping (micronutrients no longer 'Not in
  table') and their acid text reflects #78. Stock solubility is still not
  checked, and the outputs say so.
@read-the-docs-community
Copy link
Copy Markdown

Documentation build overview

📚 Flahax | 🛠️ Build #35321500 | 📁 Comparing 56467e0 against latest (5c325b1)

  🔍 Preview build  

4 files changed
+ guide/grower-outputs.html
± changelog.html
± api/reference.html
± guide/usage.html

@rafatahmed
rafatahmed merged commit a07aab6 into main Oct 22, 2026
6 checks passed
@rafatahmed
rafatahmed deleted the feat/grower-outputs branch October 22, 2026 10:03
@rafatahmed rafatahmed self-assigned this Oct 23, 2026
rafatahmed added a commit that referenced this pull request Nov 7, 2026
Ship the grower report, batch sheet and tank grouping in the package (#79)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Grower outputs (report, batch sheet, tank grouping) are not in the installed package

1 participant

0