Jump to content

Rahul R

  • Content Count

  • Joined

  • Last visited

  • Days Won


Rahul R last won the day on November 7

Rahul R had the most liked content!

About Rahul R

  • Rank
    HyperWorks Specialist

Profile Information

  • Gender
  • Country
  • Are you University user?

Recent Profile Visitors

12351 profile views
  1. Are you using Student Edition or Full version?
  2. When saving runs from HyperStudy in FluxMotor catalog, the name of the HyperStudy approach is used in the motor name, and since HyperStudy 2019.1 version, this approach name can contain dash, which is a forbidden character in motor names, causing a failure when the motor is saved in the catalog dedicated to the current optimization project.This seems to be an issue and may get resolved in upcoming version of Fluxmotor. If it too urgent then I would recommend you to use HyperStudy 2019 to bypass this issue.
  3. I don't think this is error.If it is error, then it would have listed out with some message in the status bar. Note: Its always recommended to use the latest version(For 2017version the latest patch was 2017.3 and for current version 2019 the latest patch is 2019.1)
  4. I see you are using HyperStudy 2017.1 and would suggest you refer attached document for ARSM based optimization algorithm for termination of optimization. ARSM 2017.2.pdf
  5. Could you please share the screenshot of message log of HyperStudy?If possible please share .xml or .hstudy file.
  6. Can you try this with the latest version of HyperStudy 2019.1.
  7. Which optimization method you are using?Also try by setting the ignore failed evaluation.
  8. Which version of HyperStudy and Flux you are using?
  9. Which verion of OptiStruct you are using? Could you please share the .out file of the run?
  10. This error occurs when a model is under constrained or incorrect material property definition or contact definitions are incorrect or missing.I see there is no connectivity between nondesign and hardpoint component.Equivalencing nodes should help to run the optimization.
  11. XY entries in TABLED1 you define directly or use utility: Table create,if you have XY in csv format.Where you are facing problem?
  12. Rbe3 and Rbe2 should work for all types of analysis supported in optiStruct.Can you try running analysis using MECHCHEK control card.If still gets error then please share the .out file?
  13. Wear simulation is currently not possible with OptiStruct. Attached screenshot covers some highlights of OptiStruct 2019.1.
  14. For analysis where small deformations are assumed, there should be little or no difference between the true stress-strain curve or engineering stress-strain curve. Either of them can be used in TABLES1 definition. For large plastic strain simulation, the true stress-strain curve should be used. Recall: True Strain = ln (1 + Engineering Strain) or ε = ln(1+e) For example, if e = 0.05 (5%), then there is a 2.5% error in ε
  15. Do you want to input surface roughness for fatigue analysis?If so then you could use PFAT Bulk data entry to define same.
  • Create New...