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 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 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
Find out more now
ERROR 'Undefined symbols"
When I run a file from the GAUSS (version 10) command line like this:
» run C:\gauss10\src\rmethods.src.src;
I get the following error:
Undefined symbols: statchek C:\gauss10\src\rmethods.src.src(30) v C:\gauss10\src\rmethods.src.src(579)
Can someone help guide me in the right direction?
It looks like in your file rmethods.src.src there is a call to a GAUSS procedure or variable named statchek. GAUSS cannot find the definition of that variable or procedure.
Here are some ways that you can make GAUSS know about a procedure definition:
- Place the procedure definition in the file in which it is used.
- Place as the only contents in a file called my_procedure.g in your current working directory. (my_procedure needs to be replaced with the actual name of your GAUSS procedure.
- Add the procedure to a GAUSS library.
If your procedure is in a GAUSS library, then the library needs to be "active" or "loaded". You can load a library in GAUSS with the library statement like this:
//load a library named 'my_library' library my_library;
Inside of the library file, is a reference to the procedure and file that it is in. It will look like this:
my_source_file.src myProcedure : proc : 25
Or with a full path like this:
C:\path\to\my\file\my_source_file.src myProcedure : proc : 25.
You can open and look at the library file. It is just a text file. If the reference to your procedure contains the full path, then you need to make sure that your source file (my_source_file.src in the example above) is actually in the folder specified and that it does in fact contain the procedure in it. The 25 in these examples is the line number of the procedure. GAUSS does not demand that this is accurate.
If your library file does NOT contain a full path to the file, but just the file name instead, then the file needs to be in either:
A) Your current working directory
B) In your GAUSS SRC_PATH
Your GAUSS SRC_PATH is controlled by the src_path variable in your gauss.cfg file. (gauss.cfg is located in your GAUSSHOME directory). You can print your current GAUSS SRC_PATH with the command:
This will print out a semi-colon separated list of all paths in your SRC_PATH. It will be something like: