1********************************************************************** 2 SNNSv4.2 Known Problems 3********************************************************************** 4 5There are a number of problems that we know about, but which we 6haven't had time to fix yet. Among them are: 7 8- Some HP machines have problems with the bignet panel for Jordan 9 networks. There have been several segmentations faults reported. 10 11- When converting a netork to C-Code with snns2c, special units will 12 be ignored. This means, that when converting a network on which 13 input pruning has been performed, the resulting C function will 14 accept only patterns with less input values. 15 16 Example: A 26-10-35 network was pruned, and consequently lost 3 of 17 its input units (Note that they are still represented in the network 18 file as "special input" units). After converting the resulting 19 network to C code you can call this function only with 23 input 20 values. Which of the original 26 values have to be skipped is to be 21 determined by the user! 22 23 24********************************************************************** 25 REPORTING BUGS 26********************************************************************** 27 28If you really need to report a bug you should run 29 30 make bugreport 31 32in <SNNSDIR>. This command ensures, that your Makefiles are up to date 33and prints out all critical definitions. If you see, that the SNNS is 34reconfigured during this operation, you must recompile SNNS and check, 35if the bug is still there before complaining about problems. Also 36refer to Readme.install to learn more about how to change C-compiler 37usage and compile flags. 38 39The output from the above command should be included in your bug 40report, so we don't need to ask you about your system characteristics. 41 42Send your bugreport to SNNS-Mail-Owner@Informatik.Uni-Tuebingen.DE