Jump to content

acupro

Members
  • Content Count

    238
  • Joined

  • Last visited

  • Days Won

    13

Everything posted by acupro

  1. Have you been using multiple screens (a second/extended monitor) recently, but now only a single monitor? Perhaps the GUI is opening on that 'second' monitor. https://www.howtogeek.com/howto/windows/bring-misplaced-off-screen-windows-back-to-your-desktop-keyboard-trick/ If that is not the issue, try opening the AcuSolve Command Prompt, and try this: acuConsole -ets to see if any useful error/warning messages are given.
  2. I don't believe it matters too much what you use for the origin, so long as every boundary where you activate it you use the same origin. Your choice is to put it on that outflow surface is reasonable. Assuming up/down in the image is also the gravity direction, you probably do not need to activate hydrostatic on the outlet surface. It only has effect on a boundary that has any component parallel to the gravity direction. If you used a pressure or stagnation pressure type at the Inflow as pictured, you would need to use hydrostatic pressure there. It basically makes the pressure value at the boundary consistent with the gravity body force. The outlet at the top really wouldn't see any pressure gradient due to gravity as that surface is normal to the applied gravity.
  3. From what I've been able to gather, in the released version 2019.1, radiation through glass will work only if there is no surrounding fluid medium, using either the P1 or DO radiation model, with the DO being more expensive but more accurate. If there is a fluid medium, then only the DO model will work, but will require waiting for the 2020 released version. You'll probably want to work with your local Altair Support team on this.
  4. This would be a two-phase simulation to get correct. You can look through the tutorials through the Help system included in the installation. Best bet is to work with your India Altair support team.
  5. You'll probably need to cut out the portion of the surface, so it's a separate surface. It will have some non-zero area, so not really a point source.
  6. acupro

    Shear Flow

    1. For the inlet NBC, you may want to use cubic-spline rather than linear. It depends on if you want linear or cubic interpolation between your given data points. 2. For the NIC, you have two choices, since piecewise linear is not available in AcuConsole. You can either use a tool like Excel to determine the equation for the velocity based on Z - and use 'Script' in AcuConsole. Or you'll need to edit the input file once written, and use piecewise-linear (or cubic spline), as described in the Command Reference Manual under Nodal Data Commands > Nodal Initial Condition, which will then be similar to the NBC.
  7. If you want the four sides to be inlets, you need to have four separate inlets, rather than putting them all into one set.
  8. acupro

    Shear Flow

    Let's assume the flow direction is X (right to left in your picture) and the vertical direction is Z (bottom to top in your picture). In Nodal Boundary Condition, variable is x-velocity, type is piecewise-linear. Curve-fit-variable is z-coordinate - then enter the values (table) for x-velocity as a function of z-coordinate. Should be similar for Nodal Initial Condition. This will give the same profile everywhere - no difference for the side and top walls.
  9. The species equation is using mass fraction, not volume fraction. The surface integrated value at that point in time gives information about that location - 95% coming from Inlet2 (where Species1 = 1). It doesn't say anything about where else the flow from Inlet2 might be going. This also brings up the question of initial conditions. To what value of Species1 did you initialize the domain? You may want to track two species instead of one. You could initialize Species1 and Species2 to zero in the entire domain, then have Inlet1 with Species1 = 1 and Species2 = 0, and Inlet2 with Species1 = 0 and Species2 = 1. This could help to clarify if any regions in the flow still have results from the initial condition. There could also be some diffusion, so you may want to include diffusivity models, with a diffusivity value of 0, for the species, in attempt to minimize diffusion. You may also want to work with your local Altair support team.
  10. You may try using the Species equation, with the values different for the two inlets - for example Species1 = 0 at Inlet 1 and Species1 = 1 at Inlet 2. Then you can look at species values on the surface and correlate that with the mass flux percentage for the species. I would suggest something with that approach - basically using Species as an 'inert' scalar.
  11. This ran through with both set to 400 steps as you last sent - using the latest (or close to) official releases of both codes - OptiStruct 2019.2 and AcuSolve 2019.1. The only thing I can suppose is that the older version 2017.2 you're using (likely on the OS side) had a bug in the stopping mechanism that has since been fixed. I've attached the OS .out file, along with the OS .h3d file. Are you able to update your installations to the latest release(s)? ailette-with-f.h3d ailette-with-f.out
  12. In AcuSolve, you've specified max_time_steps = 401, and final_time = 1E+1 (10.), with a time increment of 0.025. The AcuSolve job will stop at the specified final time of 10.0, or after 401 time steps - whichever comes first. Since 400 * 0.025 = 10.0, AcuSolve will stop after 400 time steps, rather than 401. It looks like you've specified the OptiStruct job to do 401 time steps with a time increment of 0.025. AcuSolve stops after 400 time steps, so the OptiStruct job errors out once the connection signal is lost. Try setting OptiStruct to do only 400 time steps, so it matches the stop time of AcuSolve.
  13. The OptiStruct .out file suggests to look at the .stat file. Does that give any ideas? Can you also upload the AcuSolve .Log file and the OptiStruct .fem file?
  14. That generally means the surfaces on the AcuSolve side and the OptiStruct side are not co-located. Make sure both models have the DC-FSI surfaces in the same location and are the same size/scale and shape. Just above the assertion you have in the Log file: Ave distance = 9.367829e-004; Max distance = 2.350710e-002. This means the maximum distance between the OptiStruct and AcuSolve surfaces is 2.350710e-02, larger than the Max allowed gap of 5.486660e-003. Check to ensure the surfaces are the same size, shape, and location in both models.
  15. In your AcuSolve input file (slab_dcfsi.inp) you have in Auto Solution Strategy: max_time_steps = 101. With a time increment of 0.01 sec, the final time is 1.01 sec. The tutorial instructions indicate to set final time to 3.0 - which matches with the final time in the OptiStruct .fem file. Thus in your case, AcuSolve is going to stop at 1.01 sec, while OptiStruct expects to go to 3.0 sec. AcuSolve stops, and causes OptiStruct to stop (error out). If you set max time steps set to 0 and set final time to 3.0 on the AcuSolve side, as in Section 1.3 of the tutorial instructions, you should be good to go.
  16. I'm not very good on the OptiStruct side, but apparently the OptiStruct side has finished and closed the connection to AcuSolve. I now see you've made changes to the tutorial model - or whichever model you're running. But whatever you've done on the OptiStruct side does not appear to be consistent with what you've done on the AcuSolve side.
  17. You probably need to remove the space after the commas - and maybe add a space after the = (but that is likely not necessary). Yes, you'll need to use a different value for each component. You can add all three, then just comment those you don't need at the particular time by placing # in front of that line. In the acuTrans command, you can specify which surface set you want to query. Example: acuTrans -osi -osis Fan1 -osiv moment See acuTrans -h for complete usage and/or review the Programs Reference Manual, acuTrans section
  18. If you issue the command: acuTrans -h you'll see one of the options is -mc for moment_center: acuTrans -h | grep center acuTrans: -mc <str> center about which moment is computed acuTrans: moment_center= 0,0,0 [default] If you're using Linux, you can add -mc 0.0,2.5,-2.3 to the acuTrans command directly. If you're using Windows, you'll need to add the option to your local Acusim.cnf file - as the Windows parser typically doesn't work well with the commas. (This also works for Linux if you don't want to type it as part of the acuTrans command.) For example, in the Acusim.cnf file add: moment_center = 0.0,2.5,-2.3
  19. You may be able to accomplish this using FVX scripting. You can get FVX information in the /fv/help/FV_ReferenceManual.pdf included in the installation. The attachment has an example from which to start, then maybe use the 'modify' command within a loop to change locations and perform the queries. (You may want to consult with your local Support team as well...) test.fvx
  20. I just ran through this tutorial, and it seems to work correctly as written. (I did notice that you had left Simple BC active for the Beam surface, where it should be inactive/off since it's handled by the External Code Surface command. In any case, it still ran when I did leave it active as you had it.) Is it possible you assigned the BCs to the wrong surface sets? Can you attach the slab_dcfsi.out and cci.txt files from your run? Which versions of AcuSolve/OptiStruct are you using? (I have HyperWorks CFD Solvers 2019.1 and HyperWorks Solver 2019.2.)
  21. Which physics phenomena are you trying to capture with the simulation? Can you add the .inp file and .Log file?
  22. You should probably post that question to the OptiStruct forum - rather than this AcuSolve forum.
  23. AcuConsole doesn't support the mixed-element topology the same way that HyperMesh does. If you build the mesh as all-tets in HyperMesh (boundary layers, everything all tets) then you'll see the same groupings in AcuConsole.
  24. Most likely there is some problem with the problem setup, with the Assertion at the start, plus the BC Warnings in the Log file. Best to contact your local support office.
  25. I'm wondering if there's some difference in the keyboard/language of your OS. The original error is: Invalid command line option <ûto> where if it was related to the problem name not being specified, it would be something like: "Undefined problem". Is it possible you have two different characters that look like the - on your keyboard?
×
×
  • Create New...