Budget Filing Module vs CET TSB Different
In the attached input batch, I go slightly different TSB for a handful of the CEInputIDs. The impact is small ($1.59) but it is confusing why it is different.
- Select the module in CEDARS
- Select user type
In the attached input batch, I go slightly different TSB for a handful of the CEInputIDs. The impact is small ($1.59) but it is confusing why it is different.
Log in to comment and vote
Comments25
Oct 27, 2025
PinnedHi @JakeRichardson and @ggreen
I took the 2026 SW PGE input Jake had run and trimmed the measure and program cost files down to just one record each for testing purposes. The measure record I kept is SW-2026-SW_CSA_Bldg-320, one of the fifteen measure records Jake identified as different in his comparison. I revised the IDs to make them CPSF (an inactive PA we use for testing sometimes) so I could upload to an empty budget filing and only see the one record to make the CET run comparison straightforward.
When I uploaded the same input file to the CET and MCAL and then downloaded the saved input files for each from CEDARS, I did not see any rounding in the input files saved and made available by CEDARS. We have also found no code that would round input files in our review. The CET outputs for the MCAL and CET runs are exactly the same.
I believe this issue is resolved. Can you please let me know if you agree? I can share my test inputs/outputs if you’d like to review the files. In case it helps, I ran this latest round of tests today on cedars-3.
Jake Richardson (PG&E)
Oct 30, 2025
I was able to tie off my MCAL last night - if you can reopen our 2026 SW budget filings in CEDARS-3 I will run my files thru to test and provide a summary of the results.
cedars team
Oct 31, 2025
@JakeRichardson I can reopen your 2026 Statewide budget filings in
cedars-3for testing, but just a heads-up that the environment has a few moving parts today while other work is being tested. The Statewide module itself should be stable, though if you’d prefer to avoid any potential disruption, we can hold off until Monday and reservecedars-3specifically for your testing.Jake Richardson (PG&E)
Oct 31, 2025
No rush - I’m OK if we do this testing after MCALs are filed
Jake Richardson (PG&E)
Nov 7, 2025
I’m willing to test this now, as soon as SW is open in CEDARS-3
Oct 8, 2025
PinnedHey @JakeRichardson and @ggreen the updated dashboard TSB values are now ready for review on
cedars-3. Please let us know if they are what you would expect or if you are still seeing what looks like a rounding issue. Thanks, SonjaJake Richardson (PG&E)
Oct 8, 2025
Can I confirm - am I supposed to re-run the CETs? I still see the small rounding in our C&S programs but I wouldn’t expect it to be resolved unless I re-run the CETs (because it was confirmed that the CET inputs were being rounded in the budget filing module).
cedars team
Oct 8, 2025
@JakeRichardson I just checked and Jenn is still working on this, so it’s not quite ready for testing yet. Sorry for the confusion. We’ll let you know once it’s available.
ggreen
Oct 10, 2025
Unable to attach my excel file to show audit. I did a comparison on the dashboard results for ‘program summary’ and ‘segment summary’ vs our internal system using the production CET tool database.
I used to have all ratios, budgets and savings matching between systems. It was just TSB that was off.
TSB is better now for SW allocated programs, but still see whole number deltas for local programs. Also, the SCT values no longer match at all.
For segment summary results, my ratios no longer match at the segment level. CEDARS also has a duplicate line for Market Support that is blank across all fields when you perform a download for purposes of system audits.
cedars team
Oct 17, 2025
Thanks for the detail @ggreen, I've checked production for the issue with the duplicate Market Support line in the segment summary download, and it looks like this was resolved at the end of last week when we pushed a set of fixes into production.
Work is still ongoing for the TSB rounding discrepancies you're seeing, and we’re also reviewing the SCT mismatch you mentioned
We'll keep you posted as soon as we have an update ready for testing
cedars team
Sep 24, 2025
Hi @ggreen I’ve merged your ticket here as it looks to be a duplicate of an issue Jenn is already investigating. Thanks for sharing the additional details.
Jake Richardson (PG&E)
Sep 12, 2025
These are the CEInputIDs with differences, just 15 out of 14.5k:
CET_ID
SW-2026-SW_CSA_Bldg-320
SW-2026-SW_CSA_Bldg-322
SW-2026-SW_CSA_Bldg-334
SW-2026-SW_CSA_Bldg-335
SW-2026-SW_CSA_Bldg-569
SW-2026-SW_CSA_Bldg-571
SW-2026-SW_CSA_Bldg-583
SW-2026-SW_CSA_Bldg-584
SW-2026-SW_CSA_Bldg-71
SW-2026-SW_CSA_Bldg-73
SW-2026-SW_CSA_Bldg-818
SW-2026-SW_CSA_Bldg-820
SW-2026-SW_CSA_Bldg-832
SW-2026-SW_CSA_Bldg-833
Jennifer Scheuerell
Sep 23, 2025
Hi @JakeRichardson,
Thank you for your patience as we investigated this variance. We are seeing that the kW unit energy savings for the records with different TSB are rounded differently in the input files and that appears to be the source of the variation. For example, for record SW-2026-SW_CSA_Bldg-322 the UESkW value in the input file that ran through the CET is 0.00000140306 and the number in the input file that ran through the budget filing module is 0.0000014.
Jenn
Jake Richardson (PG&E)
Sep 23, 2025
Any chance the inputs are being rounded on the CEDARS side before being sent to the CET? I ran the exact same .zip file thru both modules.
Jake
Jake Richardson (PG&E)
Sep 29, 2025
@Jennifer Scheuerell - just checking back in on this
Jennifer Scheuerell
Oct 1, 2025
@JakeRichardson @ggreen I’m sorry for the slow reply, it looks like Cedars is rounding decimals on the input file. We are working on a fix. Thank you both for your testing and details, much appreciated.
ggreen
Oct 7, 2025
This is helpful information, thanks!
ggreen
Sep 24, 2025
•Merged request
•1 vote
TSB Rounding Issues in Budget Filing Module?
SDGE is noting discrepancies as great as 1.85 for TSB values in our Statewide and Local Programs of the Budget Filing module Program Summary table download.
SDGE feels this may be attributed to rounding values that are different between the CET Tool vs the Budget Filing module for TSB.
SDGE has observed exact matches for all CE Ratio values, so is isolated to just TSB.
ggreen
Sep 30, 2025
SDGE has been further investigating this. It appears that CEDARS uses a decimal precision of 6 decimal places for the CEI? When we applied that to our internal system, we achieved an almost exact match for TSB at the program summary level. However, this disrupted the TSB value at the portfolio level which was previously an exact match.
Question: Does CEDARS round/truncate any of the CEI inputs at upload, during processing, or at the end for CE outputs?
cedars team
Oct 29, 2025
@ggreen could you please share your testing files.
cedars team
Nov 12, 2025
@JakeRichardson I’ve reopened Statewide budget filing for 2026 in
cedars-3for you.Thanks, Sonja
Jake Richardson (PG&E)
Nov 14, 2025
I can’t seem to reproduce the error now. I’d just go ahead and close this.
cedars team
Nov 17, 2025
Thanks for checking.