Jump to content

acupro

Members
  • Content Count

    177
  • Joined

  • Last visited

  • Days Won

    6

acupro last won the day on June 14

acupro had the most liked content!

2 Followers

About acupro

  • Rank
    Expert User

Profile Information

  • Country
    United States
  • Are you University user?
    No

Recent Profile Visitors

1665 profile views
  1. You'll achieve better accuracy with lower Y+ values - at the cost of more mesh and longer simulation runtime. For example, you'll typically get a more accurate solution with Y+ = 20 than you would with Y+ = 100. However, maybe the level of accuracy at Y+ = 100 is enough for your purposes. That's where it becomes 'engineering' instead of just running a simulation. You can run a mesh sensitivity study to see how the solution of interest changes as you modify the meshing parameters.
  2. The issues I am seeing are in the locations where the tubes 'kink' and the surface edges meet together with essentially zero angle and zero space between the surface edges. With the current geometry, you'll probably need to create the mesh in HyperMesh, and toggle those edges so they're not meshed explicitly. Otherwise, if you can modify the geometry such that those surface edges don't come together like that, then AcuConsole may work better. If you right-click 'Model' and select 'Query', add a row under the 'Point' tab and input the coordinates. You may need to increase the point size and toggle visibility of things to determine where the point is - but this can help you locate problem areas. You can also view surfaces/volumes in Solid & Outline mode so you can see where the surface edges are.
  3. What is the source of the CAD - original software used to create the geometry, and the format exported from the CAD software and imported to AcuConsole? The initial warning mentions 'zero length edge'. Please share the CAD model if you are able - native geometry model plus the model imported to AcuConsole - and maybe even the AcuConsole database (.acs file) to check mesh settings.
  4. They both represent rotation. The reference frame is for steady-state, and the mesh rotation is for transient. While in some cases the steady-state assumption with reference frame is very good, typically the accuracy with mesh motion will be better. Of course, the transient simulation takes much more run-time, so that is the trade-off - increased accuracy at the cost of longer runtime.
  5. You'll probably need to contact your local Altair support office to see if they can help you.
  6. Essentially yes. The pressure used at the solver level is the pressure stated as a BC, plus whatever value is stated as the absolute pressure offset. (The absolute temperature offset operates the same way.)
  7. Use Coordinate Surface (GUI icon labelled 'Coord'). This will give you an X, Y, or Z plane.
  8. Are you going to run with density as a function of both temperature and pressure (Ideal Gas), or only of temperature (Boussinesq)? If only of temperature, then you don't need to be concerned about the absolute pressure at all. Simply use/define the material property values at the desired pressure of 10kPa. If properties are also a function of absolute pressure, then you need to use absolute pressure in your BCs. Personally I always leave absolute pressure offset at 0, and if absolute pressure is necessary, use absolute values for BCs, etc. Absolute pressure offset essentially means all other pressure values are relative to that stated offset value.
  9. Looks like you should be good to go, since the dll was created.
  10. You need to go into the directory where the C code user-function is on your machine. The compiler itself as you've shown in the Window above will not be aware of the libraries in the AcuSolve installation. But when you are in the AcuSolve Command Prompt, the appropriate paths are set (PATH, LD_LIBRARY_PATH, etc), and the necessary libraries are available to acuMakeDll.
  11. acupro

    ACUSOLVE UDF

    If you're issuing the acuMakeDll command from the AcuSolve Command Prompt, the libraries should all be readily available. Please describe the process you used, and share any images of the window showing the errors and your process.
  12. It looks like there are two surfaces in the AcuConsole version (acusolve.inp) with both Simple BC (type = wall) and Surface Output commands, where in the HyperMesh version (launcher.inp), those two surfaces only have Surface Output. It's easy to miss the fact that by default, the model after importing the mesh/.arm to AcuConsole will likely have Simple BC active. inter_CFD_bl001_CFD_tetcore001 and inter_CFD_tetcore001_CFD_bl001
  13. Please refer to the AcuSolve Help section - by default located here on Windows: file:///C:/Program%20Files/Altair/2018/acusolve/win64/help/acu/AcuSolveTOC.htm?acusolve_welcome_page.htm There's a 'What's New' section on that top-level page.
  14. There could be some 'path dependence' on the results, but I would also not expect such a large difference in the result, about 15%. Do you also get similar results differences if you reduce the convergence tolerance from 0.001 (assuming you're using the default) to 0.0001? Are you able/willing to share the model files (.inp, MESH.DIR) here? If not, you should contact the local Altair Greece support team.
  15. acupro

    ACUSOLVE UDF

    Already in other thread...
×
×
  • Create New...