AutoSearch Plus is a tentative (place-holder) name for a new feature specific to coil spring design types. In summary, when enabled, after a feasible conclusion of a Search or Seek conducted with Wire_Dia in Free status, AutoSearch Plus would conduct multiple Searches (and optionally, Seeks) with adjacent standard Wire_Dia values in Fixed status. The objective is to automatically provide the user with design alternatives that feature standard wire diameters.
Associated development and testing requirements may be significant.
Example:
If AutoSearch Plus is enabled,
.... If a Search has just completed,
........ If that Search was conducted with Wire_Dia in Free status (producing a result with a non-standard Wire_Dia),
then,
.... Two or three additional searches are conducted (potentially in parallel, using Web Workers).
.... These searches can each utilize the same starting point (the termination of the original search)
.... The value of Wire_Dia can be fixed at the bracketing standard wire diameter values.
alternatively,
.... Similar to the current operation of Action : Select Size, the two-higher and one-lower values of Wire_Dia can be Fixed for a total of three subsequent searches.
If a subsequent search returns a feasible result, it can be rendered on a separate ODOP tab from the original search. Searches returning infeasible results can be ignored.
Possible extensions
After obtaining a feasible result from a subsequent search, a Seek may be performed. The Seek target (likely Min Weight or Max Cycle_Life) can be configured as a preference value. If the result of the Seek is not feasible, yet another Search can be performed.
Additional thought has to be put into how to keep open tabs from accumulating as additional Searches (& Seeks) are performed.
Other notes
The description above has presumed that the AutoSearch Plus feature will run automatically. This does not have to be the case. In a crawl-walk-run development sequence, AutoSearch Plus might be first implemented as a macro (Execute script) plus supporting components. Similarly, parallel execution (Web Workers) might be introduced only after some real-world experience shows user acceptance for the feature.
AutoSearch Plus
AutoSearch Plus is a tentative (place-holder) name for a new feature specific to coil spring design types. In summary, when enabled, after a feasible conclusion of a Search or Seek conducted with Wire_Dia in Free status, AutoSearch Plus would conduct multiple Searches (and optionally, Seeks) with adjacent standard Wire_Dia values in Fixed status. The objective is to automatically provide the user with design alternatives that feature standard wire diameters.
Associated development and testing requirements may be significant.
Example:
If AutoSearch Plus is enabled, .... If a Search has just completed, ........ If that Search was conducted with Wire_Dia in Free status (producing a result with a non-standard Wire_Dia), then, .... Two or three additional searches are conducted (potentially in parallel, using Web Workers). .... These searches can each utilize the same starting point (the termination of the original search) .... The value of Wire_Dia can be fixed at the bracketing standard wire diameter values. alternatively, .... Similar to the current operation of Action : Select Size, the two-higher and one-lower values of Wire_Dia can be Fixed for a total of three subsequent searches.
If a subsequent search returns a feasible result, it can be rendered on a separate ODOP tab from the original search. Searches returning infeasible results can be ignored.
Possible extensions
After obtaining a feasible result from a subsequent search, a Seek may be performed. The Seek target (likely Min Weight or Max Cycle_Life) can be configured as a preference value. If the result of the Seek is not feasible, yet another Search can be performed.
Additional thought has to be put into how to keep open tabs from accumulating as additional Searches (& Seeks) are performed.
Other notes
The description above has presumed that the AutoSearch Plus feature will run automatically. This does not have to be the case. In a crawl-walk-run development sequence, AutoSearch Plus might be first implemented as a macro (Execute script) plus supporting components. Similarly, parallel execution (Web Workers) might be introduced only after some real-world experience shows user acceptance for the feature.