Adjusting Seed Sheet with Multiplication Factors Across Multiple Scenarios

[[email protected]]

Hi, Happy New Year!

I have defined the baseline learning rate in the baseline scenario file (Scen... rather than BY file). Now, I need to model various other scenarios by applying a multiplication factor (e.g., *1.0, *2.0) to update those values. However, I would like to keep the seed sheet aligned with the baseline scenario. Is this achievable?

Thank you!

[KanORS-AssistGPT]

Yes, you can achieve this by using the sourcescen field in a ~UPD table. This approach allows you to reference the baseline scenario for seed values while applying the desired multiplication factors in other scenarios. Here’s how you can do it:

1. Defining the Baseline Scenario
   Ensure the baseline learning rates are defined in the baseline scenario file (e.g., BaselineScen). This scenario will act as the source for seed values.
   
   


2. Setting Up the ~UPD Table
   In the new scenarios where you want to apply the multiplication factor, create a ~UPD table. Use the sourcescen field to point to the baseline scenario and apply the adjustment factor.
   
   Below are examples of how your ~UPD tables should look:
   
   UPD Table for Scenario 1:
   
   
   UPD Table for Scenario 2:
   
   
   


3. How It Works
   The sourcescen field ensures that the seed values for ACT_COST are sourced directly from the BaselineScen.
   The val field applies the desired multiplication factor (*0.5 to halve the values in Scenario 1 and *2 to double them in Scenario 2).
   This keeps your baseline definitions untouched while enabling flexible scenario analysis.
   
   


4. Verification
   After implementing the ~UPD tables, verify that:   
    The baseline values are correctly referenced from BaselineScen.
   The multiplication factors are applied as expected in the outputs of each scenario.
   

This method is efficient and aligns perfectly with the intended functionality of Veda's sourcescen field. Let us know if you need further clarification or help setting this up! ?

For your information, this can also be achieved using the ~TFM_Fill tag. However, the ~TFM_Fill tag is typically used when the UPD tag cannot perform the required operation, such as aggregations like SUM, AVERAGE, or COUNT.