Post validity-integration tweaks

[grumpyinca]

This issue is intended to provide a branch supporting a range of small-scale changes applied after the validity changes of branches 590 and 569.

Changes associated with Alerts.js, AlertsModal.js & Help/Alerts.md:

• introduce the message prefix "INVALID CONSTRAINT VALUE"
• provide Help URLs & associated content for constraint validity
• tweak the tooltip wording

Also include:

• increase default MAXIT
• corresponding changes to MAXIT in Br590TestScript & tweakPrefs script, etc.
• a couple selected design type specific alerts conditioned on OBJ > OBJMIN
• reduce the default value of OBJMIN from 0.00005 to 0.00001.
• add a digit in the format of the objective value output in the feasibility status tooltip.
• keep Help/alerts.md synchronized with changes design type specific alerts files.

Update new Patsh.js:

• modified the new patsh to count iterations in a similar manner as that of the old patsh

[1fifoto]

Also consider adding to patsh: s + tol * Math.abs(ssi) >= ssi

[grumpyinca]

Validity and Alert handling before & after Search, Seek & Trade

Before Search

• remove tests for: Objective Value less than OBJMIN. (tested before menu enable or button display) One (or more) Independent Variable(s) is (are) Not a Number (input filtering blocks non-number) Objective Value is Not a Number. (Necessary? input filtering blocks non-number)

• keep tests for: No free independent variables (Alert only warns; there is no other block) constraints are inconsistent (Alert only warns; there is no other block)

After Search This section moved to issue #705.

Before Seek

• remove tests for: One (or more) Independent Variable(s) is (are) Not a Number (input filtering blocks non-number) Objective Value is Not a Number. (Necessary? input filtering blocks non-number)

  Is validity test really necessary (moot) ?
  Won't invalid create enough of an objective value to block the availability of Seek ?

  • keep tests for: No free independent variables (Alert only warns; there is no other block) constraints are inconsistent (Alert only warns; there is no other block)

  • add test for Calc Input validity ? (Necessary? Will objective value block availability of Seek ?)

After Seek This section moved to issue #705.

Before Trade Add same tests as before Search. This section moved to issue #705.

After Trade This section moved to issue #705.

[1fifoto]

Merged into master.

[grumpyinca]

Issue #698 is now closed. Ongoing initialState changes being handled as part of this issue.

Specifically, Allow User_Specified End_IDs & L_Ends to be 0 w/o invalid alert.

[grumpyinca]

Added alerts for Cycle_Life for case when Prop_Calc_Method > 1 and also case where FS_2 < 1.0.

[grumpyinca]

Changes in the past several days:

• add See Also link to Cycle_LifeNA_FS_2
• Add alert for Excess Force

These changes resulted in merge conflicts versus branch #707. It appears that it is time to close this branch and move on to a greater number of new and short-lived issues based on the then current master.

Merged to master. Pushed to remote. Closing.