From d5a0869a7d1482b67f3fd42805948ee30a05eb1e Mon Sep 17 00:00:00 2001 From: Harpreet Date: Thu, 4 Feb 2016 15:36:02 +0530 Subject: Source files --- .../scilab_en_US_help/sym_isIterLimitReached.html | 84 ---------------------- 1 file changed, 84 deletions(-) delete mode 100644 help/en_US/scilab_en_US_help/sym_isIterLimitReached.html (limited to 'help/en_US/scilab_en_US_help/sym_isIterLimitReached.html') diff --git a/help/en_US/scilab_en_US_help/sym_isIterLimitReached.html b/help/en_US/scilab_en_US_help/sym_isIterLimitReached.html deleted file mode 100644 index 7081962..0000000 --- a/help/en_US/scilab_en_US_help/sym_isIterLimitReached.html +++ /dev/null @@ -1,84 +0,0 @@ -
- -To know whether the iteration limit (node limit) was reached.
sym_isIterLimitReached()
This post-solution query routine is used to learn whether the iteration limit(node limit) was reached.
-It prints whether or not the iteration limit (node limit) was reached to scilab console.
-It can also be used if "find first feasible" parameter was set to true before solving the problem.
This function takes no arguments
It returns 1 if the iteration limit is reached or 0 if the iteration limit is not reached or -1 if there was an error.