Errors with runs in latest dev and main

[mikehsu90]

Hi! I’m picking up some work here and running into a few issues. I have checked out main and dev and have different issues when I change '_csv_all_variables.txt' to 'csv_all_variables.txt' and run python main.py

When I checkout from dev, I get the following errors:

[30-Jan-2026_Fri_12-59-55.259012][ERROR][freestall] No metadata found. No metadata is found for variable '_default_values' with given properties_blob_key _default_values_csv_properties. Consider adding variable information and properties to the metadata.
[30-Jan-2026_Fri_12-59-55.260328][ERROR][freestall] Emissions metadata load failure. Failed to load runtime metadata for 'EEE_econ'. Aborting emissions estimation.

When I checkout from main, I get the following errors:

[30-Jan-2026_Fri_12-41-30.104756][ERROR][default] units_key_error. Key 'avg_essential_amino_acid_requirement' not found in the units dictionary for variable 'AnimalModuleReporter.report_ration_interval_data.avg_rqmts_pen_1_GROWING'.
[30-Jan-2026_Fri_12-41-30.106391][ERROR][default] units_key_error. Key 'avg_essential_amino_acid_requirement' not found in the units dictionary for variable 'AnimalModuleReporter.report_ration_interval_data.avg_rqmts_pen_2_CLOSE_UP'.
[30-Jan-2026_Fri_12-41-30.108544][ERROR][default] units_key_error. Key 'avg_essential_amino_acid_requirement' not found in the units dictionary for variable 'AnimalModuleReporter.report_ration_interval_data.avg_rqmts_pen_3_LAC_COW'.

Any advice on how to correct this (or if I should be using dev or main or something else)? When I posted this #2607 for a similar error a few months ago I was able to get a fix (many thanks!) @PooyaHekmati @KFosterReed @ew3361zh

[KFosterReed]

Hi @mikehsu90!

Thanks for your questions! We are inching closer to updating the main branch so I would recommend working on dev for now and then when we update main in the next few weeks, switch over to main. The errors you are getting on dev are related to the data required for the upcoming economics analyses so aren't actually stopping the biophyiscal module from working. You should be able to get outputs from the simulation you ran on dev even though it produced those errors.

Another note that I am sure you are aware by now is that the filter for 'csv_all_variables.txt' will give you A LOT of data. I'm attaching an emissions focused report filter (report_example_filter.json) and a soil N cycling report filter (report_soil_N_cycling.json) that I have used in the recent past and might help you get a jump start on collecting the outputs you are interested in.

Be warned that depending on the simulation you run, these filters might cause some ReportGenerator errors that are likely because the simulation you are running isn't producing what is being filtered for. As you get started, I would ignore the report generator errors. Then ask you get more familiar, you will be able to know if those errors are because the filter is configured incorrectly, the scenario you are running is correctly not producing an certain output, or if there is an error in the ReportGenerator itself.

Last note for today is that we have some awesome User Guide videos that are almost ready to share so be on the lookout for those soon too!
report_example_filter.json
report_soil_N_cycling.json