Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - charles

Pages: [1] 2 3
Uncertainty Quantification (quoFEM) / Local Failure Setting up Dakota
« on: November 16, 2022, 08:44:49 PM »

I tried to run my data on designsafe, but got this error...
problems with the setup?


can't find it anymore...


Yes, the parameters of the dashpot can be defined: the 'Rock' layer's Density and Vs can be changed. See the attached img.
The matlab files are attached.

Hello, thanks for your interest.

We choose to use json format because it provides a human-friendly format suitable for encapsulating all the information for defining the ground motion in a single file. 
It is a simple text file, you can edit using any text editor.
Let me use this example to explain:
If you open it, you'll see its structure like shown in the attached figure.
You only need to change a few things to fit for your data:
1. You can see the type of this motion is "UniformVelocity",  which means in the "data" section, you should input velocity values.
2. "numSteps" = 7998, it means there should be 7889 values in the "data" section.
3. In the units section, you only need to change the 'length' unit to either "in" or "m", means inch or meter. So the unit of the "data" is in/sec or m/sec, depending on the 'length' unit you choose
4. "dT" means the interval between the "data" values, dT's unit in this example is second, because you "time":"sec"

To account for the finite rigidity of the underlying half-space (bed rock), a Lysmer-Kuhlemeyer (1969) dashpot is incorporated at the base of the soil column.

Let me know if I answered your question.

If you are using a bbox for a place outside of the US and you specified the footprint to be Microsoft, you'll get that message.

In that case, the program automatically switches the footprint source to be OSM.

So you don't need to worry about that.

Site Response Analysis (s3hark) / Re: How to build issue in windows
« on: May 01, 2021, 01:36:39 AM »
Ok, let's first try to solve the conan error.

Inside your build directory:
conan install path/to/s3hark/folder

Then go to Qt Creator and run qmake

Then click build

Let me know what you get

Site Response Analysis (s3hark) / Re: How to build issue in windows
« on: April 24, 2021, 04:13:54 PM »
Do you have conan installed (pip install conan)?

Site Response Analysis (s3hark) / Re: soil column model
« on: April 24, 2021, 04:11:19 PM »
In one file you are updating mat 1-5, in another you are updating 1-5 and 100-500, tho you don't have 100-500 defined.
Not sure if this will cause differences in the results, but it is an example of the differences in your input.
Why did you say they are the same?

Other differences that might also affect results including:
1. The precision format, for example, 2.8000000e+01 vs 28

2.The coordinate system.
In one file the second dof is the gravity direction.
In the other file the third dof is the gravity direction.
I know there is no difference for human understanding (if you've taken care of all the directions when you create the node, elements, loads),
but it might be different for the preprocessor or solver to understand.

Site Response Analysis (s3hark) / Re: soil column model
« on: April 20, 2021, 11:53:20 PM »
At least the "#switch material stage from elastic to plastic" is different.

Site Response Analysis (s3hark) / Re: soil column model
« on: April 18, 2021, 11:28:42 PM »
Those tcls files are not exactly the same.
Any small difference could cause discrepancies in the results.

But looking at the figure, they are very close.

Site Response Analysis (s3hark) / Re: soil column model
« on: April 17, 2021, 04:42:54 PM »
Hello, thanks for sharing this.
Could you provide more info: what are two different ways to write the models?

Hi jsaw,

I see the problem. It's caused by the path type.
Just updated the code. Try to upgrade again.

I updated the code the put columns of image names in the output.
Please upgrade BRAILS:
pip install BRAILS --upgrade

AI use in Regional Simulation (BRAILS) / Re: pip install BRAILS
« on: April 14, 2021, 02:32:17 PM »
Can you share how you solved your first problem, i.e., did you install Microsoft Visual C++ 14.0 or you did
pip install pycocotools-windows?

For the new error, try this if you are using conda:
conda install shapely

I got it from here:

Pages: [1] 2 3