This is to provide documentation only of previous process. When a user would check the create Map Output option, this is what they would get.
A zipped folder would go to the desktop defaulting to the name of the scenario.
within that folder would be sub directories for each iteration run.
Each iteration would have a set of files.
DayPremStat - a comma delimited file with the fields
Day, prem, status, latitude, longitude, proddesc, size
data for day 0 was initial disease status (susceptible, latent, subclinical, clinical, destroyed, vaccine immune, nat immune)
then day would show as status change through iteration, only days with a prem with a change
data for day 9999 was last day with status
there were also files with lookup values
Days, one column that counted the number of days in that iteration and added the 9999
Max, with fields "NUMDAYS","NUMSTAT","NUMPREM","NUMPROD","NUMDAYPREMSTATUS"
Prod with field ProdType
Stat with field Status
I think this was done because file sizes had the possibility of overwhelming the database.
This is to provide documentation only of previous process. When a user would check the create Map Output option, this is what they would get. A zipped folder would go to the desktop defaulting to the name of the scenario. within that folder would be sub directories for each iteration run. Each iteration would have a set of files. DayPremStat - a comma delimited file with the fields Day, prem, status, latitude, longitude, proddesc, size data for day 0 was initial disease status (susceptible, latent, subclinical, clinical, destroyed, vaccine immune, nat immune) then day would show as status change through iteration, only days with a prem with a change data for day 9999 was last day with status there were also files with lookup values Days, one column that counted the number of days in that iteration and added the 9999 Max, with fields "NUMDAYS","NUMSTAT","NUMPREM","NUMPROD","NUMDAYPREMSTATUS" Prod with field ProdType Stat with field Status
I think this was done because file sizes had the possibility of overwhelming the database.