Aptech Systems, Inc. Worldwide Headquarters
Aptech Systems, Inc.
2350 East Germann Road, Suite #21
Chandler, AZ 85286
Ready to Get Started?
For Pricing and Distribution
Training & Events
Step-by-step, informative lessons for those who want to dive into GAUSS and achieve their goals, fast.
Have a Specific Question?
Q&A: Register and Login
Premier Support and Platinum Premier Support are annually renewable membership programs that provide you with important benefits including technical support, product maintenance, and substantial cost-saving features for your GAUSS System or the GAUSS Engine.
Join our community to see why our users are considered some of the most active and helpful in the industry!
Where to Buy
Available across the globe, you can have access to GAUSS no matter where you are.
Recent Tagsapplications character vectors CML CMLMT Constrained Optimization datasets dates dlibrary dllcall error error handling errors Excel FANPACMT file i/o floating network GAUSS Engine graphics GUI hotkeys installation Java API license licensing linux loading data matrices matrix matrix manipulation Maxlik MaxLikMT Memory Optmum output PQG graphics proc procs RAM random numbers string functions strings structures threading Time Series writing data
Time Series 2.0 MT
Find out more now
Time Series MT 2.1
feasible step length could not be found in Constrained Optimization
I got this warning message “feasible step length could not be found” when using CO. It is said in the manual that “If none of the constraints are protecting the function from undened calculations, then
the test can be removed.” What does this exactly mean? I have one linear constraint, lower bound and upper bound. Should I need to pay attention to this message?
With some functions, the calculation of the function fails when one or more parameters are outside feasible parameter space, for example, the function calculation produces a zero value for a call to ln(). Other times feasibility may not be an issue in the computability of the function. In that case set a global variable to turn off the test for feasibility:
_co_FeasibleTest = 0;
If the calculation of the function now fails, you will need to place additional constraints on the parameters to keep it in well-defined parameter space.