Jump to content

acupro

Members
  • Content Count

    228
  • Joined

  • Last visited

  • Days Won

    12

acupro last won the day on December 19 2019

acupro had the most liked content!

4 Followers

About acupro

  • Rank
    Super User

Profile Information

  • Country
    United States
  • Are you University user?
    No

Recent Profile Visitors

2077 profile views
  1. 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
  2. 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.
  3. 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?
  4. 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.
  5. 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.
  6. 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.
  7. 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
  8. 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
  9. 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
  10. 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.)
  11. Which physics phenomena are you trying to capture with the simulation? Can you add the .inp file and .Log file?
  12. You should probably post that question to the OptiStruct forum - rather than this AcuSolve forum.
  13. 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.
  14. 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.
  15. 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...