Best Of
Find Holes and Create Spiders
Overview
This script allows the user to select comps that have holes in it, select a search tolerance, and it will then find all of the holes within those tolerances and then automatically create spiders in each of those holes.
Usage/Installation Instructions
Step 1: Select the components where you would like to find holes.
Step 2: Enter the minimum hole diameter for the search
Step 3: Enter the maximum hole diameter for the search
Step 4: It will then search for a single node per hole and make a temp node there for you. You then should inspect the results, and select the nodes you do not want to be used to create spiders.
Step 5: Then you are allowed to select additional nodes to include in the spider creation.
Step 6: It will then make a spider for every node you have selected and put them all into a new component called “Spiders”.
Limitation
You can only select and deselect the node selection once before you click "proceed" to create the spiders.
Functionality
Connectors|Meshing
Subfunctionality
1D Meshing
Interface
No Specific Interface
Chayan
Hwascii Export Tool From HyperView
Overview
HWASCII export tool from HyperView. It exports any data type from any solver interface to HASCII format file. (Ver. 11: HWDesktop SA1-120)
Usage/Installation Instructions
1. Load model + result (from any solver) in HV
2. Contour the data type you want to export
3. Run the scrirt
4. Select the hwascii file path
5. If you want to append to the existing hwascii file please select the append check box.
6. Export Some of the key points to be noted are:
1. This tool exports for all the simulation in the given subcase for the selected data type.
2. Exports complex results
3. Exports corner results
4. Export vector,tensor,scalar results
Limitation
1. Does not export layer information. It export for the current layer.
2. Does not export the coordinate system information
3. Does not export the id pool information
Functionality
Results
Subfunctionality
Contour
Interface
No Specific Interface
Chayan
Re: How to create track vehicle modeling in MV 2023?
I tried to use a repositioned link graphic but it doesn't show the graphic.
When I use primitive graphics, no errors appear.
please find the attach to know link CAD
Thanks
Re: How to create track vehicle modeling in MV 2023?
Hi.
Your "link.x_t" needs to be scaled into mm. It was x1000 to small. Then it wokrs.
I have attached a re-scaled version of the link.
/Erik
GTT Erik
Re: How to pass a variable to a different __device__ in CUDA Code?
Hi,
On CPU, through the geometryManager( ) you can access quite a few different helper functions. I think the one you're going to want to use is:
So what I'd do is something like:
1) Declare a member variable in my plugin to hold the manager, so I can use it anywhere in your plugin2) Initialise it in starting( ), with something like the following (although this is for a different manager that I'm using in the plugin I'm working on)
3) Pass in your geometry/geometries to the get geometry index call for whichever geometries you want. There is also a function to get all your geometry names in the manager too, to simplify this
4) Once you know which index is which, pass it across to the GPU through one of the parameterData functions and use it how you need.
Hopefully that makes sense, though I realise it's a little convoluted.Cheers,
Richard
Edit: I'm using v1.4 of the geometry manager here. Depending on which version of EDEM/the API you're using, you might not have all these functions.
Thank you Richard, very much appreciate your help and answer.
I ended up using the ID and isParticle function approach, as it is working with CUDA as well. I forgot that "element.1" is always a particle, so it gave me weird results in the first run..
Works now!
Regards
What's new in Altair® FluxMotor® 2023.1 ?
Altair FluxMotor 2023.1
Creating a motor model in FluxMotor and be ready to run multiphysics studies takes only a few clicks and a few minutes. You can also easily create a Flux model for 2D or 3D analysis, speeding up the simulation process. With this new version of FluxMotor, we are extending the possibilities by introducing new machine types. And new ones will also come in the close future.
POLYPHASE SYNCHRONOUS MACHINES
Polyphase machines are used in electrification mostly to ensure better reliability. You can now define synchronous permanent magnet machines, with inner or outer rotors, having more than 3 phases: 5 to 15 (only odd numbers).
The characteristics of the winding architecture can be defined in detailed in the winding area of FluxMotor. Once defined, the machine can be exported to Flux 2D or Flux Skew.
Defining a 7-phase machine in FluxMotor
WOUND FIELD MACHINES
Quite well known in the field of power generation, wound field synchronous machines can also be used for traction. This technology offers good efficiencies and various control scheme options and does not rely on costly rare-earth permanent magnets. You can now define such machines in FluxMotor with a wide library of rotor part templates that will let you consider various types of pole shapes, dampers and field windings. A dedicated interface will help you define the rotor winding architecture, defining the characteristics of the coils, the insulation and the end-winding dimensions.
A wound field synchronous machine easily defined
When the model is ready, it can be exported right away to Flux to perform working point or back-emf analysis.
AUTOMATED CALIBRATION OF THERMAL NETWORKS
When performing thermal computations at pre-design stage, FluxMotor is using 1D thermal networks that are automatically extracted from the motor topology definition. To increase the accuracy of the model, you have the possibility to use X-Factors that will adjust thermal resistances or cooling method inputs. It helps to be consistent with measurement results for instance and will have an impact on the resulting temperatures one gets in steady state or transient simulations. This calibration process can be fully automated with the new version of FluxMotor. You target the temperatures to be obtained and the X-Factors will be determined automatically to reach this goal. You can easily calibrate a model from measurement and then use it to extensively test your machine in various conditions.
Automated calibration of thermal simulation for fast and accurate temperature predictions
3D MODEL GENERATION FOR INDUCTION MACHINES
Have you ever tried to generate a 3D finite element model of an induction machine ? It can get quite time consuming ! Within FluxMotor, you can now do it in a very few steps for induction machines with squirrel cages. You have the option to consider the full machine or take advantage of periodicities and symmetries to reduce the model size. The lengths of the rotor and the stator can be different. Geometry, mesh, winding, circuit are automatically generated. Your model is ready to be solved.
Getting a 3D model ready to be solved in a few minutes
Want to know more about the new version? Get all the details in the Release Notes [Link].
If you want to learn also about Flux and its new features, follow this [Link]
Enjoy the new version !
Fabrice Marion - Senior Program Manager - FluxMotor®
Vincent Leconte - Senior Director - Electrification Solutions
Re: How to pass a variable to a different __device__ in CUDA Code?
Hi Richard,
thanks seems to work just fine!
Is there a function to access the geometry directly and not via the ID function? I found a getTypeIndex (Returns the index of the particletype/geometry group. ) function but i don't know the index of my geometry group. Where can i find that?
Thank you
Hi,
On CPU, through the geometryManager( ) you can access quite a few different helper functions. I think the one you're going to want to use is:
So what I'd do is something like:
1) Declare a member variable in my plugin to hold the manager, so I can use it anywhere in your plugin
2) Initialise it in starting( ), with something like the following (although this is for a different manager that I'm using in the plugin I'm working on)
3) Pass in your geometry/geometries to the get geometry index call for whichever geometries you want. There is also a function to get all your geometry names in the manager too, to simplify this
4) Once you know which index is which, pass it across to the GPU through one of the parameterData functions and use it how you need.
Hopefully that makes sense, though I realise it's a little convoluted.
Cheers,
Richard
Edit: I'm using v1.4 of the geometry manager here. Depending on which version of EDEM/the API you're using, you might not have all these functions.
RWood
Re: How to create track vehicle modeling in MV 2023?
And to the point position question: There is a ms_ref market in each of the rollers that you can reorient to make the nodes align with the CAD.
/Erik
GTT Erik
Re: How to create track vehicle modeling in MV 2023?
Hi Brian,
Your “link-graphic-file” is not centered on (0,0,0) which then results in an offset to the wrapped link positions. Using the std. primitive CAD for the links shows good correlation.
Reposition the link-CAD to be centered at (0,0,0) then it should align.
/Erik
GTT Erik
Re: How to measure strains versus time responses for SPH analysis bird striking on plate
Dear Adriano A. Koga,
Thank you very much for your reply.
I have added a tensor of strain card which is shown as follows.
Also requested plotting for the top layer as follows
But results are not in order
kindly suggest any correction.
Regards ,
Sachin
correlation is not so simple, but as a remark the paper shows probably principal strains and not vonMises, as you're plotting. The paper results shows negative strain values, which would not happen plotting vonMises.
Anyway, the red curve seems to be very high. The others are showing strains around 5000~10000microstrains, which is not so far from the paper, apparently.
Could you share the reference paper?
