<< Click to Display Table of Contents >> Running Example Programs |
|
The Setup program installs several example programs in a GeneHunter program group in Windows that you may use by clicking on the icons. These same example programs are available as Visual Basic source code in the C:\GENEHUNTER\EXAMPLES subdirectory. Other example programs are available as Excel worksheets that are installed in the C:\GENEHUNTER\EXAMPLES\EXCEL directory. If you installed the AI Trilogy, the GeneHunter directory is located under the C:\AI Trilogy directory.
Excel Examples Included in GHSAMPLE.XLS
Included in CLUSTERS.XLS
Included in INDICATE.XLS
Programming Examples GeneHunter provides examples for the following programming languages:
1. Visual Basic 6 in C:\GENEHUNTER\EXAMPLES\VB6 2. Microsoft Visual C++ 6.0 or higher in C:\GENEHUNTER\EXAMPLES\MSVC6 3. Delphi 6 - in C:\GENEHUNTER\EXAMPLES\DELPHI6 4. Microsoft .NET - There are two .net programming examples: one for C#, another for VB. Examples are located in the following folders: C# example: C:\GeneHunter\Examples\MS Visual Studio 2013 Express\C# VB example: C:\GeneHunter\Examples\MS Visual Studio 2013 Express\VB
As folder names suggest, examples were created with Microsoft Visual Studio 2013 Express for Windows Desktop. Both examples can operate as 32- or 64-bit programs depending on the active solution platform selection in the Configuration Manager. If you installed the AI Trilogy, the GeneHunter directory is located under the C:\AI Trilogy directory.
Each example consists of a full set of source code modules necessary to load and compile the example with a specific programming language. All necessary genetic algorithm function declarations modules (prototypes) are provided for each programming language mentioned above. If you have newer versions of these compilers, you may have to make adjustments.
If you have any problems calling DLLs in your language, please check with your compiler vendor for assistance. It is very difficult for Ward Systems Tech Support staff to keep abreast of DLL calling procedures for all languages, especially since they change so frequently as new versions are released. Tell them our DLLs are called by name, not number, and underbars are not used in the names. |