08-08-2019, 09:33 PM
Hi all (apologies for another question in quick succession!),
When running TIAM with Price-Elastic demand, we're currently getting a whole set of warnings, and we're not sure where they're coming from.
We run Price-Elastic demand as normal, and we get normal completion of the run. The results can be seen in BE and look sensible (i.e. there is some reduction in demand due to mitigation).
However, I also get a file called QA_Check (see attached file), which raises a number of warnings. Briefly summarised, they are:
1. *** Delayed Process but PASTInvestment
2. *** Elastic Demand but either COM_BPRICE/ELAST/VOC missing
3. *** Demand: DEM commodity with missing COM_PROJ Projection
4. *** IRE Process with invalid Parameters
5. *** RPC in TOP not found in any ACTFLO/FLO_SHAR/FLO_FUNC/FLO_SUM
6. *** Empty Group in FLO_SUM/FLO_FUNC/FLO_SHAR
I'm aware that's a lot of warning messages, and I may not have provided the requisite information to allow someone to give a solution, but if anyone has any idea about the origin of any of these warnings, and how we could deal with them, that would be really appreciated.
Many thanks,
Neil
When running TIAM with Price-Elastic demand, we're currently getting a whole set of warnings, and we're not sure where they're coming from.
We run Price-Elastic demand as normal, and we get normal completion of the run. The results can be seen in BE and look sensible (i.e. there is some reduction in demand due to mitigation).
However, I also get a file called QA_Check (see attached file), which raises a number of warnings. Briefly summarised, they are:
1. *** Delayed Process but PASTInvestment
2. *** Elastic Demand but either COM_BPRICE/ELAST/VOC missing
3. *** Demand: DEM commodity with missing COM_PROJ Projection
4. *** IRE Process with invalid Parameters
5. *** RPC in TOP not found in any ACTFLO/FLO_SHAR/FLO_FUNC/FLO_SUM
6. *** Empty Group in FLO_SUM/FLO_FUNC/FLO_SHAR
I'm aware that's a lot of warning messages, and I may not have provided the requisite information to allow someone to give a solution, but if anyone has any idea about the origin of any of these warnings, and how we could deal with them, that would be really appreciated.
Many thanks,
Neil