Skip to main content

MCAL Test Runs Feedback - CCR

Testing FeedbackBudget Filings

Expiring on Dec 31st, 2025 - MPs with legacy DeliveryType (ex. DnDeemDI) and MeasImpactType (ex. Deem-WP-FuelSub) still yield errors. Manual fix is to overwrite this fields with new format CEI values (ex. DI, Deem). Changing Impact Type for FuelSubs measures then requires adding a FuelID as flag for AC to work as intended. Latest PCG meeting advise to leave FuelID blank and MeasImpactType will flag for FuelSub measures.

eTRM - SWWH006-08 reports WtrHt-Com and RUL = 5 yrs. MP needs update to WtrHt-Com-Gas and RUL = 4.33 yrs (Manual Fix for now). Also, SWFS022-04 and SWFS021-05 have expired TechTypes in the 2026 MPs. (OvenConv and Fryer, vs OvenConv-Gas and Fryer-Gas).

From above, outputs metrics, such as TSB calculate different (CEI Budget Application Filings vs CEDARS Production; Job ID 1350 vs 105441).

I understand there are a lot of updates happening in parallel with testing, so I am just asking if the above is on the radar for update and is just pending deployment. Thanks!

Posted by fmonterroso ·
Status: Completed15 comments

Log in to comment and vote

Comments15

  • cedars team

    Team•

    Aug 21, 2025

    @fmonterroso Hi Felix,

    I hope the issue you’re experiencing is simply due to some unfortunate timing with your filings in the different testing environments. The MCAL work was conducted on cedars-3, not cedars-2, which is likely why you encountered difficulties testing yesterday.

    Now that we have freshly cloned cedars-2 after the production deployment, I believe you shouldn’t face any issues. However, please let me know if you encounter anything unexpected.

    • fmonterroso

      •

      Aug 21, 2025

      Thank you CEDARS Team. This morning I was able to initiative the budget filings for both 2026 and 2027 in CEDARS2.

  • Jennifer Scheuerell

    Team•

    Aug 12, 2025

    Hi @fmonterroso I just applied the update to cedars-2 to allow the older measure package values, can you please retest?

    • fmonterroso

      •

      Aug 12, 2025

      Thanks Jen, I will try this and let you know.

      • fmonterroso

        •

        Aug 13, 2025

        Error when trying to create Budget Filing for 2026 MCAL in CEDARS2

        • cedars team

          Team•

          Aug 13, 2025

          Hi @fmonterroso , did you want to try testing in cedars-3 as it’s using the same version of CET that now allow the older measure packages to pass validation.

          We’ll look into the error for cedars-2 in the meantime.

          - Sonja

          • fmonterroso

            •

            Aug 13, 2025

            Hi Sonja. I was getting the errors in CEDARS3 yesterday. I tried again today (in CEDARS3) and I am still getting the same errors. Problems with Delivery Type and Measure Impact Type for SWWH027-06.

            Job ID 1359.

            • fmonterroso

              •

              Aug 13, 2025

              For planning purposes, do we know when to expect CEDARS to be fully ready for MCAL submissions?

              • cedars team

                Team•

                Aug 14, 2025

                We aim to have MCAL deployed by Friday morning (PDT); however, if we are unable to do so, it will be rescheduled for Monday morning. We have freshly cloned to cedars-3. Could you please test again for us?

                • fmonterroso

                  •

                  Aug 14, 2025

                  Great, thanks! I initiated a new budget filling on CEDARS3 after the update you guys did and I was able to run the previous CET file successfully (Job ID 1345).

                  I did notice though, that the outputs don’t match what I am getting from CEDARS production. CEDARS3 seem to be referencing a 2026AC file last updated on April 9 while production is referencing one from April 22. Could this be the reason of why I am getting different CET outputs?

                  • fmonterroso

                    •

                    Aug 14, 2025

                    Also, I tested year 2027. It ran but only after I did a manual update of the CET input field label as “PA” to IOU_AC_Territory. Error Given:

                    Measure.csv: Column name mismatch:

                    • Missing columns: ['IOU_AC_Territory']

                    • Unexpected columns: ['PA']

                    • cedars team

                      Team•

                      Aug 14, 2025

                      @fmonterroso the field rename measure.PA to measure.IOU_AC_Territory is expected for this update.

                      I can follow up more about the different outputs. Was there specific outputs you were concerned about?

                      What I do know is that the gas avoided cost data for production CET runs are not the same as the v25.1 gas avoided cost data. You should expect different gas benefits when v25.1 goes out to production. cedars-3 is using CET 25.1

                      Thanks,
                      Sonja

                      • fmonterroso

                        •

                        Aug 19, 2025

                        I am unable to initiate a filing year for 2026 in CEDARS2. Also, 2027 doesn’t even have an initiation option. Can you advise? Thanks!

                        • fmonterroso

                          •

                          Aug 20, 2025

                          @Sonja , here is the inquiry from CCR regarding initiation of a filing year in CEDARS2.

                          • cedars team

                            Team•

                            Aug 21, 2025

                            Thanks @fmonterroso and apologies for missing this message. The team is working on the issue. I’ll report back as soon as I know more.