Changes

m
Line 322: Line 322:  
# frequency < 1   
 
# frequency < 1   
 
   
 
   
If the frequency is set to 1 then the RCC will more closely align with how you probably set up your main CBA (e.g., 10 years of impact estimates spread over 10 columns). Recall from above that upfront activities are always assumed to have an annual frequency of 1 and that upfront impacts are assumed to be incurred at the beginning of every period. Upfront activities that start at the start of the analytical period will have 11 total periods over a 10-year timeframe (0 ,1, 2, 3, 4, 5, 6, 7, 8, 9, 10). Conversely, ongoing costs are assumed to be incurred at the end of every period, so an ongoing cost with a frequency of 1 that lasts 10 years will have 10 total periods.     
+
If the frequency is set to 1 then the RCC will more closely align with how you probably set up your main CBA (e.g., 10 years of impact estimates spread over 10 columns).      
 
   
 
   
 
However, if you enter an annual frequency of 1,200, then you are telling the RCC that you want to split every single year into 1,200 evenly spaced periods, in which the stakeholder count must be estimated and impacts must be discounted back to the PV base. Is that really what you want to do? That is probably not how you set up your main CBA. With 1,200 evenly spaced periods that means the RCC will estimate the stakeholder count more than 3 times per day. There is nothing mathematically wrong with this, however it is computationally intensive and it may not be necessary.     
 
However, if you enter an annual frequency of 1,200, then you are telling the RCC that you want to split every single year into 1,200 evenly spaced periods, in which the stakeholder count must be estimated and impacts must be discounted back to the PV base. Is that really what you want to do? That is probably not how you set up your main CBA. With 1,200 evenly spaced periods that means the RCC will estimate the stakeholder count more than 3 times per day. There is nothing mathematically wrong with this, however it is computationally intensive and it may not be necessary.     
136

edits