When inputting destruction parameters, specifically on the destruction priorities screen, in NAADSM 3.1.23, I encounter an error in a message box:
"List index out of bounds (0)"
What is causing this?
This error is caused, typically, because no production types have been previously identified as selected for destruction on the "Production type settings for destruction" input screen under the "Destruction" menu item.
If moving from screen-to-screen during the scenario parameters setup process, this error can happen because the "Production type settings for destruction" input screen is after, instead of before, the "Destruction priorities" input screen.
Recommended procedure/fix to avoid this problem in 3.1.23:
1) Select the global destruction setting from the first destruction input screen, i.e. "Use destruction for disease control..." setting.
2) Save the scenario file.
3) Export the parameters, and herds files to XML.
4) Close the scenario.
5) Import the parameters, and herds files from XML.
This process corrects the issue internally in the software by rebuilding the index, for which the "index out of bounds" error was raised.
Alternate solution:
If none of the fixes from 3.1.21 to 3.1.23 are an issue for your scenario, then you may export your existing 3.1.23 scenario file and herds file to XML and import them into version 3.1.21 and use that version for simulation. (Be sure to check your parameters again, to be sure everything is as you want it to be, before running.)
I am having the same problem when setting vaccination priorities, but I haven't been able to get this solution to work. Do you have any other ideas about how to proceed?
I'm afraid that there are no good work-arounds, other than those that Shaun described. If they aren't working for you, I'm not sure what else to suggest.
The good news, however, is that this bug will be fixed in the forthcoming NAADSM version 3.1.24. We are finishing testing of this version now, and it should be publicly available early next week.
We're sorry for the problems, and we appreciate your patience. You should be back in business in just a few days.
Re: Destruction Priorities Input Screen Error (NAADSM 3.1.23)
Re: Destruction Priorities Input Screen Error (NAADSM 3.1.23)
Re: Destruction Priorities Input Screen Error (NAADSM 3.1.23)
I'm afraid that there are no good work-arounds, other than those that Shaun described. If they aren't working for you, I'm not sure what else to suggest.
The good news, however, is that this bug will be fixed in the forthcoming NAADSM version 3.1.24. We are finishing testing of this version now, and it should be publicly available early next week.
We're sorry for the problems, and we appreciate your patience. You should be back in business in just a few days.
Thanks,
Aaron
Re: Destruction Priorities Input Screen Error (NAADSM 3.1.23)
For those who've not yet noticed, this error is now fixed in NAADSM 2.1.24.
Thanks,
Aaron