Jump to content

ydigit

Moderators
  • Content Count

    432
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by ydigit

  1. I am unsure if VWT -AcuSolve has the option to change the turbulence model in the interface. You could import the .ACS file in AcuConsole and change the turbulence model there. Export .INP again. Now you could start AcuSolve manually from Command Line or using AcuConsole. Post processing, you will have to deal with manually.
  2. 1. For PFSI you need input in OP2 format (from OptiStruct) with fixed nodes at one end. 2. Not an optiStruct Expert, but you should be able to specify in OP2 output that you want only modes for one component in that file.
  3. Could you please send a screenshot of the directory where this case is running? Do you see MESH.DIR or ACUSIM.DIR?
  4. Last few lines give a hint about the issue. Seems that AcuSolve exited abruptly. In this case probably rerunning the case is the easiest option. There are ways to recover data as well, however unsure if that would be worth, as each iteration is only ~34s.
  5. Yes it would be possible to particle tracing using AcuTrace for you application. You might want to contact your local Altair Support in case AcuTrace setup gets tricky.
  6. However, I did not define as air as a material or "solid". Are these conditions still adequate to simulate the heat exchange (conduction) with an ambient medium or do I have to model air especially? It is adequate to simulate without external air, if you use the BCs above. And should I have to model a cuboid with air as static fluid, does the program automatically recognize that where there is a solid, there can't be fluid, or do I have to define that specifically? You have to define explicitly mediums for all volumes.
  7. Short answers for now, as I cannot open the HM right now. 1. Yes you can use AcuSolve without fluid. You can define Material_Type= solid for Air. This will essentially create a "solid" with properties of air, however only conduction will take place. 2. Contact definition between two surface is default Flux = 0. This means that there is prefect contact between two surfaces and conduction will take place without any thermal resistant (like air gaps or glue). If you need to define free convection, then all AcuSolve preProcessors have options to define those as well.
  8. Please post a screenshot of your run folder for this simulation, so that we can see if ACUSIM.DIR, MESH.DIR folders were generated or not. Also there should be two .Log files. Please post them here, so that I can see what is going on.
  9. The last release of VWT for AcuSolve was with 2018. You download that from connect.altair.com I am not aware of any method to use VWT 2020 for AcuSolve.
  10. Correctly mentioned above, that both will very likely give the "same" results. Also, AcuSolve is a node based solver. Hence the way these nodes are connected is secondary for the solver, important is to have enough nodes in the region of interest. I am not aware of any setting in AcuConsole to get the "nice" looking mesh.
  11. https://altairhyperworks.com/training/new_feature_videos/14/content/cfd.htm Check the second video on solver setup.
  12. https://altairhyperworks.com/training/new_feature_videos/14/content/cfd.htm Check the second video on solver setup.
  13. Also you can define the air with properties mentioned above as a type=solid instead of fluid. This will ignore convection in the medium.
  14. acuGetRsp command should be helpful to get the response. Check all three tutorials in the Optimization part of the tutorial manual.
  15. Thermal Shells in AcuSolve can help. Which preprocessor are you using? AcuConsole, HyperMesh, HyperWorks CFDx and SimLab all support thermal shells for the purpose you need. HyperWorks CFD: Thin domain AcuConsole : HyperMesh:
  16. In your third screenshot, Surface outputs for fluid_walls are disabled. That also needs to be enabled.
  17. I am unsure about your request. If you would like to split the same VWT window instance into two and to the comparison, thats not supported. What you could do it open the .Log file in AcuFieldView or HyperView. Both support multiple windows/dataset for comparison.
  18. You can also try Fields for mapping purposes. It is available in AcuSolve Profile, under the Job Launcher. See screenshot.
  19. Also HV has similar Reader Options to read extended nodal outputs:
  20. For AcuFieldView you can enable the Read Extended Variables to see heat flux, etc as a variable for plotting.
  21. Enclosure radiation model is calculating the View factors between all surfaces. So this is a Surface-Surface radiation model in that sense. See P111 of Command Reference Manual for more details on view factor calculation. e.g. Location in your installation: D:/HW20191.1/hwcfdsolvers/acusolve/win64/doc/Altair_AcuSolve_2019.1_Command_Reference_Manual.pdf
  22. @Rahul Ponginan Might be in a better position to answer about licensing and VWT availability in Student Edition.
  23. If not VWT, then HypeWorks CFD X 2019.1 is probably the next "easiest" option. The only thing is you will have to do repairs mostly on the geometry (CAD), Detailed Mesh editing operations like in HyperMesh are not there. If not that, you can also setup the complete wind tunnel analysis in HyperMesh or SimLab or AcuConsole. In the end all will write out input for AcuSolve. Any reasons you want to avoid VWT workflow?
  24. If the geometry is causing so many issues, it might be worth to have a look at SimLab. It is pretty efficient at removing such intersection and overlapping elements. You can export the current mesh as .NAS or SimLab can also open HM files directly. Looks for options under „assembly“ in SimLab.
  25. There is one more check that I generally perform before exporting from HM, that is a small angles check. I start by repairing all elements with <2° initially. Once those are repaired <5° check/repair may or maynot be needed depending upon geometry. This also helps to remove really small edges <1mm, as they are generally not needed. Also one more aspect is the level of tyre cut that you introduce, while positioning the vehicle in VWT. Sometimes increasing the chopped of portion of tyres, helps to avoid sharp angles at the intersection of tyres and the road.
×
×
  • Create New...