Search found 16 matches
- Thu Feb 10, 2022 2:28 pm
- Forum: Customization
- Topic: Condition over duplicate nodes using CustomLIB
- Replies: 8
- Views: 5352
Re: Condition over duplicate nodes using CustomLIB
Thank you so much for your help!
- Wed Feb 09, 2022 8:03 pm
- Forum: Customization
- Topic: Condition over duplicate nodes using CustomLIB
- Replies: 8
- Views: 5352
fcdiass
Thank you so much for your explanation. I was trying to implement some tricks for the 14 version of GiD. No matter what choice I make, I will have to identify duplicate nodes after each new mesh generation. So I tried to use the built-in function GiD_Event_AfterMeshGeneration with no success. Even a...
- Tue Feb 08, 2022 6:25 pm
- Forum: Customization
- Topic: Condition over duplicate nodes using CustomLIB
- Replies: 8
- Views: 5352
Re: Condition over duplicate nodes using CustomLIB
The team do not fix this bug in version 14 is unfortunate. I noticed you use – at least in the official versions of GiD – semantic versioning ( https://semver.org/ ). I think this situation demands an increment in the PATCH version (14.0.x) and not an increment in the MINOR version (14...
- Wed Feb 02, 2022 7:04 pm
- Forum: Customization
- Topic: Condition over duplicate nodes using CustomLIB
- Replies: 8
- Views: 5352
Re: Condition over duplicate nodes using CustomLIB
Additional information:
I am using the GiD version 14.0.6.
The example used in the previous post:
I am using the GiD version 14.0.6.
The example used in the previous post:
- Wed Feb 02, 2022 6:57 pm
- Forum: Customization
- Topic: Condition over duplicate nodes using CustomLIB
- Replies: 8
- Views: 5352
Condition over duplicate nodes using CustomLIB
Hello, I have the same problem reported years ago on this topic: https://www.gidhome.com/forum/viewtopic.php?f=9&t=2877 . The difference is that I am using the new problem type, based on the CustomLIB library. I need to define a boundary condition (fixed displacement in x and y directions) for a...
- Tue Jun 01, 2021 1:41 am
- Forum: Mesh
- Topic: Refining quadrilateral and hexahedral element meshes
- Replies: 3
- Views: 3363
Re: Refining quadrilateral and hexahedral element meshes
Sorry, GiD cannot do this kind of hexahedra refinements, with pattern of edge subdivisions 1:3 The octtree mesher is doing internally a similar subdivision with pattern 1:2, but in any case it is an internal feature not accessible at user level. Thanks for your quick answer! Currently, I am doing t...
- Fri May 28, 2021 2:01 pm
- Forum: Mesh
- Topic: Refining quadrilateral and hexahedral element meshes
- Replies: 3
- Views: 3363
Refining quadrilateral and hexahedral element meshes
Hello everyone! I would like to know GiD offers some way to refine meshes as proposed by Robert Schneiders in his work "Refining Quadrilateral and Hexahedral Element Meshes". Here we have some examples of this type of refining in 2D quadrilateral meshes: image (1).png ... and in 3D hexahed...
- Thu Dec 17, 2020 7:50 pm
- Forum: Customization
- Topic: Updating the material name
- Replies: 1
- Views: 2832
Updating the material name
Hello, I am developing a problem type with customlib. It is based on the 'cmas2d_customlib' example and inherited a problem with updating the material name. For example, in the 'cmas2d_customlib' problem type: When applying a 'Shells' condition, you need to choose a material in the list and apply it...
- Fri Nov 06, 2020 4:00 pm
- Forum: Customization
- Topic: Automatic resizing in the data tree window
- Replies: 1
- Views: 2686
Automatic resizing in the data tree window
When using the new problem type approach (with the customlib), is possible to change the state of some fields from 'hidden' to 'normal' and vice versa. Considering the GiD version 14, the opened window is adjusted according to the number of fields with the state 'hidden' or 'normal'. However, in ver...
- Fri Nov 06, 2020 2:11 pm
- Forum: Customization
- Topic: Problem type transformation
- Replies: 7
- Views: 5503
Re: Problem type transformation
Yes, I am using GiD version 14.0.5.
I am limited by my company, which bought only version 14.
There is any possibility of you release a new version (e.g. 14.0.6), which solves these bugs reported here?
I am limited by my company, which bought only version 14.
There is any possibility of you release a new version (e.g. 14.0.6), which solves these bugs reported here?