We apologize, but sometimes there are bugs that pop-up within Cranium and Synapse. Typically, we can reproduce the bug which is essential for correcting the problem. Sometimes, a bug occurs from an interaction between Cranium or Synapse and your specific computer environment. This is when generating a function call log file can be very helpful.
The following window displays an example log file. The file contains the application's sequence of function calls.
Function call logging can result in a significant degradation in performance. Logging should only be used as a diagnostic tool when instructed by us.
|Browse button for entering the name of the log file.|
|Logging Options: some function arguments may contain the names of chemicals, techniques, etc., which may be written into the log file. If you do not wish this information to be recorded, select the Private option. This will only report the characteristics of the argument, e.g., a positive number or a ten character string.|
|Display Options: check the "Show when done" option to display the log file once logging has ended.|
C:\Program Files (x86)\Molecular Knowledge Systems\Craniumor
C:\Program Files (x86)\Molecular Knowledge Systems\Synapse
"Cranium - logging" or "Synapse - logging"
The application will display the notice dialog notifying you that logging has started.
MKS Log 2020-08-24-00-23-25.mkslogwhere the digits denote the date and time. Note that even if the application unexpectedly terminates during a logging session, a log file will still be written.
|Getting Started using Cranium||provides a quick tour of Cranium's capabilities including physical property estimation and a discussion of structure editing.|
|Getting Started using Synapse||provides a quick tour of Synapse's capabilities including examples of chemical product design.|