Jump to content

Omer Faruk GUMUS

  • Content Count

  • Joined

  • Last visited

About Omer Faruk GUMUS

  • Rank

Profile Information

  • Are you University user?

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Mr Kosuke; Thans for your video record and demonstration via examples. I need to improve usage of NVH utilities on Hyperworks. Do you have any extra examples or documentation related NVH Utilities to be shared ? Thanks in advance
  2. I have a similar problem as @ep2398 experienced. I converted Radioss A001 result files into h3d file utilizing HVtrans. In Hyperlife, different kind of stress results are available in time series and result can be seen in Transient Response as subcase. However fatigue analysis results are stiil receive as N/A for both damage and life. Why fatigue analyses can not solve the problem, though explicit analysis is performed time-dependent event with time dependent loads?
  3. Hi, I tried to do Transient fatigue Analysis in Hyperlife , and I have a h3d file generated from Radioss and it includes Stress result by time. But Hyperlife do not see the result as a Subcase to be inputted in Load Map. Radioss h3d output is supported in Hyperlife for the fatigue assesment ?
  4. Hi, While explicit analysis, I could get one A000 File per 10 minutes once used 4 core , however, I could get one A000 file per 14 minutes once used totally 8 core (+4 logical processors) . How much I increase the logical core numbers, getting A000 animation files speed is getting slower. Another computer we used have totally 72 core ( 36 of 72 are logical processor) has same situation when we include the logical processor in radioss as -nt .. Dou you have any suggestion to speed up our explicit analysis when we would like to use logical processor in PC ? , Thanks in advance.
  5. Thanks Mr. Pranav. I actually wondered about if a mass and inertia are unnecessary just only when I create the spring by two independent nodes. In the video , the instructor could write "0" for mass and inertia in hypercrash interface. But it is not possible to set 0 value for mass and inertia in hypermesh interface , if you try, you'll get * sign with red color. So, so zero length means that mass and inertia are not taken into consideration ???
  6. Hi, https://altairuniversity.com/learning-library/v_e_spring-element-type-8/ In the first example of the video on the link above, instructor has two cylinder laid in same axis. Each cylinder has one RBODY with their whole nodes. And RBODY's independent nodes weren't created using calculated nodes. Then, how did he create "zero-length" spring as he told in the video ??
  7. Hi, I would like to model a door latch mechanism with pin wrapped a spring as below. So I read in radioss book and hyperworks help that it is recommended to use a Type spring 8 to represent a revolute joint. But as you guess, that type of spring has tension in the static state, and as it rotates its tension increases. So how I implement this situation for pin surrounded with spring in Radioss? Thanks in advance.
  8. Thank your kindly answers @Ivan and @Prakash Pagadala. However I see your explanation above, I would just to know why I'm in trouble with the model when I import a radioss model inside and delete the ^temp comp from the model. I guess the ^temp component's surfaces connect directly to contact surfaces. So, deleting the ^temp comp from model effect the contact surfaces , then solving it after export is not possible. Do you have any suggestion to get rid of this issue?
  9. Hello, Once any radioss model is exported to solve the model in Radioss solver, then reimport the model back, I can see that the .rad input deck file created a new component named "^tempCompSurfSegment" . Why exactly that kind of component is added into the input deck? In additionally, if this component is removed from input deck, radioss solver would give an interface error ? I would be appreciated if I knew more about this component created in each time. Thanks in advance.
  • Create New...