[GiDlist] pressure-velocity visualization
Moderator: GiD Team
[GiDlist] pressure-velocity visualization
Hello,
i would like to know how to visualize (animation in fluid dynamics)
pressure and velocity on a free surface at the same time.
Like at page 166 of GID Reference Manual Version 7. There is no enough
explanation on the topic.
thank you
abdou
i would like to know how to visualize (animation in fluid dynamics)
pressure and velocity on a free surface at the same time.
Like at page 166 of GID Reference Manual Version 7. There is no enough
explanation on the topic.
thank you
abdou
[GiDlist] GiD 8 ??
Hi,
we would like to order licences of GiD for our institute, but I just
saw in the announcement for the 3rd GiD Conference that GiD 8 will be
available next year.
Could you please tell me when GiD 8 will be available. Is it possible to
buy licences for GiD 8 in advance? How much would an update cost?
Thanks a lot for your information.
Regards
M. Neumann
--
Malte Neumann
Institute of Structural Mechanics, University of Stuttgart, Germany
http://www.uni-stuttgart.de/ibs/members/neumann/
we would like to order licences of GiD for our institute, but I just
saw in the announcement for the 3rd GiD Conference that GiD 8 will be
available next year.
Could you please tell me when GiD 8 will be available. Is it possible to
buy licences for GiD 8 in advance? How much would an update cost?
Thanks a lot for your information.
Regards
M. Neumann
--
Malte Neumann
Institute of Structural Mechanics, University of Stuttgart, Germany
http://www.uni-stuttgart.de/ibs/members/neumann/
[GiDlist] Bug in Element definition
Hi everynody,
i'm using GiD Version 7.7.0b on a SuSE Linux 9.3 machine.
The following bug occours during mesh generation:
Elements are defined wrong, so that a negative Jacobi Determinant is
reported by our simulation program.
This it is not GiD that reports the error, but still produces it.
Proof of bug:
create a line, i.e.
line from 0,1 to 0,2
then rotate this line my -90° using the copy menu using the
2D switch, rotating around 0,0 - extruding surfaces.
Create a mesh and look at the element definitions.
They are clockwise.
Then switch to geometry view, and switch the normal of the surface you
previously created by extruding.
Remesh
The elements are now defined counterclockwise and everything is fine.
Regards
Martin Meiler
--
--------------------------------------------------------------------
_/ _/_/ _/_/_/ Friedrich Alexander Universität Erlangen
_/ _/ _/ _/ Lehrstuhl für Sensorik
_/ _/ _/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
_/ _/_/ _/_/
_/ _/ _/ University of Erlangen
_/ _/ _/ _/ Department of Sensor Technology
_/_/_/ _/_/ _/_/_/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
Dipl.-Ing. Martin Meiler
tel.: (+49)-9131-85-23140
fax.: (+49)-9131-85-23133
email: Martin.Meiler at lse.eei.uni-erlangen.de
i'm using GiD Version 7.7.0b on a SuSE Linux 9.3 machine.
The following bug occours during mesh generation:
Elements are defined wrong, so that a negative Jacobi Determinant is
reported by our simulation program.
This it is not GiD that reports the error, but still produces it.
Proof of bug:
create a line, i.e.
line from 0,1 to 0,2
then rotate this line my -90° using the copy menu using the
2D switch, rotating around 0,0 - extruding surfaces.
Create a mesh and look at the element definitions.
They are clockwise.
Then switch to geometry view, and switch the normal of the surface you
previously created by extruding.
Remesh
The elements are now defined counterclockwise and everything is fine.
Regards
Martin Meiler
--
--------------------------------------------------------------------
_/ _/_/ _/_/_/ Friedrich Alexander Universität Erlangen
_/ _/ _/ _/ Lehrstuhl für Sensorik
_/ _/ _/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
_/ _/_/ _/_/
_/ _/ _/ University of Erlangen
_/ _/ _/ _/ Department of Sensor Technology
_/_/_/ _/_/ _/_/_/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
Dipl.-Ing. Martin Meiler
tel.: (+49)-9131-85-23140
fax.: (+49)-9131-85-23133
email: Martin.Meiler at lse.eei.uni-erlangen.de
[GiDlist] problems with conditions
Hello everybody,
when applying our problemtype we define within our conditionsfile (.cnd)
the following condition:
NUMBER: 161 CONDITION: Line_Elem_Labels
CONDTYPE: over lines
CONDMESHTYPE: over body elements
CANREPEAT: yes
QUESTION: NameID
Value: 0
END CONDITION
This should realize boundary conditions defined by 1D line elements.
We later on use
GiD_Process data cond assign Line_Node_Labels change 1 17
that should apply this special condition to line 17 and index this
condition with index 1
This works quite fine for just one line, but if we define the same
condition to more than one line, like
GiD_Process data cond assign Line_Node_Labels change 1 17 18 19
or even
GiD_Process data cond assign Line_Node_Labels change 1 17
GiD_Process data cond assign Line_Node_Labels change 2 18
GiD_Process data cond assign Line_Node_Labels change 3 19
we obtain the following error when generating the mesh:
Condition 'Line_Elem_Labels' has flag 'on elements' and maybe it needs
flag 'on face elememts' in the .cnd file in the problem type
2.5
Error when transfering condition 'Line_Elem_Labels' from geometry to
mesh in line 12. It has not been transfered.
Well, where is my/our error or what does GiD want to tell me by this
behaviour.
I'm using the actual GiD 7.7.0b Beta version.
Thanks for your help
Regards
Martin
--
--------------------------------------------------------------------
_/ _/_/ _/_/_/ Friedrich Alexander Universität Erlangen
_/ _/ _/ _/ Lehrstuhl für Sensorik
_/ _/ _/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
_/ _/_/ _/_/
_/ _/ _/ University of Erlangen
_/ _/ _/ _/ Department of Sensor Technology
_/_/_/ _/_/ _/_/_/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
Dipl.-Ing. Martin Meiler
tel.: (+49)-9131-85-23140
fax.: (+49)-9131-85-23133
email: Martin.Meiler at lse.eei.uni-erlangen.de
when applying our problemtype we define within our conditionsfile (.cnd)
the following condition:
NUMBER: 161 CONDITION: Line_Elem_Labels
CONDTYPE: over lines
CONDMESHTYPE: over body elements
CANREPEAT: yes
QUESTION: NameID
Value: 0
END CONDITION
This should realize boundary conditions defined by 1D line elements.
We later on use
GiD_Process data cond assign Line_Node_Labels change 1 17
that should apply this special condition to line 17 and index this
condition with index 1
This works quite fine for just one line, but if we define the same
condition to more than one line, like
GiD_Process data cond assign Line_Node_Labels change 1 17 18 19
or even
GiD_Process data cond assign Line_Node_Labels change 1 17
GiD_Process data cond assign Line_Node_Labels change 2 18
GiD_Process data cond assign Line_Node_Labels change 3 19
we obtain the following error when generating the mesh:
Condition 'Line_Elem_Labels' has flag 'on elements' and maybe it needs
flag 'on face elememts' in the .cnd file in the problem type
2.5
Error when transfering condition 'Line_Elem_Labels' from geometry to
mesh in line 12. It has not been transfered.
Well, where is my/our error or what does GiD want to tell me by this
behaviour.
I'm using the actual GiD 7.7.0b Beta version.
Thanks for your help
Regards
Martin
--
--------------------------------------------------------------------
_/ _/_/ _/_/_/ Friedrich Alexander Universität Erlangen
_/ _/ _/ _/ Lehrstuhl für Sensorik
_/ _/ _/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
_/ _/_/ _/_/
_/ _/ _/ University of Erlangen
_/ _/ _/ _/ Department of Sensor Technology
_/_/_/ _/_/ _/_/_/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
Dipl.-Ing. Martin Meiler
tel.: (+49)-9131-85-23140
fax.: (+49)-9131-85-23133
email: Martin.Meiler at lse.eei.uni-erlangen.de
[GiDlist] problems with conditions
Hello again,
i resolved the problem and it has its origin in using the function
GiD_Process
I have an array containing the entities for a certain element boundary
condition.
I use the following command
GiD_Process Meshing MeshCriteria Mesh
$bndryRegionData(selType,$regionNo) $bndryRegionData(entities,$regionNo)
and i can see within the Undo history, that i.e. the following has been
executed
Meshing MeshCriteria Mesh 1 "1 15"
If i use .central.s process instead of GiD_Process, then
Meshing MeshCriteria Mesh 1 1 15
is executed by GiD.
So is there a difference between the use of GiD_Process and .central.s
process ?
Concerning the mentioned problem, i now understand what happened:
This behaviour didn't create 1D line elements and therefore the
condition assigned to the line couldn't be mapped from the line entity
to the refering mesh elements, because they didn't exist.
Thanks for an answer to the difference between GiD_Process and
.central.s process question
Regards
Martin
Martin Meiler wrote:
Hello everybody,
when applying our problemtype we define within our conditionsfile (.cnd)
the following condition:
NUMBER: 161 CONDITION: Line_Elem_Labels
CONDTYPE: over lines
CONDMESHTYPE: over body elements
CANREPEAT: yes
QUESTION: NameID
Value: 0
END CONDITION
This should realize boundary conditions defined by 1D line elements.
We later on use
GiD_Process data cond assign Line_Node_Labels change 1 17
that should apply this special condition to line 17 and index this
condition with index 1
This works quite fine for just one line, but if we define the same
condition to more than one line, like
GiD_Process data cond assign Line_Node_Labels change 1 17 18 19
or even
GiD_Process data cond assign Line_Node_Labels change 1 17
GiD_Process data cond assign Line_Node_Labels change 2 18
GiD_Process data cond assign Line_Node_Labels change 3 19
we obtain the following error when generating the mesh:
Condition 'Line_Elem_Labels' has flag 'on elements' and maybe it needs
flag 'on face elememts' in the .cnd file in the problem type
2.5
Error when transfering condition 'Line_Elem_Labels' from geometry to
mesh in line 12. It has not been transfered.
Well, where is my/our error or what does GiD want to tell me by this
behaviour.
I'm using the actual GiD 7.7.0b Beta version.
Thanks for your help
Regards
Martin
--
--------------------------------------------------------------------
_/ _/_/ _/_/_/ Friedrich Alexander Universität Erlangen
_/ _/ _/ _/ Lehrstuhl für Sensorik
_/ _/ _/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
_/ _/_/ _/_/
_/ _/ _/ University of Erlangen
_/ _/ _/ _/ Department of Sensor Technology
_/_/_/ _/_/ _/_/_/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
Dipl.-Ing. Martin Meiler
tel.: (+49)-9131-85-23140
fax.: (+49)-9131-85-23133
email: Martin.Meiler at lse.eei.uni-erlangen.de
i resolved the problem and it has its origin in using the function
GiD_Process
I have an array containing the entities for a certain element boundary
condition.
I use the following command
GiD_Process Meshing MeshCriteria Mesh
$bndryRegionData(selType,$regionNo) $bndryRegionData(entities,$regionNo)
and i can see within the Undo history, that i.e. the following has been
executed
Meshing MeshCriteria Mesh 1 "1 15"
If i use .central.s process instead of GiD_Process, then
Meshing MeshCriteria Mesh 1 1 15
is executed by GiD.
So is there a difference between the use of GiD_Process and .central.s
process ?
Concerning the mentioned problem, i now understand what happened:
This behaviour didn't create 1D line elements and therefore the
condition assigned to the line couldn't be mapped from the line entity
to the refering mesh elements, because they didn't exist.
Thanks for an answer to the difference between GiD_Process and
.central.s process question
Regards
Martin
Martin Meiler wrote:
Hello everybody,
when applying our problemtype we define within our conditionsfile (.cnd)
the following condition:
NUMBER: 161 CONDITION: Line_Elem_Labels
CONDTYPE: over lines
CONDMESHTYPE: over body elements
CANREPEAT: yes
QUESTION: NameID
Value: 0
END CONDITION
This should realize boundary conditions defined by 1D line elements.
We later on use
GiD_Process data cond assign Line_Node_Labels change 1 17
that should apply this special condition to line 17 and index this
condition with index 1
This works quite fine for just one line, but if we define the same
condition to more than one line, like
GiD_Process data cond assign Line_Node_Labels change 1 17 18 19
or even
GiD_Process data cond assign Line_Node_Labels change 1 17
GiD_Process data cond assign Line_Node_Labels change 2 18
GiD_Process data cond assign Line_Node_Labels change 3 19
we obtain the following error when generating the mesh:
Condition 'Line_Elem_Labels' has flag 'on elements' and maybe it needs
flag 'on face elememts' in the .cnd file in the problem type
2.5
Error when transfering condition 'Line_Elem_Labels' from geometry to
mesh in line 12. It has not been transfered.
Well, where is my/our error or what does GiD want to tell me by this
behaviour.
I'm using the actual GiD 7.7.0b Beta version.
Thanks for your help
Regards
Martin
--
--------------------------------------------------------------------
_/ _/_/ _/_/_/ Friedrich Alexander Universität Erlangen
_/ _/ _/ _/ Lehrstuhl für Sensorik
_/ _/ _/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
_/ _/_/ _/_/
_/ _/ _/ University of Erlangen
_/ _/ _/ _/ Department of Sensor Technology
_/_/_/ _/_/ _/_/_/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
Dipl.-Ing. Martin Meiler
tel.: (+49)-9131-85-23140
fax.: (+49)-9131-85-23133
email: Martin.Meiler at lse.eei.uni-erlangen.de
[GiDlist] problems with conditions
There is an importand difference between GiD_Process and .central.s process:
GiD_Process preserve his number of parameters, and they have standard tcl list syntax
.central.s process split the parameters in separated words if they include spaces
Usually the GiD commands are single words, but sometimes they have spaces (for example a filenames, layernames, etc)
It's difficult to use .central.s process if his parameters can include spaces , it's necessary to add additional quotes
for example if you use:
set filename "C:/My dir/test"
.central.s process escape files read $filename
The command fail, because filename is splitted in two words "C:/My" and "dir/test", then GiD can´t open the file "C:/My" and unknow the other command "dir/test"
You must use some like this to avoid this problem:
if { [llength $filename] 1 } {
# if include spaces must be enclosed with additional quotes
.central.s process escape files read \"$filename\"
} else {
.central.s process escape files read $filename
}
The best option is to use the new GiD_Process command
GiD_Process escape files read $filename
In your case, you set a variable with several GiD commands, for example
set cmd "escape escape geometry create point 1.0,1.0,0.0"
if you use
.central.s process $cmd
it works, because $cmd is splitted in 6 words "escape" "escape" "geometry" "create" "point" "1.0,1.0,0.0"
and
GiD_Process $cmd
fail, because "escape escape geometry create point 1.0,1.0,0.0" is traited as a single word
A trick to solve this problem using the Tcl eval command to split $cmd before be send to GiD_Process
eval GiD_Process $cmd
Note: For this useful problem, the future Tcl 8.5 language will include an special command {expand}to split arguments,
then in the future can be used some like: GiD_Process {expand}$cmd
Concluding, It's better to use GiD_Process (.central.s process will be deprecated)
Regards
Enrique Escolano
----- Original Message -----
From: "Martin Meiler" Martin.Meiler at lse.eei.uni-erlangen.de
To: gidlist at gatxan.cimne.upc.edu
Sent: Wednesday, November 09, 2005 10:06 AM
Subject: Re: [GiDlist] problems with conditions
Hello again,
i resolved the problem and it has its origin in using the function
GiD_Process
I have an array containing the entities for a certain element boundary
condition.
I use the following command
GiD_Process Meshing MeshCriteria Mesh
$bndryRegionData(selType,$regionNo) $bndryRegionData(entities,$regionNo)
and i can see within the Undo history, that i.e. the following has been
executed
Meshing MeshCriteria Mesh 1 "1 15"
If i use .central.s process instead of GiD_Process, then
Meshing MeshCriteria Mesh 1 1 15
is executed by GiD.
So is there a difference between the use of GiD_Process and .central.s
process ?
Concerning the mentioned problem, i now understand what happened:
This behaviour didn't create 1D line elements and therefore the
condition assigned to the line couldn't be mapped from the line entity
to the refering mesh elements, because they didn't exist.
Thanks for an answer to the difference between GiD_Process and
.central.s process question
Regards
Martin
Martin Meiler wrote:
Hello everybody,
when applying our problemtype we define within our conditionsfile (.cnd)
the following condition:
NUMBER: 161 CONDITION: Line_Elem_Labels
CONDTYPE: over lines
CONDMESHTYPE: over body elements
CANREPEAT: yes
QUESTION: NameID
Value: 0
END CONDITION
This should realize boundary conditions defined by 1D line elements.
We later on use
GiD_Process data cond assign Line_Node_Labels change 1 17
that should apply this special condition to line 17 and index this
condition with index 1
This works quite fine for just one line, but if we define the same
condition to more than one line, like
GiD_Process data cond assign Line_Node_Labels change 1 17 18 19
or even
GiD_Process data cond assign Line_Node_Labels change 1 17
GiD_Process data cond assign Line_Node_Labels change 2 18
GiD_Process data cond assign Line_Node_Labels change 3 19
we obtain the following error when generating the mesh:
Condition 'Line_Elem_Labels' has flag 'on elements' and maybe it needs
flag 'on face elememts' in the .cnd file in the problem type
2.5
Error when transfering condition 'Line_Elem_Labels' from geometry to
mesh in line 12. It has not been transfered.
Well, where is my/our error or what does GiD want to tell me by this
behaviour.
I'm using the actual GiD 7.7.0b Beta version.
Thanks for your help
Regards
Martin
--
--------------------------------------------------------------------
_/ _/_/ _/_/_/ Friedrich Alexander Universität Erlangen
_/ _/ _/ _/ Lehrstuhl für Sensorik
_/ _/ _/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
_/ _/_/ _/_/
_/ _/ _/ University of Erlangen
_/ _/ _/ _/ Department of Sensor Technology
_/_/_/ _/_/ _/_/_/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
Dipl.-Ing. Martin Meiler
tel.: (+49)-9131-85-23140
fax.: (+49)-9131-85-23133
email: Martin.Meiler at lse.eei.uni-erlangen.de
_______________________________________________
GiDlist mailing list
GiDlist at gid.cimne.upc.es
http://gid.cimne.upc.es/mailman/listinfo/gidlist
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listas.cimne.upc.edu/pipermail/gidlist/attachments/20051109/eea47b54/attachment.htm
GiD_Process preserve his number of parameters, and they have standard tcl list syntax
.central.s process split the parameters in separated words if they include spaces
Usually the GiD commands are single words, but sometimes they have spaces (for example a filenames, layernames, etc)
It's difficult to use .central.s process if his parameters can include spaces , it's necessary to add additional quotes
for example if you use:
set filename "C:/My dir/test"
.central.s process escape files read $filename
The command fail, because filename is splitted in two words "C:/My" and "dir/test", then GiD can´t open the file "C:/My" and unknow the other command "dir/test"
You must use some like this to avoid this problem:
if { [llength $filename] 1 } {
# if include spaces must be enclosed with additional quotes
.central.s process escape files read \"$filename\"
} else {
.central.s process escape files read $filename
}
The best option is to use the new GiD_Process command
GiD_Process escape files read $filename
In your case, you set a variable with several GiD commands, for example
set cmd "escape escape geometry create point 1.0,1.0,0.0"
if you use
.central.s process $cmd
it works, because $cmd is splitted in 6 words "escape" "escape" "geometry" "create" "point" "1.0,1.0,0.0"
and
GiD_Process $cmd
fail, because "escape escape geometry create point 1.0,1.0,0.0" is traited as a single word
A trick to solve this problem using the Tcl eval command to split $cmd before be send to GiD_Process
eval GiD_Process $cmd
Note: For this useful problem, the future Tcl 8.5 language will include an special command {expand}to split arguments,
then in the future can be used some like: GiD_Process {expand}$cmd
Concluding, It's better to use GiD_Process (.central.s process will be deprecated)
Regards
Enrique Escolano
----- Original Message -----
From: "Martin Meiler" Martin.Meiler at lse.eei.uni-erlangen.de
To: gidlist at gatxan.cimne.upc.edu
Sent: Wednesday, November 09, 2005 10:06 AM
Subject: Re: [GiDlist] problems with conditions
Hello again,
i resolved the problem and it has its origin in using the function
GiD_Process
I have an array containing the entities for a certain element boundary
condition.
I use the following command
GiD_Process Meshing MeshCriteria Mesh
$bndryRegionData(selType,$regionNo) $bndryRegionData(entities,$regionNo)
and i can see within the Undo history, that i.e. the following has been
executed
Meshing MeshCriteria Mesh 1 "1 15"
If i use .central.s process instead of GiD_Process, then
Meshing MeshCriteria Mesh 1 1 15
is executed by GiD.
So is there a difference between the use of GiD_Process and .central.s
process ?
Concerning the mentioned problem, i now understand what happened:
This behaviour didn't create 1D line elements and therefore the
condition assigned to the line couldn't be mapped from the line entity
to the refering mesh elements, because they didn't exist.
Thanks for an answer to the difference between GiD_Process and
.central.s process question
Regards
Martin
Martin Meiler wrote:
Hello everybody,
when applying our problemtype we define within our conditionsfile (.cnd)
the following condition:
NUMBER: 161 CONDITION: Line_Elem_Labels
CONDTYPE: over lines
CONDMESHTYPE: over body elements
CANREPEAT: yes
QUESTION: NameID
Value: 0
END CONDITION
This should realize boundary conditions defined by 1D line elements.
We later on use
GiD_Process data cond assign Line_Node_Labels change 1 17
that should apply this special condition to line 17 and index this
condition with index 1
This works quite fine for just one line, but if we define the same
condition to more than one line, like
GiD_Process data cond assign Line_Node_Labels change 1 17 18 19
or even
GiD_Process data cond assign Line_Node_Labels change 1 17
GiD_Process data cond assign Line_Node_Labels change 2 18
GiD_Process data cond assign Line_Node_Labels change 3 19
we obtain the following error when generating the mesh:
Condition 'Line_Elem_Labels' has flag 'on elements' and maybe it needs
flag 'on face elememts' in the .cnd file in the problem type
2.5
Error when transfering condition 'Line_Elem_Labels' from geometry to
mesh in line 12. It has not been transfered.
Well, where is my/our error or what does GiD want to tell me by this
behaviour.
I'm using the actual GiD 7.7.0b Beta version.
Thanks for your help
Regards
Martin
--
--------------------------------------------------------------------
_/ _/_/ _/_/_/ Friedrich Alexander Universität Erlangen
_/ _/ _/ _/ Lehrstuhl für Sensorik
_/ _/ _/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
_/ _/_/ _/_/
_/ _/ _/ University of Erlangen
_/ _/ _/ _/ Department of Sensor Technology
_/_/_/ _/_/ _/_/_/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
Dipl.-Ing. Martin Meiler
tel.: (+49)-9131-85-23140
fax.: (+49)-9131-85-23133
email: Martin.Meiler at lse.eei.uni-erlangen.de
_______________________________________________
GiDlist mailing list
GiDlist at gid.cimne.upc.es
http://gid.cimne.upc.es/mailman/listinfo/gidlist
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listas.cimne.upc.edu/pipermail/gidlist/attachments/20051109/eea47b54/attachment.htm
[GiDlist] Bug in Element definition
You are rigth, but it's not really a GiD bug.
In general, specially in 3D space, it's valid that the normal points to any
direction.
You can have a surface in the XY plane with normal pointing to +Z , but you
can move
this surface (for example rotate 180 degrees arount the X axe) then the
normal now points to -Z.
In other hand, to facilitate the use, when GiD create a surface in the XY
plane, it usually automatically set
the orientation to point to +Z, to avoid orientation problems (negative
determinants) for 2D FEM solvers.
In any case, the user (or automatically the problemtype) must check the
surfaces orientation (GiD has tools to draw by colors, swap, etc).
Note: The elements orientation is the same as the source surface orientation
Regards
Enrique Escolano
----- Original Message -----
From: "Martin Meiler" Martin.Meiler at lse.eei.uni-erlangen.de
To: gidlist at gatxan.cimne.upc.es
Sent: Wednesday, November 09, 2005 1:11 AM
Subject: [GiDlist] Bug in Element definition
Hi everynody,
i'm using GiD Version 7.7.0b on a SuSE Linux 9.3 machine.
The following bug occours during mesh generation:
Elements are defined wrong, so that a negative Jacobi Determinant is
reported by our simulation program.
This it is not GiD that reports the error, but still produces it.
Proof of bug:
create a line, i.e.
line from 0,1 to 0,2
then rotate this line my -90° using the copy menu using the
2D switch, rotating around 0,0 - extruding surfaces.
Create a mesh and look at the element definitions.
They are clockwise.
Then switch to geometry view, and switch the normal of the surface you
previously created by extruding.
Remesh
The elements are now defined counterclockwise and everything is fine.
Regards
Martin Meiler
--
--------------------------------------------------------------------
_/ _/_/ _/_/_/ Friedrich Alexander Universität Erlangen
_/ _/ _/ _/ Lehrstuhl für Sensorik
_/ _/ _/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
_/ _/_/ _/_/
_/ _/ _/ University of Erlangen
_/ _/ _/ _/ Department of Sensor Technology
_/_/_/ _/_/ _/_/_/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
Dipl.-Ing. Martin Meiler
tel.: (+49)-9131-85-23140
fax.: (+49)-9131-85-23133
email: Martin.Meiler at lse.eei.uni-erlangen.de
_______________________________________________
GiDlist mailing list
GiDlist at gid.cimne.upc.es
http://gid.cimne.upc.es/mailman/listinfo/gidlist
In general, specially in 3D space, it's valid that the normal points to any
direction.
You can have a surface in the XY plane with normal pointing to +Z , but you
can move
this surface (for example rotate 180 degrees arount the X axe) then the
normal now points to -Z.
In other hand, to facilitate the use, when GiD create a surface in the XY
plane, it usually automatically set
the orientation to point to +Z, to avoid orientation problems (negative
determinants) for 2D FEM solvers.
In any case, the user (or automatically the problemtype) must check the
surfaces orientation (GiD has tools to draw by colors, swap, etc).
Note: The elements orientation is the same as the source surface orientation
Regards
Enrique Escolano
----- Original Message -----
From: "Martin Meiler" Martin.Meiler at lse.eei.uni-erlangen.de
To: gidlist at gatxan.cimne.upc.es
Sent: Wednesday, November 09, 2005 1:11 AM
Subject: [GiDlist] Bug in Element definition
Hi everynody,
i'm using GiD Version 7.7.0b on a SuSE Linux 9.3 machine.
The following bug occours during mesh generation:
Elements are defined wrong, so that a negative Jacobi Determinant is
reported by our simulation program.
This it is not GiD that reports the error, but still produces it.
Proof of bug:
create a line, i.e.
line from 0,1 to 0,2
then rotate this line my -90° using the copy menu using the
2D switch, rotating around 0,0 - extruding surfaces.
Create a mesh and look at the element definitions.
They are clockwise.
Then switch to geometry view, and switch the normal of the surface you
previously created by extruding.
Remesh
The elements are now defined counterclockwise and everything is fine.
Regards
Martin Meiler
--
--------------------------------------------------------------------
_/ _/_/ _/_/_/ Friedrich Alexander Universität Erlangen
_/ _/ _/ _/ Lehrstuhl für Sensorik
_/ _/ _/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
_/ _/_/ _/_/
_/ _/ _/ University of Erlangen
_/ _/ _/ _/ Department of Sensor Technology
_/_/_/ _/_/ _/_/_/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
Dipl.-Ing. Martin Meiler
tel.: (+49)-9131-85-23140
fax.: (+49)-9131-85-23133
email: Martin.Meiler at lse.eei.uni-erlangen.de
_______________________________________________
GiDlist mailing list
GiDlist at gid.cimne.upc.es
http://gid.cimne.upc.es/mailman/listinfo/gidlist
[GiDlist] pressure-velocity visualization
Hi,
Just inside the 'Several results window', which appears by choosing the
'Window-Several results...' entry on the top menubar, inside this window
select the 'one over another' radio button and press the apply button.
Then each different result view you choose will be stacked above the
previous one.
In the picture, first a deformation was done, then a contour fill of
'relative thickness', then vectors of the 'shell force' were displayed and
last, it shows the minimum and maximum value of the 'relative thickness'.
In the 'several resuts' window all the result views are shown inside the
listbox.
miguel
-----Mensaje original-----
De: gidlist-admin at gatxan.cimne.upc.edu
[mailto:gidlist-admin at gatxan.cimne.upc.edu] En nombre de asene at sunumail.sn
Enviado el: domingo, 06 de noviembre de 2005 13:27
Para: gidlist at gatxan.cimne.upc.edu
Asunto: [GiDlist] pressure-velocity visualization
Hello,
i would like to know how to visualize (animation in fluid dynamics)
pressure and velocity on a free surface at the same time.
Like at page 166 of GID Reference Manual Version 7. There is no enough
explanation on the topic.
thank you
abdou
_______________________________________________
GiDlist mailing list
GiDlist at gid.cimne.upc.es
http://gid.cimne.upc.es/mailman/listinfo/gidlist
Just inside the 'Several results window', which appears by choosing the
'Window-Several results...' entry on the top menubar, inside this window
select the 'one over another' radio button and press the apply button.
Then each different result view you choose will be stacked above the
previous one.
In the picture, first a deformation was done, then a contour fill of
'relative thickness', then vectors of the 'shell force' were displayed and
last, it shows the minimum and maximum value of the 'relative thickness'.
In the 'several resuts' window all the result views are shown inside the
listbox.
miguel
-----Mensaje original-----
De: gidlist-admin at gatxan.cimne.upc.edu
[mailto:gidlist-admin at gatxan.cimne.upc.edu] En nombre de asene at sunumail.sn
Enviado el: domingo, 06 de noviembre de 2005 13:27
Para: gidlist at gatxan.cimne.upc.edu
Asunto: [GiDlist] pressure-velocity visualization
Hello,
i would like to know how to visualize (animation in fluid dynamics)
pressure and velocity on a free surface at the same time.
Like at page 166 of GID Reference Manual Version 7. There is no enough
explanation on the topic.
thank you
abdou
_______________________________________________
GiDlist mailing list
GiDlist at gid.cimne.upc.es
http://gid.cimne.upc.es/mailman/listinfo/gidlist