Lesson finished
Lesson finished
Lesson finished
Unlock all 10 lessons of Crashworthiness Analysis using HyperMesh and RadiossFull course ₹40,000 · paid
1D Elements, Radioss Input Files and Critical Time Step
A free lesson from Skill-Lync's Crashworthiness Analysis using HyperMesh and Radioss course, on Grow by Skill-Lync · Last updated 16 Nov 2026 · Session: “2.0 - 1D Elements Export Part 1 Seg 1”
What will you learn in this free Crashworthiness Analysis using HyperMesh and Radioss lesson?
The instructor shows how to create and update RBE2 rigid bodies in HyperMesh, then covers beams, trusses and springs, including spot welds modelled as springs. He explains the Radioss starter and engine files and the critical time step formula, ending with an element length exercise.
- RBE2 rigid body with a master and slave nodes
- Spring elements for spot welds and seam welds
- Starter (0000.rad) and engine (0001.rad) input decks
- Time step as L divided by sound speed
What comes after lesson 2?
The next free lesson is lesson 3, “Shell Element Formulation and Radioss Element Properties” (101 min). Later in Skill-Lync's Crashworthiness Analysis using HyperMesh and Radioss course (paid): lesson 4, Materials Part 1; lesson 5, Hypercrash Part 1; lesson 6, Kinematic Conditions Part 1. The full course has 10 lessons (25 h 22 min of video); see the course overview or its price and syllabus.
Lesson transcript
Machine transcript of the lesson audio (lightly cleaned). Technical terms may contain errors; the video is the reference.
Part 1
In HyperMesh, regarding exploded solvers such as Radius and LSDyna, there are a few 1D elements that can be used for many purposes. So the following as shown on the screen are the most commonly used 1D elements. Then in that, the main types or the most commonly used that we will be using in our day-to-day analysis will be springs and rigids. So we will start with rigids and then we will move to beam, trusses and then we will finally go to the springs. So the peculiar thing about springs is that if you are trying to create spot welds or even seam welds, they can be represented as a spring element.
And if it is a seam element, then a series of spring elements can represent a seam element or seam weld. Let's first move to rigids. So in rigids, as we see on the screen, we have two types mainly. This is the type that will be commonly used, whereas this type, it is still more in the books, but less used in case of Radius or LSDyna. Whereas other solvers such as Optistruct or Abacus, RB3 is very commonly used. So we will focus first on RBE2 and then we will move to RBE3 just for conceptual purpose and then we will go to the rest.
So let's talk about rigids RBE2. So RBE2 are actually, in this case, we are going to connect all the nodes together. So on the screen, I have two panels and I have single 1D elements right now. What I will do is I will simply get rid of it by deleting the whole part. Now I have only two panels. They have material and property assigned. Now what I do is first go to 1D panel. Then here I have all the options that are needed to create anything.
Otherwise, I can always go to mesh, create 1D elements and then there I have all the options that are needed to be looked at. So we will start with rigids. Now in rigids, by default, you will get to see this kind of form. Now once you get this, first thing you should do is, now the rigid body, what it will do is, whatever the number of nodes you select inside the rigid body, if you impose any motion on any of the nodes inside a rigid body, the same motion will be implied on all the nodes inside the rigid body.
It won't be distributed, but it will be exactly identically copied on every node. So what happens is, usually we have a group of nodes such as, let's say there is a hole and instead of modeling the bolt, we have just decided that let's just connect that hole with the matching hole on the other panel without modeling the bolt. In that case, we want all the nodes on the bolt or on the hole circumference to be treated equally. So in that case, usually that can be one application where a rigid body could be created.
Now here, because that would be the case of multiple nodes, we will select multiple nodes for the independent node. And here for primary node, we will select calculate. And now you will see what exactly is happening. So now we have nodes, multiple node option. So I will select one node from this panel and few nodes from other panel and now all degrees of freedom are locked. It creates a rigid body and the calculated node, when I say calculate node, it actually calculates the centroid or let's say the mass, the weighted center of mass for all these nodes.
It calculates and it places the master node of this rigid body at that location. So this is currently the master node. So the thing about this master node is, let's say if I want to impose any forces here, let's say I want to impose one kilonewton each on all these nodes. If I impose one kilonewton on this, same one kilonewton will be imposed on each and every node. It won't be distributed, but exactly identical node will be or load will be applied. Such is the case for velocities.
Now, when you imagine a crash scenario, there are so many rigid bodies where you simply want to select all of them and impose some motion. So in such cases, many times if you don't have good representation of the physical body, many times rigid bodies are referred and only master of the rigid body will be applied to the initial velocity or imposed motion any which you want. Rest of the nodes will follow that path. So this is called master node, rest of them will be slave nodes.
Whatever the master does, slave will follow the same. So this is about rigid body. Now, if I want to update any rigid body, what I can do is, so I have the rigid body switched on because of this component. See that the card image and there is no card image and property ID. In fact, once we go to hyper crash for this, this won't even be recognized as one single component, but it is recognized only as a rigid body, which is a separate entity shown in hyper crash and not just as a component.
So here right now, what we'll do is, let's try to modify this rigid body. So I'll go to this panel, or I can simply use the same path again. And here I'll go to update. So I've selected this element. It's usually tricky if you're trying to select 1D element because your click may not be too accurate. So now it is asking me where I want to update only DOF or connectivity or I want to switch something else. So I'll say I want to update only the connectivity.
So in terms of connectivity, now it is asking whether independent node, which is master node in this case, do I want to switch that node somewhere else? So I can select this node for master node and it will shift the whole master node to this particular node, which I don't really want. So I'll refrain from doing that. Whereas, maybe I want to add a couple of more nodes and I'll hit update. And now I see even those nodes have been included in the rigid body, but the independent node is still at the same location.
What do I do in that case? So I'll hit calculate node again. I have the same nodes in that case. I'll need to select the element again. Now I have the same nodes. I have hit calculate node mode this time. And once I do that, now I see that the node position has been modified accordingly. So this is how the rigid body works. This is the most ideal form of rigid body that we are allowing the hyperworks to calculate the node, master node location for us, than imposing any particular node that usually gives a better understanding of the rigid body dynamics up.
After that, we'll quickly look at Rb3 as well, just as a concept. So Rb3, it is actually also rigid, but in a different sense. So in this rigid body, these nodes are literally inseparable. Whatever we impose on this particular master node, the same motion will be implied on all the nodes, all the dependent nodes. But in case of Rb3, now that if I'm imposing particular motion on this, in case of Rb3, the only difference from this is that the motion will be applied based on the weighted distance.
So let's say whatever I'm applying here, the maximum effect of that particular motion or force will be experienced on these two nodes because they are the closest. Then comes the corner four nodes and then comes this particular node where the effect of that particular motion will be the minimum. So this is more like, well, let's create an Rb3 and then I can explain you. So again, the very similar method or the dependent node and the concept of dependent and independent changes a bit here. So the slave nodes that we have been calling here, they become the independent node in this case.
And the dependent node, which is completely based on those, is calculated based on center of mass. So that's why the weight is 1. If you keep weight 1, that means it will calculate as regular. And now it has calculated the center at this location. What would happen is, whatever motion I impose on this particular node, maximum motion will be implied out of that on these two nodes on the corner. And less will be on the, like, maximum on these two nodes and less will be on the corner.
So, usually, this method is good. If I want to apply 100 kN of node, or load, on this particular surface, which includes only two elements, then it is a good idea. Usually, either I select the whole surface and apply pressure or I can create a rigid body out of it. So, again, these nodes will be inseparable from each other. But, because I am applying node, or I am applying load here, it will be distributed as per the distance, as per the weight. And, in the end, if I am applying 100 kN here, well, it is very likely that I will experience 25 kN on these two nodes.
And, maybe, 12 or 13 kN on each of these nodes. So, total will be 100 kN, but it will be distributed accordingly. So, really, the difference lies down in the basic mechanism of RB3 itself. The nodes, which are in multiple numbers, are actually the independent node in case of RB3, whereas the case is different in case of RB2 or rigids. So, the rigids, when I call, it is usually the RB2, very popularly known concept, and this becomes RB3. So, if we are clear about rigids and RB3, let's move further to the next topic, that is beam and trusses.
So, after creating rigids, well, let me get rid of rigids now, just to clean the model. So, when I hit escape, I can also escape or return from this particular panel, which where I was right now. So, let's create a bar element, maybe. Now, you see that we have only two components created over here, and those two components belong to those two shell elements or shell components. Now, what I would say is instead of bar, let's start with a rod, which is much simpler to understand.
The rod is also called as truss element in case of radius or even dyna. So, I click one node, and it is asking for only two nodes. So, plain and simple, it is asking for two nodes. Now it is connecting two nodes directly here because this is not a rigid body. That means these two nodes can have some relative motion between them. But interesting thing here is that now this becomes the truss element. Create a property for it. Now we'll very soon understand what exactly is property. But well, so for now let's just assume that there is something called property. So this truss element is actually or the bar element is actually having a cross sectional area. Now in case of rigids that wasn't the case.
Rigid body hardly cared about whatever cross sectional area there could be. So here I'm giving area of 100 and for hyperbeam section we are saying let's say the radius of that particular truss which is always a circular truss element or truss member that they are considering. So if we say radius 5 it calculates the area by itself and the moment of inertias are also calculated by itself. We hit this button and now area though I was trying to assign 100 or 10. Now it is being calculated because of this hyperbeam section. The gap is really not significant parameter here. So I'll hit close. So now what I have done is I have created a truss with 5mm radius and that way all the properties have been assigned.
The truss element because it has only two nodes. There is no frame of reference as such. It can only undergo axial loads. That means you can either compress it or you can either or you can put under tension so you can extend it. There is no bending because there is no sensitivity for bending. Now that actually creates the requirement for an element which can also take care of some bending. Now if you really remember the strength of material classes. There was always a truss element which will be considered only for tension or compression calculations. Whereas if you are looking at bending then we simply use the term beam.
That's why we will go to bars or beam. Now in this case what I will do is I will create a new component. Now we have a beam component over here. That's why the current component inside the model. Using this button I can set the current component. Once I click here it gives me all the options of all the four components that are available in the model right now. I'll hit beam and that makes sure that my current component is beam. Bar 2 element also asks for node A and B but apart from that it also asks for an orientation axis.
Now if we carefully look at this particular picture for beam what it is showing is there are two node inputs and then there is one node extra as an input. So the first two nodes that we are telling him or telling this computer along those two nodes will be the X axis local X coordinate of that particular local coordinate system. Whereas the third node is actually considered to be on the X Y plane of the local coordinate system. So these two nodes will are going to decide the direction of X. This node is going to only help figure out what is the X Y plane of that particular beam.
And based on that there will be a perpendicular drawn to this particular plane which will give you Z axis and a perpendicular to Z axis as well as X axis gives you Y axis. So this is how using these three nodes. So the first two nodes are very serious selection whereas the third node just has to be somewhere on the X Y axis or X Y plane and that has given us a whole coordinate system. So that is what we are going to do here. N1 is the origin node. N2 is the X axis node.
And now for N3 which is just a plane or just a node on X Y plane supposedly X Y plane. I can give that anywhere. Usually you need to be careful to understand or to decide where your Y should be, where your Z should be in local axis because such orientations are very important during analysis stage. So I click here. That means this is the origin, this is the X axis and because I have a node in this plane so that means Y axis will be on this direction.
Now because this is X Y that's why Z will be in that direction. Now this is called beam3n element. Again, I'll assign some property to it. In order to create beam element, the properties that are significant are basically the cross section. So if I hit cross section, now here the section type can be changed. Even in case of truss, you could have changed this as well. So here I'm going to select a box section. Now dimension A and B are nothing but the width and the length.
So thickness of this particular doesn't have much significance. So rest of the things have been already calculated. That is all that is needed to be done in this case. If we select any of these options, then that will put additional constraint on these things or on such beams that they can move only in this direction or which direction. So this WX1, translational degree of freedom, X rotation degree of freedom, node 1 is released. That is what it is trying to say. So node 1, which is this node, X degree of freedom.
So currently, these two nodes are connected by this beam element. The degrees of freedom of that particular node will be released if we select any of these radio buttons. So rather selection buttons. So this is local X, this is local Y, which is actually on this direction, local Z and then rotational. Again, because this is X axis, the rotation about this X axis can be locked or kept open. That is what it is trying to tell us. Now, as I said earlier, truss can undergo only axial loads, whereas beams, they can undergo loads in any direction.
And that is why such degrees of freedom have been mentioned so that if you want, you can lock that and that way you can make a more accurate model. So this is about truss and beam elements. We have covered this much area so far. Now comes the spring element that really is a huge topic. So springs as such, again, I'll create a new component. In springs, I have multiple options. I can hit spring 2 and it will create a spring of two nodes. I can ask for a spring 3N.
And now it is asking for very similar thing as beam element. It is asking for a local orientation axis. So it has already considered the local X as these two nodes. Whereas for local Y, it is going to ask for one more node. So this is a three-noded spring. The typical application for a three-noded spring is usually a pulley that is used in the belt system of an occupant. So the seat belt that you use, it has a pulley at the base of your seat or on the corner of the base of the seat.
And usually that is represented in FEA using a three-noded spring.
Part 2
So important thing to understand here is there is spring 2, spring 2-noded and 3-noded. Out of that 3-noded is very rare use because it is only used in that particular application for seeds. Whereas spring 2 or the 2-noded spring is very commonly used. Now let's play with this 2-noded spring. Now we know that spring can be of many types. You can have linear stiffness on the spring, long linear stiffness, non-linear is much more practicable whereas linear is not too much. No spring as such is completely linear but as long as you are dealing within the yield limit of that particular spring then that could behave linearly but many springs as such are non-linear.
So in order to take care of such non-linearities we also need to apply some properties to that and this is where it actually gives us an option to do all such things. Now this property, the spring property is a core topic of a solver such as Radius or LS Dyna. So if you have different solver such as Dyna or Radius you can have different card images here. So because this is a Radius profile it is giving us options of only Radius cards. You can assign some mass to the spring.
Now because we are following kg millimeter millisecond system, 4 is actually a 4 kg of mass that is being applied on these 2 springs. And then the stiffness, so initial stiffness let's say 50 kN per mm because now the force unit is kN, distance unit is mm. Now 50 kN per mm is really tough stiff, very stiff so keep it 1 kN per mm. We can always allow some damping that can be very much alike how suspension strut can be modeled using a spring. So you can add some damping and then there are ABD that is based on the strain rate and then there are other functions which you can use to put dx dt that is distance upon time.
So that is actually the strain rate versus strain rate versus stiffness or force and then there will be a failure value for each spring that is negative value negative failure displacement. So if you try to compress the spring by too much more than what the distance we say here it will try the spring will fail. It will simply get deleted and that way you won't have any connection between these two nodes after that. Alright, so we don't want to discuss too much on this right now because this is very specific to a solver.
So with that we have completed the spring topic as well. Now another important topic that is connectors which leads us to weld elements. So when I hit connectors, the good thing about connectors is that it is a geometrical entity and not an FE entity. And connectors really remember the location of your welds. So once you remember the location of welds, you can imagine when we are redesigning something or when we are doing the design iterations. For every new model you have to create the welds again.
Now while recreating if you have a connector data from the previous model then you can simply import that here and you can simply create the welds using that connector data. Now the first question though is how to create a basic weld. So we know that there is spot weld, there is seam weld and there are many more things. We will cover only spot and seam here. So for the spot weld, first of all when we are dealing with connectors, what I recommend is let's go to view, browser, HyperMesh and then we go to connector.
So that will open a new browser over here. Meanwhile just as a precaution, I also create a new component and name it as welds. Ideally when we are trying to create a weld element, a new component will be created by itself. So while creating spot, imagine what all information do you usually need. You need a node or you need a location where you want to create a spot weld. So that location is being given here. Now you also need to understand how much is the actual distance between these two panels.
I know from because I have created this that the distance is 10mm. This is an example. So usually in reality the distances are in 2mm max or 3mm in order to weld two panels. Now here because I have distance 10, I'll need to use some tolerance for this node to find its counterpart on the other panel while creating a weld. So I have selected this node as well as this node. So I have two nodes. I need to tell what components needed to be connected using this weld and then I'll hit create and it creates a spring element again.
And that spring is actually representing the spot weld that we just created. Now if you realize there is a new component that has been created here. And if you see the groups, there are two new entities that have arrived. The type here, the type that I selected was type 2 spring. And that has a significance. Now when we study contact interfaces, we'll study these two things. But the important part here is when we create weld element using spring 2n. There are few boundary conditions that are needed to be applied and that is what is happening over here.
Now this was about spot weld. Now we knew that these two are the points where we need a spot weld. So we created that. But the seam weld. Now some cases are those where you need to create a simple seam weld line. And there, instead of actually modeling some material, what is usually done is you'll simply select from which node to which node you want the seam weld. And then you'll add some spacing. So because the mesh size right now is already 5mm, I'll change the spacing to 3mm just to see that effect.
Not to mention again the type here that I have considered is type 2, single row. And now we know what does it connect and then there is tolerance. When I say yes or say create, it has created a new component again. This time it has also created two new groups that is contact interfaces. And now we see because we gave the spacing as 3mm, it has created weld elements at every 3mm. Now the next question lies is how to use this connector data. Now this connector browser is actually going to tell me if my welds are or my connections are successful or not.
And they are successful. Just that now we need to be smart and that is why. Once we create any weld or once we complete our model, we try to export that. Now you can save as this model as an HM file. So that is one way of preserving or storing your data. Other way is, now since we have done significant work on these two panels, you can go to export. You can hit solver deck. Now, if you hit solver deck, this setting will export this mesh as well as this 1D elements to some secure location or to a location that we select.
And that exported data will be written in .rad format and that can be imported back to work further. But apart from that, preservation of connectors is also important because that is something that is not preserved in a radius file or even a solver file. So here in export, we have an option of connectors and here is where it asks for XML file. So maybe you can save 1D connectors and it will export all the connectors that we have created. So, so far we know that there are three connectors that will go to that special documentation.
So from now or until now, we know that there is a difference between RB2 and RB3. RB2 is most commonly or more commonly called as rigid body in case of radius or dyna. Whereas apart from rigid bodies, we also studied beam and truss elements. We need to, so the trusses will be used only in actual loads. Whereas beam can be used anywhere because it has that degree of freedom and the local coordinate system. Whereas spring, as long as, as long as we have the local coordinate system or we have something else, we should be good to go for the springs.
So once everything is modeled, the most important thing that we do is export and that will save this data in case of, in terms of FEA. But if you really want to, because now the connector data is actually CAD data, you can export this and refer to this for, for any general understanding from here on. Obviously, the welds that I have created over here, those are not the approved welds or those may not be always the approved welds. So an engineer needs to make sure of that, that the welds are getting created at the right location.
Alright, so once the export option is done, you should be able to use the same file again with import feature. And then you will, so the exported file can be imported using this particular option. So that completes the 1D element topic from, from HyperWorks point of view and the export topic as well. and the production file can be explored. Now, let's get started. Now first, make sure the
Part 3
Today, we will start with RADIOS introduction and learning what is exactly going on in RADIOS when we are solving a crash analysis problem. So, as we go on exploring RADIOS over the process, we will end up learning some important and basic concepts in explicit solvers. And while doing that, in the end, we are going to reach the stage where we can run our crash analysis projects by ourselves. So, just to give an overview, we will start with an introduction, what exactly is RADIOS, what kind of files the RADIOS uses and what is exactly there inside those files.
Then we will look at the time step that is usually used in case of RADIOS. So, how the time steps are going to be calculated for in general purposes and then we will move to elemental properties. So, so far, since we have learnt HyperMesh and we have learnt meshing, we have seen there are three different types of elements, 2D, 3D and 1D. So, in all those cases, the way the time step is being calculated is different. So, we will be studying that. Right after that, we will be looking at metal properties and how they are defined, how exactly the metal is being applied to some particular component in crash analysis.
Right after that, we will get introduced to hypercrash, which is a specialized pre-processor for RADIOS. And once we know how to use hypercrash, so this will be more of introductory session for hypercrash. But right after that, because we will be studying elemental properties, material properties over and over for many of the examples, we will get accustomed with hypercrash over the time. And right after looking at hypercrash, the idea is to study interface modeling. Now, interface modeling is nothing but contact interfaces, which is deciding the interaction between two meeting components.
So, if your car is hitting a barrier, the interaction between car and barrier, what kind of friction should go, what kind of forces should be calculated. So, all those things that comes under interface. And please mind that, time step, the introductory session for RADIOS, element properties, material properties and interface modeling. These four are the most important topics in RADIOS. If you understand these well, then rest of the topics like kinematic conditions, that is more like how do you how do you set up the boundary condition or let's say constraints or degrees of freedom.
How do you set those up? That is usually discussed in kinematic conditions, which is pretty easier to pick up compared to the first four. The first four are very important. Then comes the load definition. We'll see how we can apply constant forces or dynamically variable forces or maybe even the initial velocities. And then, by that time, we'll be confident enough to run a simulation by our own. The assignments, assignment workload by that time will be enough to get you some confidence on running a model by yourself.
And then we'll look at some methods to increase the simulation speed. So, again, if you have understood time step very well, right in the beginning when we are discussing time step and element properties, then you'll probably get this time step control method very well. And then output request, that is just like seeing how you can request a particular force for particular element. Because many times in a car, you have millions of nodes. Now, you want to point out to the solver in particular which node you are interested in looking at when you are looking at results.
So, perhaps what solver will do is it will try to calculate exclusively what are the accelerations or what are the forces that are being experienced at that particular element. And then you can simply see that it's deliberately kept in the last is debugging an error. So, while running a simulation, if you go wrong with any of these steps, there is a definite chance that you'll end up in an error or your simulation may not run at all. Even if your simulation runs, you'll end up in a non-physical result.
Now, what is a non-physical result that also will come to know over the time. So, all such errors which are easily detectable or which are not easily detectable, all those will be looking at in this particular topic or section. So, let's start with the radius introductory part. So, all this material that we are discussing is actually available pretty much on HyperWorks help website or even Alter University website. They have shared some really nice documentation and that was very helpful while getting this material to you. So, while we open radius, there are couple of files that are usually looked at.
So, whatever your run name is, underscore zero zero zero zero dot rad. So, mind that there is no change in this name ever. After that, there will be run name, the same name as whatever you are saying here. The same name will be here and then underscore zero zero zero one dot rad. Now, when you are running in a normal mode, as in you have one model to run and you have all the simulation to be run in one shot and there are no installments of running.
So, let's say you want to run a model for let's say 100 milliseconds and then you want to run the result of that model for next 100 milliseconds without doing any structural changes but by only changing some velocity or some output request. In such cases, the next file will be two dot rad and three dot rad and so on. But essentially, very important, the basic minimum required files to run any radial simulation is these two files. Run name zero zero zero dot rad and one dot rad.
So, this zero dot rad is actually called starter input deck and one dot rad is engine input deck. Now, why the names are like that? We'll see. So, actually the zero zero zero dot rad file which is starter input deck, it consists of all the model information. So, all the nodes, all the mesh that we are creating, all the load definition, initial velocities or all types of boundary conditions. Everything that we create in a model that is included in this zero dot rad file. Now, that tells you how crucial this file can be.
The good thing about it is because it is written in a text format, you can actually open these files in notepad and you can edit the numbers. So, let's say if I am applying a velocity of let's say 100 meter per second, you will actually see that 100 number inside this text file. So, if I want to change that speed to 110, instead of opening the whole model in hyper crash or HyperMesh, I can simply open the text file, change that number to 110. And if I run that simulation, I'll see the velocity as 110.
So, it's as good as editing a text file if you really understand the format well. Obviously, when you have model information, you also need the information on how much time you want to run the simulation for, then what are the simulation speed control parameters that you want to see or are there any special output requests that you have. So, all such requests are handled in engine input file. So, starter input file is only model information that is the starter information. Engine input file is actually the information given to the radius engine.
That means, well, just the connotation of the word engine, it gives you. Engine is something that runs the whole show. So, that means your engine file is going to tell by what speed your simulation should be running, up to what time your simulation should be running and what all things you want to extract from the simulation. So, that's why usually engine file, the parameters inside the engine file will be responsible for what is the number of animation files that you are getting or what is the number of time history files or what is the size of the time history file that you are going to get.
Then this restart file, this is usually useful if you want to continue the same simulation ahead with maybe some other engine file parameters such as other speed or other end time or maybe other output request. So, in such cases, this 1.RST that is result file is being carried forward. Whereas for starter file, the output that we get 0.RST and usually that is the only output that you will see from starter file. So, starter file will also be responsible for one particular type of output file that is 0.out.
Notice the convention, if the starter file is 0.rad, even the corresponding output file of the starter is 0.out. Whereas for engine file, 1.rad gives you 1.out. Now, again, because starter file has all the model related information, you will see that 0.out file also is giving you the information as what the radio. So, okay. Solver has understood out of your model. So let's say if you apply one particular material for 10 different parts, you'll actually see the mention of each and every part in outfile, 0.outfile, and for each and every part, it will reiterate what kind of material is being applied for that. So it means you are giving the instructions to the solver in your own language, but what solver understands is all written in this 0.outfile.
So usually it is a good idea to look at 0.outfile to understand what exactly the solver has taken. Usually in beginner stages, this is a very good idea to do. Later on, you'll understand what all things could change or could not change at all in 0.out. And that way you can start focusing on maybe one or two particular things out of 0.out. Then we come to engine.outfile such as 1.out. Now this 1.out is going to tell you about the energy balances or at what time your current simulation is running or how much time is left for your simulation to finish or how much time was taken for the simulation to finish.
All such information will be stored in 1.out. So we'll be looking at the snapshots for all these four types of files, 0 and 1.rad, 0 and 1.out, and that should give you a little more idea on what exactly I'm trying to say here. So there we go. We have a starter file. Now this is exactly what I was saying earlier. It gives you 0.out, 0.rst, but inside the starter file, as I said, it exists in a text format. So this is much more like any syntax, any programming language syntax. It starts with, let's say, in case of C language, it starts with some include file, include console.input.output.h.
Just like that here also in radius, it always starts with this keyword begin. Now after that, you'll have your title of the whole simulation. So right now, generic name, run name, right after that, this is the version of what exactly, what kind of radio solver version you are using. So that version is usually mentioned here. And for all these, the documentation for all of this is usually available in the HyperWorks help. So if you go there and type the word slash begin, it will give you the syntax for this.
So it will tell you what is supposed to be on the next line, what is supposed to be on the line next to that. And then it will tell you block by block information that this block should have the version number, the next block should have maybe some other variant. And right after that is the unit system. Now, this unit system is pretty crucial. Now, radius doesn't exactly work in whichever unit system you want. They have a few sets of unit systems out of which you have to pick one.
You have to mention it here in the beginning. And then you have to make sure that you are following the same unit system throughout your input. Right after that, you see rest of the information such as title of the model, then material information. Now, here I see there is a elastic material defined. That's why the name also is given as an easy convention, linear elastic material. Now, as the syntax says, density was mentioned here, elasticity value was mentioned here. Now, see that it is elastic material and from the numbers, I can tell you that it is defined for steel.
And now for steel, the density is actually 7.8 gram per cc. Now, because they are following this particular unit system, they have to put these values in mega gram per cubic millimeters. So, it is 7.8 e raised to minus 9 tons per mm cube. That is the density that is being mentioned over here. Same is the case with E. Now, if you have weight or if you have mass into mg or mega grams, your elasticity value, which is actually nothing but newton per meter square or the unit system is newton per meter square, equivalent unit system will be used.
So, in this case, it could be kilonewton or it could be something else. We have to be sure on what exactly are we trying to, what kind of numbers we should be putting up. So, from that experience, I know that elasticity of steel, Young's model of steel is 210 GPA, 210 GPA, that is 210,000, megapascal, that is 210,000, newton per mm square, which in the end corresponds to this particular unit system. Then new, which is unitless, really, and then nodal information and rest of the information.
Now, notice that in node, they have given the node ID, which is actually the syntax, and then right after that, you will see the coordinates of that particular node. So, node number 51 exists at x equal to minus 64.95 and blah, blah, blah, at y coordinate 23.87 and z coordinate minus 4.57. Now, from the numbers, you can see that these two points lie very close to each other. In fact, their x coordinates and in fact, their z coordinates exactly the same or similar, y coordinate is about the same, but only the x coordinate has changed by almost 10.
Now, what 10 is it, it is the distance unit system here, that is mm, that's why I can say that these two nodes differ in location by around 10 mm. Now, that is really a rough case, you will never have to do such cases in looking at these files, but I am just trying to give you a meaning of whatever we are seeing on the screen here. So, again, in the help documentation, you will also see what is the length of this particular block, what should be the length of this particular block when you are mentioning a node.
If you are looking at material information, then you will see that these blocks are actually of the same length. So, right after this minus 9, a block ends and usually all these numbers and the words are right aligned. So, that's why they exist at the end of the, end of the tab, right after that, the same number of spaces have been left for the next quantity. And the next quantity has, because it has a single digit, it has gone all the way to the end of the tab.
Now, about unit system, as I mentioned, we have a few sets of unit systems defined. Now, though in this case, the unit system defined was MG, that is megagram, millimeter seconds, for better precision in our simulations and even in the industry or OEM levels. Now, OEMs are nothing but original equipment manufacturers, that is, all the car manufacturing companies or even the heavy machinery facturing companies. All those, they usually care a lot when it comes to explicit analysis and when there is a time concern, usually your time calculations.
So, a typical graph scenario happens within at the most 150 milliseconds. Now, in such case, if I try to use second as my unit system for time, I'll have to write that as 0.15 to represent 150 milliseconds. In terms of seconds, now, in that case, it is very likely that 0.15 might look very negligible, it might get rounded off to 0.2 or it might get rounded off to something else. And because of that, it's usually a good idea to use a more precise unit, that is, millisecond.
Now, because I'm looking at 150 milliseconds, my degree of change or tolerance has actually come down to 150 milliseconds, so 151 or 149. Now, on global level, that won't make much difference. But if you had considered seconds, then because we have already lost all the significant digits, 0.15, well, it could get rounded off to something else. Same thing with rest of the quantities. Now, for length, I feel that I can imagine mm much better than meters because, well, we keep looking at scales all the time being engineers.
And then we have mass units as kg and rest of the units which are derived from all of these are continued over there. So, because we have mass in kg, time and length in millimeter and millisecond, your force, which is actually kg meter per second square, if it is 1 newton, in order to compensate for that, the force unit has been adjusted to kilonewton because your time unit is actually very less or very small. Then pressure, same thing with that, kilonewton per mm square is actually GPA.
Now, I'm just following the same unit system, so kilonewton per mm square usually go for 10 rest to 3 into newton per mm square, and newton per mm square is nothing but megapascal. That's why we go to 10 rest to 3 megapascal, that is 1 GPA. And then velocity, well, we are free there because velocity can be used in millimeter per millisecond or meter per second now because this is, this is more about getting cancelled in the division, and that's why you see different materials, unit system here, but it's actually nothing but the same.
Then this is about density, energy, and g-value, that is acceleration due to gravity, so because it is 9.81 meter per second square for this case. Now, because we have milliseconds, it's actually a good idea to use E rest to minus 3 in front of that. So, idea is just to keep consistent. If I'm following this line maybe, then I'll have to put all the quantities in respective row only. So, since I'm suggesting, you can start looking at this particular unit system and try converting number in your mind what it could be.
That will give you a good idea in what ballparks usually the number should lie. And that is why exactly the unit system is usually kept consistent. Now, let's get back to the starter file. Now, each block is going to define some feature. It could be nodes, elements, material, properties of elements or even interfaces. So, it starts with slash, then you have the rest of the syntax. And then, as I mentioned earlier, you have tabs here. And now, these are actually at the most 10 fields in a row.
And they are all of 10 characters. So, right now, we have consumed 5 of each, 5 of this particular tab. So, there are 5 more that could come just in case we need to reach for higher numerical range. And then, because we have the syntax, if you write out the files to hypercrash, it will give you a nice explanation of all such things. So, if you have a car, let's just say you have a component. Inside the component, usually, they allow, they apply a property. Now, this property of the elements is taking care of the thickness and some of the formulation inside element property.
And then, we also apply material. So, right after property ID, there is material ID. And that material is defined later. So, this is much more like calling a function at one particular appropriate location. And that function should be defined somewhere in the program. It's very similar to programming. And then, when we are looking at metal properties, there are element properties. So, thickness is mentioned 2.5 mm. And rest of the parameters we'll be looking at very soon. Then, the definition of elements. Now, because this is shell element.
That means it is 4-noded quadrilateral element that we meshed a few days ago. Now, these are the labels for shell elements. And then, rest of them are the node numbers. Now, these nodes will be defined again in the bottom along with their XYZ coordinates. Then, we come to the output files of starter file. So, the output file, if not just the material information applied to every part, it will also tell us the time step, what is the current time step that is going on on the minimum of the elements, rest of the diagnostics tools.
So, now it is saying no true in compatible kinematic conditions. But, there are 7 warnings which could be pointing me such things. So, this is just one of the warnings that can be ignored. Now, since we have the whole simulation ready, the next turn comes is off engine file. So, as I mentioned earlier, it is 1.rad file. It contains information on time steps, the duration, and then there is 1.rst that can be used for restart. So, this is the usual form of a 1.rad that is engine radius file.
So, this title should be, it may or may not be same as 0.rad file. But, here, for this particular keyword, we see that it is pretty important to keep the same running. Apart from that, there are other output requests. Now, we will be studying those towards the end part of the radius class. But, for now, we can just look at them how they have been created there, or how they must have been written out there. So, if you look at the anim, which is responsible for animation, what it is trying to say is animate all these results.
So, animate for brick elements, that is 3D elements. Tensor stress. So, that should tell me, or in my animation, I will have a special result ready. That is for this particular team. And, this is how the engine output file is going to look. Now, this will tell us about the time at which the simulation is running. The time step, which is, again, very important parameter to look at very soon. And then, errors, energy errors. So, in this slide, I have given very nice explanation of what all things mean to radius.
So, there are some basics that need to be followed. The radius file, the starter radius file, should always end with 0000.rad. So, here we come to our first example based on radius. This is more like an assignment for everyone. So, this model is going to set up an impact against a thin wall, a rigid wall. Now, the simulation time should be around 60 milliseconds. The thickness of the components should be 1.5 mm, which might have been already set up. But still, you need to go and check how to check the thickness.
Then, the initial velocity that was applied, the good call. That should not be applied to all the nodes, but only the master node of some rigid body. That's why the number there. And then, there are results requested. Now, just by looking at their syntax, you will understand what exactly they stand for. Animate, vectors, displacement, animate vector, velocities, and rest of the things. So, based on that particular problem, there is an engine file that is shared. You will have to, in this assignment, you will have to first calculate the speed of sound, which I will show you how to exactly very soon.
And then, the rest of the things. The time for sound to travel length at rail. Now, once you have a velocity of sound through the rail, and since you already know the distance from the mesh, it's easier for you to calculate the time. And then, we jump to time step calculations. Thank you. Bye. Bye. Bye. Bye.
Part 4
One of the important parts in radius is the time step. Now we'll see first how the time step is being calculated. So time step dt or let's just call it dt or delta t from here on, it is the time required for a shock wave propagate across a smallest distance in an element. Now that might feel complex but let's look at the picture on the screen. So this cage, now we are looking at a cross section of a mesh or it could be a 1D mesh as well.
So the smallest distance on this element is actually this length that we see. If you imagine whenever you have an object undergoing any deformation or it is being applied any particular load, all the loads that are being developed inside the body, they are transferring by node to node. This transfer is actually in terms of a shock wave and this shock wave is traveling at the speed of the sound. So when you actually knock on the door of any room, then you can say that the vibrations of the door are governed by the speed of the sound on the door. The same vibrations are even in the picture, any case of deformations on any metallic object as well or any complex structures such as any trusses or any complex structures in general. Automotive could be one more example.
So to simplify this, let's get back to our sketch here. So the time step is nothing but the time required for the shock wave to go from this point to this point. Now that looks pretty simple but the speed of the sound, now if you remember the speed of the sound through vacuum is 340 meter per second. What about the material that we are looking at? So that actually depends on the material properties. And those properties usually are Young's modulus, then Poisson's ratio, density, and any damping properties that material could have. So there are many factors and this speed of the sound calculation, it also depends on what kind of element you are using.
So that adds one more layer of complexity. But in simple words or just to keep everything to the basics, it is always based on the speed of the sound. Now if the speed of the sound, let's say with the speed of the sound, we are moving from one node to another and within that time, we are trying to calculate the force at this particular node and this particular node as well by the end of the by the end of that time step. But what if, what if we don't have this result ready by the time the wave reaches here? Now that actually creates the unstable condition. So this delta t, that is the time taken by the shock wave, so the time step in our solution, that actually is the time by which we should be ready with the calculation or the solver should be ready with the calculations of all these nodes before the shock wave passes to the next node.
So what happens is, now when we apply external force on this particular node, this is at the zero time, so there is no force in anywhere, anywhere else on the on the system. But once the force is being applied here, because of the shock wave, a shock will be passed to the next node, and then the next node, and then the next node. By this time we already know that the forces here are zero, then once the wave reaches here, because of the forces on this node, and because of the mass that has already been applied because of the density, this node will have some mass on it.
Now we have force, we have mass, that will give us an acceleration on the node. Now this acceleration will help us determine, over the time, what kind of distance this node will be travelling in whichever direction. Now that direction again depends on the direction of force, because all these are going to be the vector quantities, that displacement is actually inspired because of this force in the end. So force to acceleration to displacement, and in between we also calculated velocity. So once I have this distance, this node moves by some amount, now because this has moved by some amount, this material has undergone some deformation.
Now that deformation is leading to a strain, and this strain is going to lead to stress. Now when the stress gets generated here, by that time we have, because of that stress, strain and stress, you see that there is a curve which goes on increasing until the elastic limit, and then it might become flatter. There is, the area under the curve is actually nothing but the internal energy or the strain energy that is being absorbed by the material in the local region. So once it absorbs some energy, this force is going to diffuse a bit, and less force is going to travel at this node.
Now this node, again the same things are going to happen. We have force, and we have nodal mass, so mass and force is going to give us acceleration. Acceleration ultimately will give us displacement, and the displacement is again going to lead to some energy dissipation and further transmission to next node. Now you can imagine, if this material is too stiff in between, you will see that because the material has not deformed by too much, most of the energy or very less energy has been absorbed. And that is why the force has diffused very less, that's why more quantity of force has already passed to the next node.
Now what will happen if we have more forces on the next node, compared to lesser forces? More the forces we have, more the displacement we have. So that means, more the energy we absorb over the material, less forces are going to be transmitted. Isn't that what exactly we discussed in the very first session, when we were talking about the principle of crash, or the crash physics. We are trying to absorb energy over the material, and by that means, we are trying to diffuse the loads. And that is why, if you have a car, and you hit some barrier, or some object, rigid object.
If your car structure is too stiff, you are going to feel more jerk on the inner end, that is the passenger end. Whereas if your car structure, the frontal structure is little weak, or it has been made weak to absorb the forces, so that the material deformation would happen over the time, or in between that distance, you will get less forces, or you will experience less jerk inside the car. Now that is how the explicit analysis works, and that is exactly the reason why it is being used for crash analysis.
Now, obviously, by this description so far, we have discovered that the smallest distance between this and the car, this node and this node, it is going to play a crucial part in deciding the time step. Because, more the distance, more the time will be required by the shock wave to travel across one node to another. So that is why, smallest element size, that becomes a parameter. And then, sound propagation speed. Now, material to material, that speed is going to be different. And that is why, the speed also makes little difference.
So, let's say if you change your material from steel to aluminum, sound propagation speed is going to be different, because you have different elastic modulus, or Young's modulus, and you have different density. But in the end, when we look at the sound propagation speed formula, you might understand that it depends more on their ratio than their absolute values. So, you might say that steel has more Young's modulus, or higher value of Young's modulus, higher density, whereas aluminum has less stiffness as well as less density. But because their ratio might still be around in the same region, that is why, the time step, whether we change from steel to aluminum, the time step remains in the same ballpark, or very similar ballpark.
Now, that is a very good hint for the assignment that is upcoming very soon. So, now, to understand this better, I found one link on Quora, which is very, very popular. Let's quickly take a look at what exactly they have written. So, I have purposefully, I have written what is the time step in explicit solvers, but the Quora answer that we are looking at, it is going to tell us an answer specific for LSDyna. But let me tell you, if you replace the word LSDyna by Radios, whatever is written on the screen is perfectly true, because that is the whole principle of any explicit solver.
Whether you do an explicit analysis in Radios, or in Dyna, or even in Abacus, or even in Ansys, all of them are going to work on the same principle of time step calculation. That's why, this answer is going to be unique, or going to be the same, for all the explicit solvers. And, whatever I explained just now, that if you have force entering at one node, then you will have it transferred across all the nodes. And, now in this case, because it is a 2D example, they have shown, this minimum distance actually makes more sense.
Now, in this case, the forces on this node could travel to node number 16, 17, or 22. It will reach the earliest at a node, which is closest to node number 21. And, that is why the smallest length of the element, that matters the most in this case. Now, many times, now this is a very, very good regular mesh. But, if you had any distorted mesh, then in such cases, the time taken by, by the shockwave, to travel from this particular node to the edge of the, to the opposite edge of the element, that could be the minimum length that it needs to travel, or minimum distance it needs to travel.
Because, as long as it reaches the edge, that edge is going to transfer the rest of the shock to the next element, and subsequently, the rest of the nodes. So, again, in that case, the height of the element could also become your minimum length of the element. So, getting back to the presentation, smallest element size is crucial one, sound propagation speed is another crucial factor. So, just to give you a hint, if you go to Quora, you should search with this particular keyword, what is the time step in LSDyna, and you will get this, get this nice, Basically a nice answer written by the person over here. So definitely give it a try reading that and it would give you a much better understanding on what exactly the time step is. So the language over there is pretty simple. You won't have to get into too much complex stuff that follows in the end of that answer. But just try to understand what exactly or how exactly the time step is working in the solver. So further on time step, now let's look at some formulae.
So the elemental time step in general, let's say if you have single degree of freedom element, that is 1D element, then the time step or the critical time step can be again L by C. So L is actually the length of the element because now you have 1D element. The minimum distance between node to another node is the length of the element. So there is no much confusion there. Purposely I have taken the formula for only 1D element just to explain in the simplest terms. And then once you go into 2D or 3D, element arena, then this expression gets little more complex. But in simple terms, it will be sufficient for you to remember this particular formula to calculate to roughly guess what could be the time step or for many other cases.
Well, L is the length of the element and then C, that is the speed of the sound through this material. It actually is a very simple formula for 1D element, that is square root of E by rho. Now E is your Young's modulus, rho is your density. Now you can imagine when you have 2D element, obviously you have two different directions and that is why it can involve some other moduli as well, unlike 1D element. Then comes the nodal time step. So this time step is actually the one that governs your speed of the simulation.
Whereas this time step is actually the length of the element. So main role of elemental time step comes down to deciding length of the element. Whereas the nodal time step, if you control this one nicely, it is going to decide your speed of the simulation or stability of the simulation in many cases. So the nodal time step, again if we go by L by C in this case, because it is nodal time step, there is no much sense in saying it should be dependent on the distance. But just by simplifying this particular formula and considering the distance as unit, they have come up with a better formula and that actually gives a nice idea on nodal time step.
So here is one example for us. We have mild steel example or mild steel case where we have density of 7.8 E minus 6 kg per mm cube. Now this is the same material that we saw yesterday in the radio starter file example. We had 7.8 gram per cc density of steel and Young's modulus in that particular example was 210 GPA. Here I am considering a different grade, so 205 GPA. Now the target or critical time step that is delta T over here is 0.5 microseconds. Now remember this number very carefully because this is the common time step that is being followed in many many OEMs. So 0.5 microsecond in the usual units that we understand the seconds, it becomes 5 E minus 7. The task for you, quick task is to calculate the minimum length of the element to maintain this time step.
So task is easy. So task is easy. You have to substitute these values here and you have one value over here. You just need to find out L. What is exactly the L? This will be a good exercise for you to understand the concept of time step. So try to get this answer. Take a couple of minutes break just for this and come back.