11/20/2022 0 Comments Risa 3d failure![]() ![]() They also allow users to get drift reporting at specific points of interest even if these points don't line up well from floor to floor or don't behave the same as other nodes at that elevation. They allow models defined in older versions of the program (which only used defined "story joints") to produce identical drift results in the current version. Node definitions are included for a number of reasons. In addition, the user may specify individual nodes to be used in drift calculation. These elevations are defined with respect to the vertical axis of the model. However, these elevations must be manually entered by the user in the Drift Definitions spreadsheet. Drift calculations may be performed at specific elevations (where diaphragms don't exist). If the model contains diaphragms, the nodes connected to that diaphragm will automatically be considered in the drift calculations. The Drift Definitions spreadsheet defines where the drift calculations will be performed. The calculations will be performed in the two horizontal translation directions, but not for the vertical direction. The font types and colors will need to be adjusted once in AutoCAD since you can't choose "BYLAYER" for the color or an actual style name (just the shx file).You may calculate and report inter-story drift based on calculated node RAM also has a cleaner output for AutoCAD than RISA you can define offset distances, layers, font height and types and colors. RAM is more automated, you draw elements and they're already defined. draw a line, define it as a beam and add additional criteria to it) this is a pro and con like much of what I am saying, it allows you some broader capabilities while taking a little more work. RISA is more of a general design product and you need to assign the properties to the elements you draw (e.g. If you're going to be around anytime soon just give me a call and I'll be sure to have a couple of our engineers available to talk to you about their experiences with both products.Īs for pros and cons, like Paul mentioned ETABS is quite a robust package generally I've heard it's more suited for taller projects. Most of our engineers lean towards RAM, but there are a few here that are also quite impressed with RISA. ![]() I'll post back to the forum with more information as we progress further in our testing. Good luck with your decision and hopefully you found something useful in my rambling. It seems that the word is out that Revit Structure is for real and it's up to us to keep pushing for more links. Some to our surprise are already in the works. We utilize some lesser known software packages (analytical and otherwise) that we have expressed interest in linking to Revit and have received nothing but positive feedback from the developers of these packages to generate these links. That being said any switch from RAM would be a costly one in terms of software, training costs, and initial lost productivity, so needless to say we are proceeding somewhat cautiously at this point and doing a lot of testing and research.Īs far as 50 analysis programs developing links to Revit Structure that number would not surprise me one bit. ![]() If we had to pick today I believe we would give the nod to RISA3D and RISAFloor. Robot is another interesting option that at first glance seems to be on par with the RISA interface. At this stage our impression is that the ETABS link may be a little more robust / mature but our engineers prefer the user interface of RISA (personal preference). We have been doing preliminary testing with the ETABS and RISA links. That being said we are keeping our eye on the current acquisition of RAM by Bentley and what impact that may or may not have on a future Revit Structure link. Our engineers preference for most design projects is RAM. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |