1
Performance Based Engineering (PBE) / Re: Height factor premiums
« on: March 23, 2023, 03:35:05 PM »
Thanks! The general frameworks sounds like a great approach for future flexibility. Much appreciated.
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.
Pages: [1]
2
Performance Based Engineering (PBE) / Height factor premiums
« on: March 17, 2023, 11:39:05 PM »
Hi Simcenter team -
We'd be interested in implementing "height factor premium" values as suggested by FEMA P58 Vol 2, Table 2-1; ie. applying small cost adjustments/ premiums for repairs that occur on higher floors of the building.
We realize we can do this now by duplicating the fragilities and editing the costs manually, but would like to confirm: the current PBE interface doesn't offer a shortcut to input this kind of per-floor premium, right?
Thanks!
We'd be interested in implementing "height factor premium" values as suggested by FEMA P58 Vol 2, Table 2-1; ie. applying small cost adjustments/ premiums for repairs that occur on higher floors of the building.
We realize we can do this now by duplicating the fragilities and editing the costs manually, but would like to confirm: the current PBE interface doesn't offer a shortcut to input this kind of per-floor premium, right?
Thanks!
3
Performance Based Engineering (PBE) / Re: Dakota Error Debugging
« on: October 20, 2022, 04:44:55 AM »
I just wanted to follow up on this error in case any other users experience this problem.
I did not get this error with the EDP file. I resolved the error by correcting my components file.
I hit this error when the components file story/locations definitions contained any of the following issues:
- N stories defined in the "GI" tab was less than the max story that I provided in my components .csv file (this was an issue in pelicun v2 but I believe it is corrected in v3)
- a story definition contained an invalid string
- the .csv file format converted a story range into a date (also corrected in pelicun v3, I believe) - for example, story definition 7-15 was saving as a date format, July 15th - fixed the issue by changing to "7,8,9,10,11,12,13,14,15" for simplicity
I did not get this error with the EDP file. I resolved the error by correcting my components file.
I hit this error when the components file story/locations definitions contained any of the following issues:
- N stories defined in the "GI" tab was less than the max story that I provided in my components .csv file (this was an issue in pelicun v2 but I believe it is corrected in v3)
- a story definition contained an invalid string
- the .csv file format converted a story range into a date (also corrected in pelicun v3, I believe) - for example, story definition 7-15 was saving as a date format, July 15th - fixed the issue by changing to "7,8,9,10,11,12,13,14,15" for simplicity
Pages: [1]