Jump to content

Leaderboard


Popular Content

Showing most liked content since 11/20/18 in all areas

  1. 3 likes
    Hi, Deleting those files usually helps, Or you can write a .bat files like below: "C:/Program Files/Altair/2017.3/hm/bin/win64/hmopengl.exe" -nouserprofiledialog -uOptiStruct Search HyperMesh Startup Options in Altair Connect or in Help doc for more info.
  2. 2 likes
    The virtual wind tunnel you show in your screenshot if very small for any reasonable aerodynamics results. You might get colorful picture, but probably no useful interpretation. Wind tunnel dimensions: o 5 car lengths ahead of the car o 10 car lengths behind the car o 5 car widths on each side of the car o 10 car heights above the car o i.e., wind tunnel dimensions LWT x WWT x HWT = 16Lc x 11Wc x 11Hc. o The mesh farther away from the car will be coarse and increasing the wind tunnel domain would not affect the element count too much but it would still affect the B.Cs if they are too close to the car.  Boundary Layer details o First layer height will depend on the freestream velocity to obtain a maximum y+<100. A first guess would be 0.2mm<y<0.5mm. Ideally y+max<30. o For some applications y+max<100 should still give good results o growth rate of 1.3 o number of layers 5 o all tets in boundary layers
  3. 2 likes
    Hello @LFM1995 If you still have the hexa elements, please try this. hm_entityrecorder elems on; *createmark elems 1 "by config" 208; foreach elemid [hm_getmark elems 1] { lassign [hm_entityinfo centroid elems $elemid] X Y Z; *createnode $X $Y $Z; set center [hm_latestentityid nodes]; foreach nodeid [hm_getvalue elems id=$elemid dataname=nodes] { *createlist nodes 1 $center $nodeid; *createelement 2 1 1 1; } } hm_entityrecorder elems off; set newplot [hm_entityrecorder elems ids]; if {[llength $newplot] != "0"} { hm_createmark elems 1 $newplot; *configedit 1 "bar2"; } hm_markclearall 1; Download --->>> CreateBeamForCentroidHexElements.tcl
  4. 2 likes
    I'd like to share the seamless integration that Compose with other HyperWorks applications, such as HyperMesh and OptiStruct. In order to expose the Compose function to other HyperWorks applications, we need to register the function. This is done clicking on the right mouse button on Register Function in Compose: After this step, we may now see that the function has been registered under the same mouse click shown above under Show Registered Functions button. Once it is registered, we may now use it inside other HyperWorks softwares, and the function will be available without the need for closing and reopening the application of interest. Example in HyperMesh: Why Compose and HyperMesh? Matrix Browser queries and modifies HyperMesh and HyperView data entities without writing cumbersome TCL coding, along with a Math method developed in Compose. Example in HyperGraph: Why Compose and HyperGraph? Plotting capabilities of HyperGraph are expanded with Compose’s advanced functions and custom procedures developed by the user. Example in HyperView: Why Compose and HyperView? Advanced post-processing or special mathematical approaches may be applied directly on the model. Example in HyperStudy: Add a new output response Define a new expression Use your custom Compose function Why Compose and HyperStudy? User-defined functions to perform design exploration and optimization. Example in OptiStruct: Why Compose and OptiStruct? User-defined functions to perform optimization with DRESP3 card (desired response based on external files). Regards, Roberta
  5. 2 likes
    Thank you very mush!I use it to check a solid.It shows Intersections found.But how can i see the intersection facets?
  6. 2 likes
    please Try this: variable list1 proc framework args \ { *createmarkpanel comps 1 "Please select the components "; hm_framework registerproc getorderedcomps graphics_selection_changed; *clearmark comps 1; } proc getorderedcomps args \ { variable list1; lappend list1 [noIntersect;]; } proc noIntersect args \ { variable list1; foreach item [hm_getmark comps 1] \ { if {$item in $list1} \ { continue; } else {set comp $item}; } return $comp } framework puts $list1
  7. 2 likes
    Hi Manjunath, You can do it via: modelHandle AddResult $resultfileloc
  8. 2 likes
    Hi, We can use tool edges to create feature elements all along the free edges of your model, these can later be used to create shell cross sections and change the configuration of these feature elements to create 1D feature models of the original solid or shell models. https://altairuniversity.com/wp-content/uploads/2013/09/Tool_Edges_TTF.pdf Plotel elements can also be converted into CBAR and CBEAM elements. https://altairuniversity.com/wp-content/uploads/2017/03/1D_Elements_Extract.pdf
  9. 2 likes
    *createmarkpanel nodes 1 "Select a node on the edge" 4 set nodes_aroundhole [hm_getmark nodes 1] eval *createmark nodes 1 $nodes_aroundhole *createstringarray 4 "Remesh: 1" "AdjacentComp: 2" "CurvedFill: 1" "DefineMaxWidth:0" *fill_fe_holes 1 1 0 1 4
  10. 2 likes
    Okay, it kind of got solved. For everyone who has thr same issue. The System or the Mateial orientation dialog does NOT work for this. (2017.2) However you can create a coordinate system und put it into the property as CORDM. Select "USER" and choose the coordinate system. The materila will orient itself around the X-axis.
  11. 2 likes
    Hi Set w .wDemo Destroy $w Toplevel $w Wm transient $w . For {set i 1} {$i<5} {incr i} { Frame $w.f$i Label $w.f$i.lbl -text "Input $i =" Entry $w.f$i.ent Pack $w.f$i.lbl -side left -anchor w Pack $w.f$i.ent -side right -anchor e Pack $w.f$i -side top -anchor nw -fill x } Button $w.b -text Proceed Pack $w.b -side top -anchor e
  12. 2 likes
    Hi Use *entityhighlighting 0 hm_blockredraw 1
  13. 2 likes
    Hi, In your code, destroy .window11 will close the window. Not sure how to close it as soon as you enter a value.
  14. 1 like
  15. 1 like
    Hi pmcardle The incident field is indeed excluded in the far field.
  16. 1 like
    Hello @John1989 The FDTD solver currently only supports wire ports and edge ports, so you could use a pin feed to excite the waveguide if you want to solve it with the FDTD. You can refer to Example A-11 in the Feko Example Guide: The model that uses a pin feed to excite the horn antenna can be switched to and solved with the FDTD. It is on the development roadmap to support waveguide ports for the FDTD solver. If this is of importance to you, or if you would like to be informed when it is supported, please request this through the official support channels - see Altair Connect for support contact details or to create a support request. Kind regards Madelé
  17. 1 like
    Right. You need to establish the AcuSolve environment. It looks like you're running bash. As explained in the HyperWorks Installagion Guide, you should include the following in your ~/.profile file source $INSTALL_DIR/altair/acusolve/linux64/script/acusim.sh $INSTALL_DIR is the chose installation directory. Then you can issue the acuRun command with options from your problem directory. (You can use which acuRun to make sure you've correctly established the environment.) You can also add that line to set the ALTAIR_LICENSE_PATH environment variable to your ~/.profile file. We typically use the local (in the problem directory) Acusim.cnf file to specify the problem name and other options.
  18. 1 like
    Hi @Bidisha Barman, Maybe you can make use of the "Scope" in the far field request. There you can select which faces/wires are taken into account for the far-field calculation. You could for example select only those faces from the one element you're interested in.
  19. 1 like
    This is intended.Applied Power output is available only for Steady State Heat Transfer Analysis in H3D and PUNCH files only.Read OLOAD comment 9. OLOAD.pdf
  20. 1 like
    Above guide just create plotel elements, switch them to bar2 by panel 3d>config edit
  21. 1 like
    Hi John1989 The reference direction for the ports are different. This causes the 180 degree phase shift. You can change it for the MoM port as shown. For the FEM port, it cannot be set, and is assigned automatically internally.
  22. 1 like
    Why don't tell about it first? It is a basic tk proc: tk_dialog .dialog Hypermesh "Select criteria:" "" 0 5mm 6mm 10mm Cancel
  23. 1 like
    @Salaya it is likely the dsearch parameter is too small so some slave nodes do not find their master surfaces. If 0 is entered, the search distance by default is computed from the average size of the master segment. The following videos might help: 7.2_Type2 _Tied Interface - Altair Learn HyperMesh RADIOSS Interface 2 Connections Spot Bolt RBODY Tied - Altair University Please go through free ebook Introduction to Explicit Analysis using RADIOSS – A Study Guide - the chapter on tied contact is attached. tied.pdf
  24. 1 like
    When you have set name, you can get set ID by following command: set set_id [hm_getvalue sets name="E_1" dataname=id] When you have set ID, you can get set name by following command: set set_name [hm_getvalue sets id=2 dataname=name]
  25. 1 like
    Hi, the property assigned is incompatible with the element type.
  26. 1 like
    I think you'll create an isosurface of something like 'levelset', then use a value of 0.5. It will be something along those lines.
  27. 1 like
    You can use non-linear quasi-static (NLSTAT) analysis. However, I would recommend to first perform lattice optimization using linear static analysis with small loading % and only after you are confident enough in the results (they make sense) try the non-linear solution and larger enforced displacements.
  28. 1 like
    @aymanalsukhon no problem, that's what forums are for, eh? I used Hypercrash>quality>check all solver contact interfaces to automatically clear all penetrations (because Hypermesh does not find all). Turns out my contact definitions were off, so it's better to go with the default. You can leave the Gapmin blank and the solver will automatically set the appropriate value. Check the attached solver deck. Output requests for contact forces and pressures (ANIM/VECT/CONT & PCONT) are defined- I reckon you'll need them at some point. Trial_edit2_0000.rad
  29. 1 like
  30. 1 like
    If you does not show your script code, nobody could help.
  31. 1 like
    I believe you have some modelling inconsistency in your model. Upper arm thickness coincide with parte cima. Define contact between puxator and upper arm or honeycomb.Try all with freeze contact. Not sure about the graph.Is that Displacement vs Force graph? In above shared screenshot force magnitude is 3000 however in shared file it is 2500. Can you also share .out file of the run?
  32. 1 like
    Dear @Ivan I really appreciate your help thank you.
  33. 1 like
    For isotropic materials FEKO has an already implemented radiation boundary condition on the surface of the FEM region. Surface elements on the FEM boundary are used to couple with the Method of Moments in a hybrid FEM/MoM solution. Or in a FEM only solution, an absorbing boundary condition is used. While it is theoretically possible to implement a radiation boundary condition for anisotropic FEM dielectrics, it is just not implemented in FEKO yet.
  34. 1 like
    Solved the problem. Changed my curve to 3D cartesian and made it open. For the reaction force output I've made an expression: `FM(I,J)` where I is the PTCV´s marker I and J is the marker on T-arm placed at point_Pin.
  35. 1 like
    Hi all, New year wishes to forum members Can anyone tell how static simulation can be done for 2 wheeler wheels
  36. 1 like
    Hi @RF Engineer If you would like us to check your model setup please attach it to this post.
  37. 1 like
    Thank You for your reply Mr. Tinh but still getting error "can't read "w.lugType01": no such variable" when i run the following tcl file in hypermesh #*********************************************************************************** proc ::Execlug01LUG {args} { set w .lugType01 destroy $w toplevel $w wm transient $w . frame $w.f2 #--------------------------------------- label $w.f2.labL1 -text "L1 =" entry $w.f2.entL1 pack $w.f2.labL1 -side left -anchor w pack $w.f2.entL1 -padx 15 -pady 2 -side left label $w.f2.labL2 -text "L2 =" entry $w.f2.entL2 pack $w.f2.labL2 -side left -anchor w pack $w.f2.entL2 -padx 15 -pady 2 -side left pack $w.f2 -side top -anchor nw -fill x #--------------------------------------- button $w.b -text Model -font {Helvetica -25 bold} -height 1 -width 10 -background gray75 -foreground blue -command {hm_setpanelproc ::modelclick} pack $w.b -side top -anchor nw -fill x } proc ::modelclick {args} { set w.lugType01 set l1 [$w.f2.entL1 get] set l2 [$w.f2.entL2 get] *createnode 0 0 0 0 0 0; *createnode l2 0 0 0 0 0; *createnode l2 l1 0 0 0 0; *createnode 0 l1 0 0 0 0; } #***********************************************************************************
  38. 1 like
  39. 1 like
    Hi Use panel Tools>scale to scale all comps up to 1000x But remember that you don't need it, just understand result values
  40. 1 like
    Hi It is array get ::AbaqusCW::cwNonSurArray
  41. 1 like
    Ok, I see In case you want to position widgets in both row & column, use grid command if using pack, you need to pack label and entry in a sub frame, then pack subframes top side down Or you can use place command - the most freely-positioning command
  42. 1 like
    the following items were edited: -orthotropy direction was defined in global X direction -fully integrated elements were defined on properties -contact were modified to reduce initial penetrations IA_5.0_edit2.hm
  43. 1 like
    Student Editionには使用制限があり、HyperMeshの中からソルバーを実行していただく必要がございます。 多くの機能はHyprMesh内で設定可能であり、未対応のものもUnsupportedCardsに記述して頂くことで幾分カバーできると考えられます。
  44. 1 like
    Most of casting software use STL import (3D scan data). But you can use Inspire Cast to import step/parasolid/... files with good geometry quality. Another method I overcome this issue for complex geometry (scan data) by using Simlab or HM to create good mesh >> export to STL >> Click2Cast.
  45. 1 like
    I am also working on a script where I need this functionality. I found a script that can be used as a starting point: https://connect.altair.com/CP/kb-view.html?kb=40826 The first procedure is the one that creates the GUI with the selection panel. You can change the selection type from Nodes to Elements by modifying lines 39 and 40.
  46. 1 like
    Thanks Tinh for your advice. I cannot open 2nd session even wait for hours. Actually, I already called Altair Support and found this issue only happen in user account (not full writing permission). Admin account is fine. This bug was fixed in v2017.2.2. We can close this topic.
  47. 1 like
    Please refer attached zip file for CDSMETH. CDS_SUPERELEMENT.zip
  48. 1 like
    Hi Pablo I Check this video and forum post too, that may help you clearing the free edges and equivalence nodes.
  49. 1 like
    Hi, review and debug models using tools>Modelchecker>Radiossblock and starter out file. select user profile 2017, because for an unknown reason 2018 is not supported. There are problems with contacts- type 7 and 2 require initial gap so some parts ware offset, and some other parameters were defined. I suggest connecting parts of crash-box assembly with mesh connectivity (matching) instead of using type 2 or 7 contacts. There were also issues with composite orientation. here is the manual option: and here is Drape Estimator: Drape Estimator - Altair University You should also reduce the model, as my computer would run this simulation for the next 2 months nonstop- imagine the desperation IA_3.0-edit.hm
  50. 1 like
    Sorry for the late reply. Just saw this open question. The MetaCurve will eventually be completely replaced by the Blend Curve as we add more and more features and options to it. As a result you will be able to achieve what you are looking for. And just some additional information regarding Class A surfacing. There is generally a lot of confusion about what what it is, what it means, and how to achieve it. There are "A" surfaces and "B" surfaces. "A" surfaces just means the visible/aesthetic side of the model, and "B" surfaces are the side of the model you can't see. Take a computer mouse for example: The exterior surfaces that you can see and touch are all "A" side surfaces, whereas the inside faces of those pieces are all "B" side surfaces. The confusion comes in when you start trying to define mathematically what Class A means. For every company and product the definition can be different. For some the definition can be as simple as tangential (G1) continuity as their minimum requirement, where others may require a minimum of curvature continuous (G2), or curvature continuous (G3). These are all technically Class A surfaces, but due to the automotive influence in the design culture most people associate Class A with G2 continuity or higher. But you also have to keep in mind that the higher the level of continuity the higher the chances are to introduce "wavy" surfaces because the modeler has to manage more and more points and their relationships to each other. So just because a surface is mathematically G3 doesn't necessarily mean it is the desired shape. There are a lot of things that I could get into on this, but I will leave it here for now. So can Evolve be used for Class A surfacing? Absolutely. We have customers all over the world doing this on a whole range of products. Our tools such as Loft, Sweep, Patch, Round, etc...all have options for G2 continuity. The only exception for Class A surfacing with Evolve would be automotive exterior stamped sheet-metal, which is a very special case where additional tools and control are needed and the Class A definition requirements are much higher. Hope that helps.
×
×
  • Create New...