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 - adamzs

Pages: 1 ... 4 5 [6]
76
bug report from Stanford's CEE 296 class:

When running MDOF-LU and OpenSees response simulation with 1D ground motion input (i.e., the data_y field is removed from the event file), OpenSees returns incorrect EDPs. Looking at the example.tcl file, the error seems to stem from a second timeSeries being assigned to the acceleration recorder even though there is only one timeSeries present in the analysis.


A quick workaround: Use data_y: [0.0, 0.0] in the event file.


UPDATE:
This bug was fixed in rWHALE released as part of v2.3.0 of SimCenterBackendApplications

77
Damage & Loss (PELICUN) / Re: Component Definition
« on: May 28, 2020, 11:25:52 PM »
Hi,

If a component is non-directional, the information you provide under 'direction' is not used. I usually provide '1' for the sake of consistency, but it really does not matter. I plan to improve on this by allowing N/A under direction for such cases in version 3.0. Make sure you do not provide two direction values (such as '1, 2') because that will lead to two non-directional performance groups.

The median_quantity is applied to each performance group defined. If you have, for example, location=1,2 and direction=1,2, that leads to a total of 4 performance groups: on floors 1 and 2 in directions 1 and 2. The median_quantity is applied to each of those. Using median_quantity=10, for example, would lead to a total quantity of 40 in the building. If you want to use different quantities across floors and directions, you need multiple dictionary entries under the same component name, each specifying the location and direction of a given performance group.

Let me know if you have further questions.

78
Performance Based Engineering (PBE) / Re: Damage and Loss
« on: April 20, 2020, 08:03:43 PM »
The default list is limited to what is available in FEMA P58. There are many more components that would be great to have there, but it will take time and significant research effort to get to a point where we will have a complete list.

Although there is an ID for steel beams (B1032), no component data has been published under that ID yet.

Steel columns are assumed to experience damage or fail at their connections. There are several components for such connections (starting with B1031 and also look at B1035 for moment frame connections)

Concrete beams and columns are available under B1042, and B1041, respectively. Although, for columns, the damage is assumed to happen at the connections, similarly to the steel cases.

I'm afraid a concrete-filled metal deck component is not available. If you find a paper or data that allows you to define the corresponding damage model, I can help you prepare a fragility data file that you can use in PBE.



80
Hi Zetian,

If you set the Custom Local Applications to the PBE folder, the app should be able to pick up the location of the fragility data automatically.

Now, rather than trying to figure out why the automatic identification is not working, I suggest you to point to the location of the default data folder manually. Go to the Components tab under DL and click on the Choose button next to the Damage and Loss Data Folder. The default fragility data should be at

applications\performDL\pelicun\pelicunPBE\resources\FEMA P58 second edition\DL json\

under the PBE folder. This can help everyone find their DL data.

In your specific case, navigate to this location:

"C:\Users\Zetian\Documents\PBE\applications\performDL\pelicun\pelicunPBE\resources\FEMA P58 second edition\DL json\"

Once that folder is specified, the fragility data should be loaded properly.

Let me know how it goes.

Adam

81
To find the detailed data go to File->Preferences and check the location of the Local Jobs Directory. Go to that directory and you will find a tmp.SimCenter folder. All detailed data files are within that folder.

82
When loading EDP values from CSV files, you might experience issues on Macs if the files were originally prepared on Windows (and probably vice versa). The reason behind this is that the two operating systems use different line endings.

The solution is quite simple:
Open the EDP data file in Excel and save it without changing anything in it. This will fix the line endings and should make the analysis work fine.


83
Thanks for posting this; it is very helpful!

84
Performance Based Engineering (PBE) / Missing or incomplete Tooltips
« on: March 05, 2020, 05:38:50 PM »
Please let us know in this topic where you would find more tooltips useful and which tooltips should we extend with more information

Pages: 1 ... 4 5 [6]