Knowledge Base
Search…
0.5.1
Launched on 7/9/2020

Change Summary πŸš€β€‹

  • Quantification improvements
    • Error handling improvements
    • Misc improvements
  • Quantification bug fixes
  • Quantification changes
  • Experimental features opt-in πŸš€β€‹
  • Smart Defaults beta launch (requires opt-in) πŸš€β€‹
  • Smart Defaults changes
  • Smart Defaults documentation πŸ“–
  • Smart Defaults bug fixes
  • Intake sheet changes
  • Data import bug fixes
  • Marketplace changes

Postponed changes

Cancelled changes

Quantification improvements

Error handling improvements

There have been some significant improvements made to the way we detect errors in a supplier's intake sheet. This is in part thanks to a new feature from COMET farm that allows error trapping when they detect errors on their side of things.
Currently, most errors are handled in the app's UI using a temporary solution. Documenting and improving this UX is currently in the roadmap. Stay tuned!

Misc improvements

Suppliers no longer need to specify more than 10 years of post-switch year future data
A requirement of the COMET farm model is that 10 years of future planned data is needed. However, in the intake sheet used by the app, we allow the supplier to specify more than 10 years of planned data as each additional year will be used in each successive year to create a new quantification projection. Due to this, we were previously parsing and detecting issues in all future years, regardless of whether it was required for the current quantification run or not. As this was prone to issues when running quantification, we have removed an existing requirement that requires users to have more than 10 years of data after the switch year. That said, it is recommended that users still fill in as many years of future data with as much data as possible.

Quantification bug fixes

  • Fixed a bug disallowing successive perennials to be defined
  • Fixed a bug that caused some perennials to not be detected correctly
  • Fixed a bug causing the quantification page to result in a 500 error when new fields had been added since the last time quantification had been run

Quantification changes

Due to a change in the COMET farm API specification, the following adjustments were made:
  • Only one liming event per crop year is allowed
  • Only one burning event per crop year is allowed
  • Liming is now ignored when set to "None" in the sheet instead of sending it to COMET via the input file

Experimental features opt-in ​

Users can now opt-in to experimental features. To do so, please reach out to [email protected]​
Currently, experimental features include:

Smart Defaults beta launch (requires opt-in)

Users can now opt-in to Smart Defaults. See here for more information on how to do so.

Smart Defaults changes

Users can now specify the lbs/n per acre of fertilization used. As such, users can no longer specify "Total amount applied", "Density (lbs / gallon)", "% Nitrogen", or "% Ammonium" during Smart Defaults. That said, users can still customize this information in the sheet manually if there is reason to do so.

Smart Defaults documentation

Check out the new Smart Defaults guide here!

Smart Defaults bug fixes

  • Fixed a bug that was causing large projects (50+ field-sets) to have issues when trying to use smart defaults

Intake sheet changes

  • The default fertilizer classification has been changed from "Ammonium Nitrate (34-0-0)" to "Mixed Blends". This should not cause any changes in quantification as the COMET farm model only uses this data to calculate nitrogen stock changes (which is not currently considered for NRT quantification)

Data import bug fixes

  • Fixed a bug causing large import files (projects containing 50+ field-sets) to have issues when importing data. This includes issues where:
    • Data was not imported into the sheet
    • A 422 error was reported
  • A limitation of the intake sheet is that the Google Sheets API only allows named ranges of a certain maximum character length. This was causing issues with some Import files. As such, we are now truncating such field-set names defined in import files.
  • Data import files are now correctly checked for duplicate field-set names. Duplicate names are not allowed-- this is a limitation of the Google Sheets API.

Marketplace changes

  • An additional number of NRTs have been unlocked for sale in the marketplace
​
​
Last modified 1yr ago