Jump to content


Popular Content

Showing most liked content since 01/23/19 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. 1 like
    ベーシックチュートリアルをアップデートしました。 "01_Flux_Training.pdf"というファイル名で配布しております。 お持ちでない方、ご興味がある方は 弊社サポートまたは、担当営業までお問い合わせください。 ご活用いただけると幸いです。 アップデート内容は下記のとおりです。 ・スライドのアスペクト比を標準(4:3)からワイド(16:9)に変更 ・エンティティの選択方法について、例題を交えて説明 ・メッシュの設定方法についての説明を追加 ・Fluxでのデータ構成についての説明を追加 ・生成されるファイルについての説明を追加 ・3D Basic exampleの例題を変更 00_Flux_Training.pdfでは電磁接触器 ↓ 01_Flux_Training.pdfではアクチュエータ Flux内で形状作成する場合と、CADデータとしてインポートする場合の両方を準備しております。 CADインポートで実施する場合はチュートリアルに対応している "all_part.SAT"というファイルもご提供いたします。 ・2Dの例題として、"Brushless IPM motor tutorial"を追加 モータテンプレートによる形状作成で、 コギングトルク、逆起電力、定格速度時、始動時、モータインダクタンス を求めるチュートリアルになっています。
  12. 1 like
    Hi pmcardle The incident field is indeed excluded in the far field.
  13. 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é
  14. 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.
  15. 1 like
    Glad to help. You can verify the element orientation by performing analysis on a simplified model (single element) with highly anisotropic material parameters.
  16. 1 like
    こんにちは、@sentan 右下のCFD cornersをsquared cornersに切り替えてみて下さい。
  17. 1 like
    Hello, Massive thanks for your reply... As you undoubtly already noticed am i not such an experienced user in hyperworks. Your response is very clear and exactly what i needed Thanks a lot Ivan!!
  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
  20. 1 like
    Hi JIAYU SUN This is because the GeForce series of Nvidia is not officially recommended by HyperWorks. However, this warninig message only appear once. You can proceed further and you may experience some graphical issues in the future. HyperWorks_2017_Hardware_Recommendations_and_Certifications.pdf
  21. 1 like
    Hi Please attach the .0000.out file and correct input file ,The attached model doesn't have SPH elements there are few free edges in the model do correct it Regarding error 668 and 53 go through these post
  22. 1 like
    Can you find it in STEP file? if no name is in step file, obviously you have to check your cad software first.
  23. 1 like
    maybe, you copy & paste my code. Be not lazy, pls type it again, man!
  24. 1 like
  25. 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.
  26. 1 like
    Hello Manoj Raghav G V, As i understood this error occurs due to invalid property or worst mesh type. Plz share the file that we can solve the issue.
  27. 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
  28. 1 like
    Normal panels like F5 do not make 'function_lock' mode, so you can push other panels over.
  29. 1 like
    Brahmadev, Compose is a multilanguague (OML, Python and TCL) environment for doing Math calculations, data manipulating and visualizing. This includes CAE output files (.h3d, .op2, .odb...) or test results (.ascii, .uff, .unv....). With Compose you can program using the languages that I just mentined and debug your scripts. There are bridges between these languages too (OML-Python and OML-TCL) that gives you much flexibility to work with the best of each language. Since Compose works with TCL as well, you can write your scripts for HyperMesh with it, or even more: you may leverage the multilanguage possibilities of Compose. An example: let's say you have a CAE result file and would like to pass information from it to HyperMesh, in order to create load collectors cards, for example. You can use OML (Compose's primary language) to get the CAE result data and then pass these variables to the TCL environment using functions such as exporttotcl. Then you call your TCL script with evaltclscript and use the variables that have just been passed. Regards, Roberta
  30. 1 like
    Hi Sanket, try, foreach node $lst_nodes { dict set mydict $node [join [hm_nodevalue $node]] }
  31. 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
  32. 1 like
    @Rahul R I also tried without AUTOSPC, but got the same results. @Q.Nguyen-Dai Is it like inertia relief analysis?
  33. 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
  34. 1 like
    If you does not show your script code, nobody could help.
  35. 1 like
    Can you check control card : Sensitivity or Output : ASCSENS
  36. 1 like
    The latest version is Inspire 2019.0.1 and we improved graphics a lot. Usage of VMWare can also be an issue for graphics bugs during picking. Unfortunately this is not supported on MAC and will require that you switch to a Windows machine.
  37. 1 like
  38. 1 like
    There are no CBAR elements in the shared solver deck. Please review the *_lattice.out and *_optimized.out files for anything unusual. Unfortunately, I do not have experience with lattice optimization to be able to offer better suggestions.
  39. 1 like
    Hi Bidisha From your description I assume that you would like to extract the multi-port Z-parameters. (Note that the "MoM Matrix" solved during the Method of Moments solution in Feko is also known as the "Impedance matrix" as the elements of this matrix have the the same units and impedance.) To extract the Z-parameters you should request S-parameters in CADFEKO and then, after the simulation has completed, in POSTFEKO use the Export -> Touchstone option. Under the Touchstone export dialog there is an option to select the "Network parameter type" for the export. There you should select "Z (impedance parameters)" to then export the data to a Touchstone file. Kind regards, Johan H
  40. 1 like
    That message "There are zero region sets in the model" typically means there are no 'solid' bodies represented in the parasolid file. If the parasolid file definitely has 'solids' represented (which could also be the fluid volume, but from a solid modeler), there could be an issue with the CAD. If the file only has surfaces, you'll need to enable the 'Fill Voids' option on the import geometry panel. This will then create the volumes which are enclosed by surfaces, during the import process.
  41. 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.
  42. 1 like
    @Begoña attached is the model with composites. Try to setup you model in similar fashion. P17 stack property can be used instead of P51. Use the XREF entity (right click entity in browser) to check how different entities (plies, laminates, materials and properties) are referenced and related to each other. If the plies are too thin to properly visualize, go to Preferences>Graphics>ply visualization thickness factor. CARBON LAMINATES- Tensile.hm
  43. 1 like
    Use hm_count foreach {ename econf} {quad 104 penta 206 hexa 208} { puts "#$ename = [hm_count elems all $econf 0]" }
  44. 1 like
    グラフィックスエリアの右上に表示されているModel Infoを非表示にしたい場合は、 モデルブラウザ⇒「Titles」⇒「Model Info」⇒右クリック⇒「Hide」をクリックすると非表示になります。
  45. 1 like
    Maybe the contact was not detected because shell thickness is smaller than the gap between solid and shell midsurface. Measure the gap (F4) and use Vicinity tolerance instead and provide a slightly increased gap. If other unwanted contact pairs are then detected consider creating the problematic contacts manually.
  46. 1 like
    Hi, I definitely agree with qchen regarding the doc :-) I have a similar question: I'm trying to import one of my scripts (imprtScrpt.py) in another script (mainScrpt.py). The imported script only contains functions. The only solution that I've found until now is to call "executeBatchSpy('imprtScrpt.py')" in mainScrpt. When I simply try "import imprtScrpt", mainScrpt exits without any message. Am I doing something wrong? Thank you very much in advance for your help! PS: until now, I've been ok with importing by using executeBatchSpy, but my script is starting to get quite big and I'd like to use imports to use profiling tools (such as doxy).
  47. 1 like
    Glad to hear it is working. It's not working when the master/slave are swapped because nodes lying on the master surface can freely penetrate on slave surface. Interfaces are based on master / slave treatment. Contact can only occur between a set of slave nodes and a set of master segments. Master segments are defined depending on the type of element they lie on. If it is a 3-node or a 4-node shell, the segment is the surface of the element. If it is a solid element, the segment is defined as a face, Finally, if it is a 2D solid element (quad), the segment is a side. Check the following documents: https://insider.altairhyperworks.com/wp-content/uploads/2015/07/T-T-1119-OptiStruct-Defining-master-and-slave-roles-for-contact-surfaces-in-a-contact-pair.pdf http://blog.altair.co.kr/wp-content/uploads/2013/03/CONTACT_Card.pdf
  48. 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; } #***********************************************************************************
  49. 1 like
    Hi It is array get ::AbaqusCW::cwNonSurArray
  50. 1 like
    I have found a way. When comparing two different results of a FEM model is needed to be done on a single window on Hyperview, Hyperview. ==> Split as many windows as needed ==> import models and results to each window respectively. Mouse Rightclick while the cursor is somewhere on the window ==> active model ==> Cut/Copy/Paste. Copy the results and make sure you paste them all in one window. Before doing so, renaming the title would be wise to differentiate. From the feature tree, right click the file name ==>make current ==> maybe change colors of components to one for comparison. Hide the compo which you dont want to be shown, etc.. repeat the same for other models. I have the desired components from different result files visible in one window. It makes things a lot easier for results comparison and validation. Thank you.
  • Create New...