Jump to content

ydigit

Moderators
  • Content Count

    429
  • Joined

  • Last visited

  • Days Won

    16

ydigit last won the day on April 15

ydigit had the most liked content!

2 Followers

About ydigit

  • Rank
    Super User

Profile Information

  • Gender
    Not Telling
  • Are you University user?
    No

Recent Profile Visitors

3157 profile views
  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. https://altairhyperworks.com/training/new_feature_videos/14/content/cfd.htm Check the second video on solver setup.
  9. https://altairhyperworks.com/training/new_feature_videos/14/content/cfd.htm Check the second video on solver setup.
  10. Also you can define the air with properties mentioned above as a type=solid instead of fluid. This will ignore convection in the medium.
  11. acuGetRsp command should be helpful to get the response. Check all three tutorials in the Optimization part of the tutorial manual.
  12. 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:
  13. In your third screenshot, Surface outputs for fluid_walls are disabled. That also needs to be enabled.
  14. 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.
  15. You can also try Fields for mapping purposes. It is available in AcuSolve Profile, under the Job Launcher. See screenshot.
×
×
  • Create New...