Standardize 1000 tons to tons in fgd_sorbent_consumption column

[msa856]

Overview

Closes #XXXX.

What problem does this address?

What did you change?

Documentation

Make sure to update relevant aspects of the documentation:

• Update the release notes: reference the PR and related issues.
• Update relevant Data Source jinja templates (see docs/data_sources/templates).
• Update relevant table or source description metadata (see src/metadata).
• Review and update any other aspects of the documentation that might be affected by this PR.

Testing

How did you make sure this worked? How can a reviewer verify this?

To-do list

• If updating analyses or data processing functions: make sure to update row count expectations in dbt tests.
• Run make pytest-coverage locally to ensure that the merge queue will accept your PR.
• Review the PR yourself and call out any questions or issues you have.
• For minor ETL changes or data additions, once make pytest-coverage passes, make sure you have a fresh full PUDL DB downloaded locally, materialize new/changed assets and all their downstream assets and run relevant data validation tests using pytest and --live-dbs.
• For bigger ETL or data changes run the full ETL locally and then run the data validations using make pytest-validate.
• Alternatively, run the build-deploy-pudl GitHub Action manually.

[jdangerx]

You're headed in the right direction! I think the main thing you still need to do is update the alembic schema.

Then you can materialize the asset in dagster and then check if the output data is actually in tons instead of kilotons!

[jdangerx]

I suppose this is actually the nearest 100 tons? Looking at the PUDL viewer it does seem like the original values are to the nearest 0.1 thousand (disregarding the floating point error...):

[msa856]

I see what you mean. In tons it would be 108,599.99 for the first value and we want it rounded to 108600 (re: comment below), correct?

[msa856]

I updated the alembic schema, ran dagster dev, but materializing _core_eia923__fdg_operation_maintenance failed because of the asset check (continuity check). Should I change that too prior to materialization (src/pudl/transform/eia923.py)?

[jdangerx]

And if this is to the nearest 100 tons we should probably round this appropriately.

[msa856]

I was able to load _core_eia923__fgd_operation_maintenance into my notebook and it seemed to be rounded already (I don't know why that differs from what you showed in the viewer). Do you recommend another line of code to ensure it's always rounded?

Also, I am not sure if this is the best place to ask but was curious: does etl.defs bypass the asset checks? Is that why I can see the updated column whereas in Dagster I cannot?