Jump to content

Simon G

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Simon G

  1. Hello, Here is an example of a groovy function. FYI, only customers under maintenance have access to the support. In this case Qchen seems to belong to a Chinese university so the correct mail to use for him should be flux_support_apac@altair.com. Best regards hysteresis_control_with_groovy_example.zip
  2. Simon G

    need some help

    Hello, If the tutorial tells to use the build volume function then it means you're using the standard context so you should not enter the modeler to correct your geometry. About the message, it is only a warning, it should appear in white or orange. Not something important. However If there are some real intersections then maybe the geometry is not correct. In this case I would check the previous steps of the tutorial to see if anything is missing or if you made any mistake. Best regards
  3. Hi Romain, Unfortunately there is no document that can give you all pyflux commands for all entities. Most commands and attributes can be found by doing a help command (for instance "Point.help()" will give you everything about point entity. We have a few mementos that give some commands and help but not as much as you would expect I suppose. The best way to create your python script stays the manual way and recovering the log file. About your reporting, there is an interesting macro called AutomaticReport in the main folder of macros. This can generate a html and txt file whith all the info of your project. Best regards Altair_Memento_pyFlux_GB-v2.2.pdf Altair_Memento_python_GB-v2.1.pdf
  4. As said Pioborzy, you have to use the Nastran NX user profile for instance so that you have all kinds of elements (penta, hexa, tetra, pyra). Then in Element types, update all elements and export again in Nastran Format. Make sure to have one property assigned to each separate volume you want in Flux. Simon
  5. Hi Federico, I see two ways to do this : You can try to set up a parameter CASE that will go from 1 to your number of configurations in the scenario. Then all other parameters can depend on CAS with a list of values in a table. This works for IO parameters. Else, you can play with Valid functions in formulas to set up different values for each case. For example : V1*Valid(CASE,0,5.5)+V2*Valid(CASE,5.5,10.5) ==> This parameter equals V1 in cases 1 to 5 and V2 in cases 6 to 10. The MacroScreening allows giving Flux a list of values for some parameters and Flux will solve only these values. It will automatically reproduce the same postprocessing than in the first case. For instance you solve the original project qith one set of values. Then plot a curve. When you launch the macro you can select this curve and your txt file with the configurations. Flux will run everything and give you an excel fil with the curve values for all confuigurations. It also works with sensors. Best regards
  • Create New...