Aptech Systems, Inc. Worldwide Headquarters
Aptech Systems, Inc.
2350 East Germann Road, Suite #21
Chandler, AZ 85286
Ready to Get Started?
Request Quote & Product Information
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
Recent Tagsapplications character vectors CML CMLMT Constrained Optimization datasets dlibrary dllcall econometrics error error codes error handling errors Excel file i/o floating network GAUSS Engine GAUSS Light graphics GUI hotkeys installation Java API license licensing linux loading data loops matrices matrix manipulation Maxlik MaxLikMT Memory multidimensional array optimization Optmum output panel data PQG graphics procs random numbers strings structures threading writing data
Time Series 2.0 MT
Find out more now
Time Series MT 2.1
Find out more now
nlsys question again: controlling step size
I have a follow-up question if the answer to my last question is no. Since I will feed GAUSS very good initial guesses and the value function may not be available with some wild guesses, I wonder if I can tell GAUSS to make only small steps when it is solving the problem with "nlsys". If so, would you please tell me the right command to use?
Thank you so much!!
You shouldn't have any problem with the nonlinear transformation on the parameter. If you are having problems use a different algorithm,
struct nlControl nlc; nlc.algr = 1; //default: line search nlc.algr = 2; // or try this one: hook step