The OpenSees Community

fmk wrote:
> while i have not announced a new release .. i have a new version of 2.5.0
> available for download .. it should include the material if you want to
> check.
Hello, Prof Frank. When could you update the command manual with my added new material (FRPconfinedconcrete02)? Do you need me send you my document via email again?

Many thanks!

Dear administrators,
I have been discussing with many colleagues using Opensees. When a whole structure (e.g. a whole bridge, framed building, even high-rise building) is modeled, usually it is hard to get converged results using force-based elements. Generally, disp-based elements are used instead also for lower computational cost (? haven't tested whether five disp-based elements or one force-based element with 5 ips runs faster). The much more complicated iteration processes in force-based elements are basically the reasons for that.
I wonder if force-based elements have been used in modeling of a whole structure of a real project? What can we do generally to increase the possibility of converged results using force-based elements?

Thank you very much in advance!

fmk wrote:
> your code has been in the repository awhile now .. if you obtain the code
> using svn you will see it .. i have not gotten back about updating the
> command manual as i am not ready et to get out a new release .. sorry
>
> frank
OK. Thank you very much, frank!

Hi, fmk,
Have you checked my code? I have sent it to your email.
Very appreciate your help!

No reply yet.

fmk wrote:
> you have to send to me with the examples that demonstrate it works. when i
> can run and test i will addd to code base. i will give you permission to
> edit in the wiki which is where you will document your command.
Hi, fmk,
I have sent the materials to fmckenna@ce.berkeley.edu
Is it the right email address?
Thank you!

Hi, fmk,
My colleague and me have built an new materiel for FRP-confined concrete named FRPConfinedConcrete02 (since there already exists one such materiel in the documentation). We have also built a documentation and two examples for the new material.
I wonder if we could submit our materials here. Please tell us what to do before the new material can be implemented in the new version of OpenSEES.
Thank you very much!

Is there a big difference when you use 10 or 20 ips? For hardening behavior, I guess there is no much difference. For softening behavior, you will not get objective result using more ips, plastic hinge element will give objective results.

Hi, fmk,
I have solved my problem. Here is how:
I downloaded the new developer folder from svn://peera.berkeley.edu/usr/local/svn/OpenSees/trunk/DEVELOPER
But it seems that "bool.h" is missing in the core folder. So i downloaded "bool.h" from the opensees SRC and copied in the core folder.
After that, it works fine.

Thank you anyway!

Hi, fmk,
It is my new material cpp file. I used OPS_GetNumRemainingInputArgs() function to get the number of input parameters. When I double-click the error, it said "the system can not find the file specified"

Here is part of my code, which I think the error comes from. I am sure you can understand it easily.
#include <elementAPI.h>
#include "FRPConfinedConcrete02.h"

#include <Vector.h>
#include <Channel.h>
#include <math.h>
#include <float.h>

#ifdef _USRDLL
#define OPS_Export extern "C" _declspec(dllexport)
#elif _MACOSX
#define OPS_Export extern "C" __attribute__((visibility("default")))
#else
#define OPS_Export extern "C"
#endif

OPS_Export void *
OPS_Newmaterial(int argc,
const char **argv)
{
// Pointer to a uniaxial material that will be returned
UniaxialMaterial *theMaterial = 0;

int iData[1];
double dData[8];
int numData = 1;

if (OPS_GetIntInput(&numData, iData) != 0) {
opserr << "WARNING invalid uniaxialMaterial Newmaterial tag" << endln;
return 0;
}

int inputNum = OPS_GetNumRemainingInputArgs();

if (inputNum == {
if (OPS_GetDoubleInput(&inputNum, dData) != 0) {
opserr << "Invalid #args, want: uniaxialMaterial Newmaterial " << iData[0] << " fc0? ec0? Ec? fcc? ecu? ft? Ets? Unit?" << endln;
return 0;
}
theMaterial = new FRPConfinedConcrete02(iData[0], dData[0], dData[1], dData[2], dData[3], dData[4], dData[5], dData[6], (int)dData[7]);
}

if (theMaterial == 0) {
opserr << "WARNING could not create uniaxialMaterial " << iData[0] << endln;
return 0;
}

return theMaterial;
}

Hello, fmk,
I am building a new material using my OpenSees developer folder. If I use the function OPS_GetNumRemainingInputArgs(), i got the following error:
error LNK2019: unresolved external symbol _OPS_GetNumRemainingInputArgs referenced in function _OPS_

it seems that my developer folder is very old, so I downloaded a new one, but got the following error:
fatal error C1083: Cannot open include file: 'bool.h': No such file or directory

I have no idea what is updated in the new developer folder. If I do not use OPS_GetNumRemainingInputArgs() in my old folder, it works fine.

Thank you!

The confinement effect of FRP need to be considered manually into the stress-strain model of concrete.

You'd better contact the developer, Brag, of this material. Or you may find them in his paper.

You can find them in the source code of this model

mhscott wrote:
> Vahid,
>
> I haven't checked this message board in a while. Please come see me to
> discuss if you and Andre haven't already figured it out.
>
> Michael
Dear Scott,
Could you offer me some help?