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 dates dlibrary dllcall error 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 PQG graphics procs RAM random numbers string functions strings structures threading writing data
Time Series 2.0 MT
Find out more now
Time Series MT 2.1
Find out more now
bug with CMLMT with only one parameter
Suppose there is only one parameter estimated, with bound constraints (no other constraints). Then line 606 of cmlmt.src will create np=1. By default, qp_a=nan. Then line s 1146-1147 (if scalmiss(qp_a); qp_a = zeros(1,np-1)~1;) creates trouble "Argument out of range " because of zeros(1,np-1).
CMLMT2.0 has been released for several years. I paid for this, yet it is so disappointing! (I pinned down another serious bug a couple of years ago regarding MLE/QMLE robust covariance matrix; it appears that it is still there!)
What version of CMLMT to you have. The current version, 3.0.1, has the following for handling the single parameter model.
if np > 1;
qp_a = zeros(1,np-1)~1;
qp_a = 1;
qp_b = -1e256;
numeq = 0;
With regard to the QML bug you mentioned, could you pass on a more specific description to email@example.com? Thank you.