Search found 7 matches
- Thu Jan 22, 2015 10:31 am
- Forum: Framework
- Topic: Cannot use PlainStressUserMaterial, no definition of PSUMAT
- Replies: 6
- Views: 16318
Re: Cannot use PlainStressUserMaterial, no definition of PSU
Thank you for your reply.
- Mon Jan 19, 2015 5:59 pm
- Forum: Framework
- Topic: Cannot use PlainStressUserMaterial, no definition of PSUMAT
- Replies: 6
- Views: 16318
Re: Cannot use PlainStressUserMaterial, no definition of PSU
fmk wrote:
> did you get OpenSees as a binary application or did you build it yourself.
> If you downloaded a binary what operating system are you using?
Thank you for your reply. I built 32-bit OpenSees myself, using the version2.4.5 source code, on a Windows 7 machine.
By the way, I cannot build 64-bit OpenSees as the .lib files ( libm.lib, libm.lib...) in "\Win32\lib\" are not suitable for 64-bit.
Thanks again!
> did you get OpenSees as a binary application or did you build it yourself.
> If you downloaded a binary what operating system are you using?
Thank you for your reply. I built 32-bit OpenSees myself, using the version2.4.5 source code, on a Windows 7 machine.
By the way, I cannot build 64-bit OpenSees as the .lib files ( libm.lib, libm.lib...) in "\Win32\lib\" are not suitable for 64-bit.
Thanks again!
- Fri Jan 16, 2015 9:23 am
- Forum: Framework
- Topic: Cannot use PlainStressUserMaterial, no definition of PSUMAT
- Replies: 6
- Views: 16318
Cannot use PlainStressUserMaterial, no definition of PSUMAT
I cannot use PlainStressUserMaterial in OpenSEES built by source code v2.4.5, with the message:
"PSUMAT - NOT DEFINED IN THIS VERSION, SOURCE CODE RESTRICTED".
There is no definition of function "PSUMAT" in PlainStressUserMaterial.cpp.
But when I use the official OpenSees.exe downloaded directly from the website, I can use PlainStressUserMaterial with no error. Maybe there are some errors in PlainStressUserMaterial.cpp.
"PSUMAT - NOT DEFINED IN THIS VERSION, SOURCE CODE RESTRICTED".
There is no definition of function "PSUMAT" in PlainStressUserMaterial.cpp.
But when I use the official OpenSees.exe downloaded directly from the website, I can use PlainStressUserMaterial with no error. Maybe there are some errors in PlainStressUserMaterial.cpp.
- Mon Dec 29, 2014 8:30 am
- Forum: Framework
- Topic: Link error when building 64-bit OpenSees on Windows
- Replies: 3
- Views: 5009
Re: Link error when building 64-bit OpenSees on Windows
That's a pity. Maybe I should just stick on the 32-bit version. But still thank you.
- Sat Dec 27, 2014 2:45 pm
- Forum: Framework
- Topic: Building v.2.4.4
- Replies: 8
- Views: 9485
Re: Building v.2.4.4
Did you solve the problem of "module machine type 'x64' conflicts with target machine type 'X86'" ? I'm facing the same problem and don't know how to solve it.
- Sat Dec 27, 2014 2:33 pm
- Forum: Framework
- Topic: Link error when building 64-bit OpenSees on Windows
- Replies: 3
- Views: 5009
Link error when building 64-bit OpenSees on Windows
Hi,
I tried to building 64-bit OpenSees on a 64-bit Windows machine, but failed due to the error:
libm.lib(isnan.obj) : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'
This error occurs both in building Project OpenSees and OpenSeesTk.
I've searched this issue and find some relevant pages, but none of them really solves it.
http://stackoverflow.com/questions/3563 ... achine-typ
http://opensees.berkeley.edu/community/ ... bit#p99005
http://opensees.berkeley.edu/community/ ... bit#p99213
http://opensees.berkeley.edu/community/ ... =4&t=62052 (same problem with mine)
What I have done are:
1. Install a 64-bit tcl, and use the sourcecode of OpenSees 2.4.5;
2. In VS2012, change the solution platform to x64/Debug in all the projects, and set the target machine to "MachineX64 (/MACHINE:X64)";
3. Try to build a new 64-bit project using VS2012 and succeed.
4. Check the "VC++ Directionaries" in "Project/ Properties" page, and all the directionaries are already changed to 64-bit, such as "$(VCInstallDir)lib\amd64";
5. Try to use old versions of OpenSees sourcecode, and the same error occurs.
6. "libm.lib" is an existing file in "\Win32\lib\", and I find that it's a lib just for 32-bit by checking it's head values (14C machine x86 ). I'm wondering if it is the point, but don't know where to get a "libm.lib" for 64-bit.
Does anyone successfully build the 64-bit OpenSees on Windows? And Could you help me solve this problem?
I tried to building 64-bit OpenSees on a 64-bit Windows machine, but failed due to the error:
libm.lib(isnan.obj) : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'
This error occurs both in building Project OpenSees and OpenSeesTk.
I've searched this issue and find some relevant pages, but none of them really solves it.
http://stackoverflow.com/questions/3563 ... achine-typ
http://opensees.berkeley.edu/community/ ... bit#p99005
http://opensees.berkeley.edu/community/ ... bit#p99213
http://opensees.berkeley.edu/community/ ... =4&t=62052 (same problem with mine)
What I have done are:
1. Install a 64-bit tcl, and use the sourcecode of OpenSees 2.4.5;
2. In VS2012, change the solution platform to x64/Debug in all the projects, and set the target machine to "MachineX64 (/MACHINE:X64)";
3. Try to build a new 64-bit project using VS2012 and succeed.
4. Check the "VC++ Directionaries" in "Project/ Properties" page, and all the directionaries are already changed to 64-bit, such as "$(VCInstallDir)lib\amd64";
5. Try to use old versions of OpenSees sourcecode, and the same error occurs.
6. "libm.lib" is an existing file in "\Win32\lib\", and I find that it's a lib just for 32-bit by checking it's head values (14C machine x86 ). I'm wondering if it is the point, but don't know where to get a "libm.lib" for 64-bit.
Does anyone successfully build the 64-bit OpenSees on Windows? And Could you help me solve this problem?
- Tue Jul 23, 2013 7:16 am
- Forum: OpenSees.exe Users
- Topic: OpenSEES - MatLAB interface
- Replies: 4
- Views: 4102
Re: OpenSEES - MatLAB interface
Newest: I have solved the problem. "model BasicBuilder -ndm 2 -ndf 3" should also be put in "analysis-2.tcl"
Old Message:
Hi Giuseppe,
If your problem had been solved, can I ask you how you solve it?
What I'm trying to do is :
1. Use OpenSEES to analyze one step of a dynamic analysis, use database command "save 1". (Filename:analysis-1.tcl);
2. Close OpenSEES;
3. Retrieve the restoring force, and calculate the command(d,v,a) of the next step ;
4. Build a new tcl file (Filename:analysis-2.tcl), use database command "restore 1" at the beginning, use command "pattern" to construct the new command(d,v,a)
5. Use OpenSEES to run "analysis-2.tcl"
I can run "analysis-1.tcl" successfully. But when I run "analysis-2.tcl" , the error comes to be " invalid command name "pattern" while executing..."
When I merger "analysis-1.tcl" and "analysis-2.tcl" to a single file ("analysis-12.tcl"), and just run "analysis-12.tcl", it successes.
I'm so confused. When we use database command, cann't we close opensees and then restore the database in a different ".tcl" ?
Thanks a lot!
Geyas
Old Message:
Hi Giuseppe,
If your problem had been solved, can I ask you how you solve it?
What I'm trying to do is :
1. Use OpenSEES to analyze one step of a dynamic analysis, use database command "save 1". (Filename:analysis-1.tcl);
2. Close OpenSEES;
3. Retrieve the restoring force, and calculate the command(d,v,a) of the next step ;
4. Build a new tcl file (Filename:analysis-2.tcl), use database command "restore 1" at the beginning, use command "pattern" to construct the new command(d,v,a)
5. Use OpenSEES to run "analysis-2.tcl"
I can run "analysis-1.tcl" successfully. But when I run "analysis-2.tcl" , the error comes to be " invalid command name "pattern" while executing..."
When I merger "analysis-1.tcl" and "analysis-2.tcl" to a single file ("analysis-12.tcl"), and just run "analysis-12.tcl", it successes.
I'm so confused. When we use database command, cann't we close opensees and then restore the database in a different ".tcl" ?
Thanks a lot!
Geyas