Just want to say Hello!

Component:User interface
Category:bug report

In the "Zone parameters" window, users specify a multiplier for the probability of detection, which then applies to clinical units inside the designated zone.

When this parameter is validated before a scenario is run, the validation routine does not allow users to specify a value of 0, and generates an error. (Note that a multiplier of 0 would mean that no detection could occur in the designated zone.)

It has been suggested that a multiplier of 0 may be a legitimate value for some (very unusual) applications. Rather than generate an error, the GUI could perhaps generate a warning for any multiplier with a value less than 1.

Such a warning is relatively easy to implement when the user is entering values, but it would be more difficult to impose when parameters are validated before allowing the user to run a scenario. Validation of all model parameters in the GUI is currently done on a "yes/no" basis: "yes, the parameters are valid, therefore run the model" or "no, parameters are not valid, therefore do not run the model". A nontrivial amount of additional plumbing would be required to offer a third option, "the parameters are valid but look a little funky, therefore warn the user and ask whether to run the model".

I suggest the following two steps:

  • Have the GUI display a warning when values are entered or edited
  • Have the core model generate warning messages (similar to the existing "missing parameter" messages) when it encounters a multiplier with a value of less than 1. These messages are sent to the GUI, and would at least alert users to this condition.

The second step may not be strictly necessary, but might save some heartache on the part of users.

Other thoughts?




Status:active» needs review


The model specification Section A.5 (page A-19) states "The multiplier for the probability of observing clinical signs in units inside a zone focus allows for the simulation of greater vigilance in higher-level zones."

Although not stating a range for valid values, it implies the intent is for values greater than one. Would the spec need to be changed to explain why and acknowledge that the multiplier can be less than one?


I like the idea in the original post of producing warnings when a value less than 1 is entered, and when the simulation launches.

As for the spec, perhaps we just need a note in parens: (A multiplier value of less than 1 will reduce the probability of detection in the zone.)


There is now a warning if the multiplier is < 1 in the C code for 3.1, 3.2, and 4.0.


Assigned to:guest» Aaron Reeves

I'll add warning code to the GUI.


Status:needs review» fixed


Status:fixed» closed

The fix for this issue has been incorporated into NAADSM 3.1.29, 3.2.10, and 4.0.5. This issue is now closed.


Title:Zone detection multipliers of 0 are not allowed by the GUI» I am the new guy
Assigned to:Aaron Reeves» guest
Status:closed» active

Thanks for one's marvelous posting! I definitely enjoyed reading it, you're a
great author.I will make sure to bookmark your blog and will come back very
soon. I want to encourage you to definitely continue your great work,
have a nice weekend!

Here is my site - antalya escort


Title:I am the new guy» Just want to say Hello!

What i do not realize is actually how you are now not actually a lot
more neatly-preferred than you might be now. You are so intelligent.
You already know therefore significantly with regards to this topic, produced me individually consider
it from a lot of numerous angles. Its like men and
women don't seem to be involved until it's one thing to accomplish
with Girl gaga! Your own stuffs nice. Always take care of
it up!

Also visit my site; http://www.sohbethilal.com/