Jump to content

acupro

Members
  • Content Count

    192
  • Joined

  • Last visited

  • Days Won

    8

acupro last won the day on July 26

acupro had the most liked content!

3 Followers

About acupro

  • Rank
    Expert User

Profile Information

  • Country
    United States
  • Are you University user?
    No

Recent Profile Visitors

1770 profile views
  1. You can download the latest release versions from connect.altair.com - which will then include the documentation, tutorials, etc. You can request a login there if you don't already have one.
  2. When the user function is compiled, it includes the libraries necessary for the type of message passing to be used by the solver itself. If you issue acuMakeDll -h you'll see the option '-mp' with the default being impi. So if you're going to use impi at the solver level, the compiled library will be correct. However, in the cases you show above, the message passing used by the solver is openmp, thus the user library needs to be recompiled. The second system doesn't have the 64-bit compiler, so it fails. If you want to compile for openmp to be used on the second system you would add -mp openmp to the acuMakeDll command you used for the first attempt. Then the compiled dll should be usable by the solver on both systems, without recompiling.
  3. I would recommend leaving Simple BC type = outflow, but then add the surface integrated condition to specify the mass flux. In AcuConsole, that would be under Advanced Options > Integrated Boundary Conditions (with BC* or ALL selected in the tree filter). For exiting flow, the mass flux value will be positive. Achieving the values will also depend on the mesh density and the level of convergence.
  4. If I read this correctly, you have three fluids you wish to mix, one of which is air. Is that correct? You'll likely be better off going through your local Altair / HyperWorks support channel so they can bring in the appropriate resources to determine if AcuSolve is appropriate for your desired simulation.
  5. According to the last line in your post, libusr.dll was successfully created - that is the linked/compiled library to be used by AcuSolve. What files are in that ACU5300 directory after you run acuMakeDll? Does the solver go through using the libusr.dll file that was created?
  6. I would assume it's the case, as it seems you should have access to AcuSolve. Can you start AcuConsole? I also noticed the student edition has a limit of 500,000 nodes in the AcuSolve mesh. https://altairuniversity.com/altair-student-edition-limitations/
  7. If you can start AcuConsole - go to Help > AcuSolve Help.
  8. You will need to extrude the surface mesh to one volume element thick to run in AcuSolve. There are a few tutorials in the AcuSolve Help system covering flow over airfoils, using various turbulence model approaches, with and without transition models.
  9. The pressure is an 'Element Boundary Condition', so there will be some variation in the result, depending on the mesh resolution and the level of convergence. (Nodal boundary condition would be a fixed value at the nodes, but it is not recommended.) You could also try with surface integrated condition at one of the outlets, and leave the other with outflow/pressure condition.
  10. Please review the 'AcuTherm' section in the AcuSolve Help System - under AcuSolve Programs Reference Manual > Post-Processing Programs > AcuTherm. The surface_film_coefficient is essentially Method 3 on that page, using the default of Y+ = 100. This is dependent only on the turbulent flow solution.
  11. 'pressure' is static pressure (P), where 'stagnation pressure' is total pressure (P + 1/2*Rho*V^2). The most stable for inflow is stagnation pressure, pressure is fine for outflow. But pressure at inflow also works for most cases.
  12. If you add ELEMENT_OUTPUT to the element set in question, one of the integrated element output quantities will be mass-averaged-momentum. That would be the first thing to try.
  13. I would probably first try mass-flux (or velocity, flow rate) at inlet, and Outflow Simple BC with the known pressure values for the two outlets. That leaves the pressure unknown at the inlet.
  14. 1. The BC definition in the input file is likely correct - use a positive value for entering flow with Simple BC type = inflow and inflow_type = mass_flux. The Surface Integrated Output (what you would see on that surface in AcuProbe) will be negative due to how the postprocessing is calculating the value using the surface normal. 2. You 'can' add a mass-flux type condition along with the outflow Simple BC, but it's not exactly physical, as it will also attempt to create a certain profile for the flow. You would add an Integrated Boundary Condition of type = mass flux, and use your desired value. (In AcuConsole, use BC* to expand to Advanced Options to then see Integrated Boundary Condition. This would be SURFACE_INTEGRATED_CONDITION in the input file itself.) In this type of boundary condition, you would use a positive value for flow leaving the domain and a negative value for flow entering the domain - again, due to the use of the surface normal in the definition. 3. Again, possible. It is better to use 'Stagnation Pressure' (or total pressure) at the inlet and 'Pressure' at the outlet. These would also be under Advanced Options - then Element Boundary Condition. But pressure for both will also normally work. The 'Outflow' type of Simple BC is just a pressure boundary condition.
  15. The definition for the integrated mass flux (flow rate) includes the surface normal direction. At the inlet, the surface normal is pointing outwards, while the velocity is going inwards - thus the negative value. At the outlet, both the surface normal and velocity are pointing outwards - thus the positive value. You can review the definitions in the Programs Reference Manual > Post Processing Programs > AcuTrans section (towards the end of that section in the 2019.0 Help).
×
×
  • Create New...