|
Size: 4836
Comment:
|
Size: 7772
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| [[TableOfContents]] | <<TableOfContents>> For questions that are not addressed here or in the manual, send email to https://groups.google.com/group/bcvtb |
| Line 6: | Line 8: |
| === Error when compiling Ptolemy II (Windows only) === If running |
|
| Line 9: | Line 9: |
| {{{ make configPt }}} or running {{{ ./configure && make fast install }}} gives the following error {{{ /bin/sh: -c: line 1: unexpected EOF while looking for matching `'' /bin/sh: -c: line 4: syntax error: unexpected end of file }}} then the source code is most likely with Unix line endings. Download the Windows source code from the Ptolemy web page. === Error when compiling MATLAB (Windows only) === |
=== Error when compiling MATLAB === ==== Windows ==== |
| Line 27: | Line 12: |
| Line 35: | Line 19: |
| Line 41: | Line 24: |
| === Error when compiling MATLAB (Mac OS X with Matlab R2009a only) === Under Mac OS X, if the BCVTB is compiled in Matlab R2009a, the following error may occur: |
==== Linux Ubuntu 10.10 64-bit ==== In MATLAB R2010b, the command {{{ cd lib/matlab ant all }}} may fail with the error message {{{ Warning: You are using gcc version "4.4.4-14ubuntu5)". The version [exec] currently supported with MEX is "4.3.4". [exec] For a list of currently supported compilers see: [exec] http://www.mathworks.com/support/compilers/current_release/ [exec] [exec] /usr/bin/ld: cannot find -lstdc++ [exec] collect2: ld returned 1 exit status [exec] [exec] mex: link of ' "establishBSDSocket.mexa64"' failed. [exec] [exec] ??? Error using ==> mex at 208 [exec] Unable to complete successfully. [exec] [exec] Error in ==> [exec] /usr/local/matlab/R2010b/toolbox/simulink/simuli>> nk/+legacycode/@LCT/compile.p>compile [exec] at 264 [exec] [exec] [exec] Error in ==> [exec] /usr/local/matlab/R2010b/toolbox/simulink/simulink/+legacycode/@LCT/legacyCodeImpl.p>legacyCodeImpl [exec] at 84 [exec] [exec] [exec] Error in ==> legacy_code at 87 [exec] [varargout{1:nargout}] = legacycode.LCT.legacyCodeImpl(action, [exec] varargin{1:end}); [exec] [exec] Error in ==> compile at 90 [exec] legacy_code('compile', def, ... [exec] }}} This problem is caused by {{{/usr/bin/ld}}} not finding the {{{stdc++}}} library. As a work-around, proceed as follows: |
| Line 44: | Line 65: |
| Type | |
| Line 45: | Line 67: |
| Undefined symbols: "_mxGetM", referenced from: _mexFunction in establishBSDSocket.o "_mxGetN", referenced from: _mexFunction in establishBSDSocket.o "_mxIsNumeric", referenced from: _mexFunction in establishBSDSocket.o "_mxGetClassID", referenced from: _ssGetDTypeIdFromMxArray in establishBSDSocket.o "_mxCalloc", referenced from: __RegNumInputPortsCB in establishBSDSocket.o __RegNumOutputPortsCB in establishBSDSocket.o _mexFunction in establishBSDSocket.o "_mxGetPr", referenced from: _mexFunction in establishBSDSocket.o "_mxIsComplex", referenced from: _mexFunction in establishBSDSocket.o "_mxCreateDoubleMatrix_700", referenced from: _mexFunction in establishBSDSocket.o ld: symbol(s) not found collect2: ld returned 1 exit status mex: link of ' "establishBSDSocket.mexmaci"' failed. ??? Error using ==> mex at 218 Unable to complete successfully. Error in ==> /Applications/MATLAB_R2009a.app/toolbox/simulink/simulink/+legacycode/@LCT/compile.p>compile at 261 Error in ==> /Applications/MATLAB_R2009a.app/toolbox/simulink/simulink/legacy_code.p>legacy_code at 91 Error in ==> compile at 58 legacy_code('compile', def, ... |
sudo emacs ~/.matlab/R2010b/mexopts.sh |
| Line 74: | Line 69: |
| This problem is caused because the linker flags in Matlab changed in R2009a. To fix this problem, open the file {{{bcvtb/lib/simulink/compile.m}}} and remove the entry | In the section {{{ glnxa64) }}}, change the line {{{ CLIBS="$CLIBS -lstdc++" }}} to {{{ CLIBS="$CLIBS" }}} Now, the command {{{ant all}}} should work and produce the files {{{libbcvtb_thunk_glnxa64.so}}}, {{{establishBSDSocket.mexa64}}}, {{{exchangeDoublesWithBSDSocket.mexa64}}} and {{{closeBSDSocket.mexa64}}}. |
| Line 76: | Line 79: |
| {{{ -L/usr/lib }}} Then, recompile the file. This will be fixed in releases after version 0.1.1. |
|
| Line 84: | Line 85: |
| === Running the BCVTB on Mac OS X version 10.11 === Apple has enabled a new default security oriented featured called System Integrity Protection, often called rootless, in OS X 10.11 onwards. This new feature prevents the BCVTB to set environment variables which are required for the BCVTB to run. To circumvent these problems copy the {{{libbcvt.dylib}}} which in in {{{bcvtb/lib/util}}} to {{{/usr/local/lib}}} with {{{sudo cp bcvtb/lib/util/libbcvt.dylib /usr/local/lib}}} Next, check if a !HostName is set on your machine. This can be done by typing in a terminal {{{scutil --get HostName}}} If there's no !HostName set, then set your !HostName. Your !HostName must be the same as your computer's local network name. To find out your computer's local network name, Open Sharing preferences (choose Apple menu > System Preferences, then click Sharing). The local network name is displayed beneath the computer’s name at the top of the pane. The local network name is your computer’s name with “.local” added, and any spaces are replaced with hyphens . For example, if your computer’s name is My Computer, your local network name is “My-Computer.local.” Set your !HostName with: {{{sudo scutil --set HostName 'YourLocalNetworkName'}}} === Check program output === By default, the {{{Simulation}}} actor in Ptolemy writes a copy of the console output of the simulation program to a file called {{{simulation.log}}}. This file can typically be found in the directory from which the simulation program has been started. |
|
| Line 85: | Line 119: |
| For each simulation, the BCVTB will write a log file that contains the console output of the simulation program. The name of the simulation log file is determined by parameter {{{simulationLogFile}}} of the {{{Simulator}}} actor, with the default name being {{{simulation.log}}}. Check this file for possible error messages. === Investigate program output === Depending on how simulation programs are called by the {{{Simulation}}} actor in Ptolemy, the console output written by the simulation program may not be visible. To see the console output, change the command line of the Ptolemy actor from {{{ bash ./runClient.sh }}} to {{{ xterm -e bash ./runClient.sh }}} This will start a terminal that shows the output of the running simulation program which help analyzing what goes wrong, for example, when the simulation program terminates due to an error before connecting to the BCVTB. === Investigate log files === |
|
| Line 105: | Line 124: |
| Then, from the directory {{{bcvtb/lib}}} compile the libraries using {{{ make clean make |
Then, from the directory {{{bcvtb/lib/util}}} compile the libraries using{{{ ant clean all |
| Line 112: | Line 128: |
=== Memory problem === If the following error occurs:{{{ java.lang.OutOfMemoryError: Java heap space}}} then increase the Java heap space by running vergil with the command{{{ java -jar path_to_bcvtb\bin\BCVTB.jar -Xmx1024m system.xml}}} The argument {{{-Xmx1024m}}} declares how much memory is allocated. The default for Java is -Xmx128m === Wrong Java version === The following error occurs if a too old Java version is used:{{{ java.lang.UnsupportedClassVersionError: Bad version number in .class file}}} To fix this problem, update your Java. === EnergyPlus on Windows cannot find Java === If !EnergyPlus writes the error{{{ Instantiating Building Controls Virtual Test Bed ExternalInterface initializes. 'java' is not recognized as an internal or external command, operable program or batch file. **FATAL:Error in ExternalInterface: Check EnergyPlus *.err file. }}} then Java is installed, but not on the {{{Path}}} variable of the operating system. This situation occurred on a Windows 7, 64-bit, installation. The Windows Explorer associated the file extension {{{.jar}}} with Java (which allowed the user to start the BCVTB from the Windows Explorer), but Java could not be found by !EnergyPlus as the Java binary directory was not on the Windows {{{Path}}} variable. To fix this problem, add the directory that contains {{{java.exe}}} to your system path. Java may be installed in {{{C:\Program Files (x86)\Java\jre6\bin}}}. === Java cannot find VergilApplication === If running{{{ bin/bcvtb examples/c-room/system.xml }}} causes the following error{{{ Exception in thread "main" java.lang.NoClassDefFoundError: ptolemy/vergil/VergilApplication Caused by: java.lang.ClassNotFoundException: ptolemy.vergil.VergilApplication }}} then the system environment variable {{{PTII}}} is set to a directory that does not contain a Ptolemy II installation. This may happen if a user installed !OpenModelica, as !OpenModelica sets the PTII variable. To fix this error, proceed as follows: * on Windows, add the line{{{ <entry key="PTII">$BCVTB_HOME\lib\ptII</entry>}}} to the file {{{bin\systemVariables-windows.properties}}} in the BCVTB home directory. * on Linux or Mac, add the line{{{ <entry key="PTII">$BCVTB_HOME/lib/ptII</entry>}}} to the file {{{bin/systemVariables-linux.properties}}} or {{{bin/systemVariables-mac.properties}}} in the BCVTB home directory. |
Help
Contents
For questions that are not addressed here or in the manual, send email to https://groups.google.com/group/bcvtb
1. Compilation problems
1.1. Error when compiling MATLAB
1.1.1. Windows
Under Windows, if the BCVTB is compiled using the Microsoft compiler, then the MATLAB libraries also need to be compiled with the Microsoft compiler. If, however, the gcc compiler has been used when compiling the BCVTB, then the following compilation error may be obtained when compiling the MATLAB libraries: