Sorry Ted but I like Telly's idea. Let me suggest the following refinements:
1) Put a special button called Sensitivity Studies on the main page. Make no changes to the basic FIRECalc entries.
2) In the sensitivity study section list two sets of entries corresponding to the calendar years that are covered by data. One set of entries would cover 1871 through 2002 and that would refer to the data that already exists in FIRECalc. The other section would be next to it and it would be the what if entries. It would start with default values equal to the current data set. If someone wanted to replace years 1940-1945 with data from 1960-1965 he would replace the 1940 default value with 1960. He would replace the 1941 default value with 1961 and so forth.
3) To satisfy Telly's wishes, include a set of entries through 2042 (or some other future date) with additional, dummy default values such as the 1871-1911 that Telly mentioned. But be sure that the user could also change these projections aka guesses.
4) From a programming standpoint, you would simply be replacing the table that has your historical data with data selected from different dates.
5) Limit changes to replacing data for one year with existing data from another year. This makes the programming task manageable.
6) Be sure that any calculations remain in the special section. Keep it as idiot proof as possible. (Understanding, of course, that nature is always able to supply a superior idiot.)
Have fun.
John R.
1) Put a special button called Sensitivity Studies on the main page. Make no changes to the basic FIRECalc entries.
2) In the sensitivity study section list two sets of entries corresponding to the calendar years that are covered by data. One set of entries would cover 1871 through 2002 and that would refer to the data that already exists in FIRECalc. The other section would be next to it and it would be the what if entries. It would start with default values equal to the current data set. If someone wanted to replace years 1940-1945 with data from 1960-1965 he would replace the 1940 default value with 1960. He would replace the 1941 default value with 1961 and so forth.
3) To satisfy Telly's wishes, include a set of entries through 2042 (or some other future date) with additional, dummy default values such as the 1871-1911 that Telly mentioned. But be sure that the user could also change these projections aka guesses.
4) From a programming standpoint, you would simply be replacing the table that has your historical data with data selected from different dates.
5) Limit changes to replacing data for one year with existing data from another year. This makes the programming task manageable.
6) Be sure that any calculations remain in the special section. Keep it as idiot proof as possible. (Understanding, of course, that nature is always able to supply a superior idiot.)
Have fun.
John R.