[GiDlist] Problem using post-processing

GiDList Archive 2013 - 2005
1

Warning: This message has had one or more attachments removed.
Warning: Please read the “VirusWarning.txt” attachment(s) for more information.

Hi,

I’m actually using :

GiD internal version: 8.1.5b
Operating system: ‘x86_64’ ‘unix’ ‘Linux’ ‘2.6.18.8-0.5-default’

I’m using GiD to solve a simple mechanical problem but I’m enable to see
results in post-processing mode in GiD. It seems that the quadrature rules
used in my code are not supported by GiD. Coulds you tell me more details
aboit the note display in the help menu explaining the “Postprocess results
format: ProjectName.post.res, ProjectName.flavia.res” :

Note:
If the natural coordinates used are the internal ones, almost all the Results
visualization possibilities will have some limitations for tetrahedra and
hexahedra with more than one gauss points. If the natural coordinates are
given, these limitations are extended to those elements with
number_gauss_points_per_element not included in the list written above.

Also, I use an hexahedron quadratic mesh (H20) created in GiD to solve a
problem using the linear version of this mesh (H8). In this way, the results
in the result file are those at vertices (the 12 other nodes are not included
in the result file). In post-processing mode, I’m unable to see these
results. According to this problem, What is the sense of this note in the
help:

Holes are allowed in any result. The element nodes with no result defined will
not be drawn, i.e. they will appear transparent.

Is the element nodes with no result can be skipped from the result file or
not ?

As I can see, the hexahedra of 20 nodes in postprocess are supported since
version 8.1.2b

Thanks,
Daniel Marceau

P.S. the result and mesh files are attached.







-------------- next part --------------
This is a message from the MailScanner E-Mail Virus Protection Service

The original e-mail attachment “poutre.post.msh”
is on the list of unacceptable attachments for this site and has been
replaced by this warning message.

If you wish to receive a copy of the original attachment, please
e-mail helpdesk and include the whole of this message
in your request. Alternatively, you can call them, with
the contents of this message to hand when you call.

At Fri Aug 3 04:27:29 2007 the virus scanner said:
Attempt to hide real filename extension in poutre.post.msh

Note to Help Desk: Look on the MailScanner in /var/spool/mailscanner/quarantine (message l732R0Gx019095).

Postmaster
-------------- next part --------------
This is a message from the MailScanner E-Mail Virus Protection Service

The original e-mail attachment “poutre.post.res”
is on the list of unacceptable attachments for this site and has been
replaced by this warning message.

If you wish to receive a copy of the original attachment, please
e-mail helpdesk and include the whole of this message
in your request. Alternatively, you can call them, with
the contents of this message to hand when you call.

At Fri Aug 3 04:27:29 2007 the virus scanner said:
Attempt to hide real filename extension in poutre.post.res

Note to Help Desk: Look on the MailScanner in /var/spool/mailscanner/quarantine (message l732R0Gx019095).

Postmaster

2

Your attachment was removed by security issues.
Please, can you send again your sample, compressed as a .zip file with single extension for the name (e.g. avoid something like
sample.gid.zip, use only sample.zip).

About your questions:
If you define ‘results on gauss points’, then the results drawn are not continuous between neighbour elements
Results are extrapolated from the gauss points to the nodes of the element. This extrapolation to nodes is not always possible in
the same way, depending of the number and location of gauss points.
for example, for 1 gauss point, his value is used for all nodes. for the same number of nodes that gauss points, it’s possible to
use the shape funcions to know the values on the nodes (solving a linear system).

Some features that works for nodal results, are not implemented yet for gaussian results for some type of elements.
Your code can directly extrapolate gaussian results, to nodes and write a ‘nodal result’, averaging the results of neighbour
elements to have a continuous result.

It’s not compulsory to write the result of all nodes, maybe your result is not defined over a part of the mesh, then this
elements with undefined results are drawn transparent.

If you have a H20 mesh, but not define the result in the quadratic nodes, then each element has undefined results, and all are draw
transparent. You can write a .post.msh mesh with H8 linear hexahedra.

Hexahedra of 20 nodes are supported in posprocess, but maybe some gaussian result is not implemented yet. How many gauss points and
locations are you writting in the postprocess file?

Enrique

----- Original Message -----
From: “Daniel Marceau” dmarceau at uqac.ca
To: gidlist at gatxan.cimne.upc.es
Sent: Friday, August 03, 2007 4:20 AM
Subject: [GiDlist] Problem using post-processing


Warning: This message has had one or more attachments removed.
Warning: Please read the “VirusWarning.txt” attachment(s) for more information.
Hi,
I’m actually using :
GiD internal version: 8.1.5b
Operating system: ‘x86_64’ ‘unix’ ‘Linux’ ‘2.6.18.8-0.5-default’
I’m using GiD to solve a simple mechanical problem but I’m enable to see
results in post-processing mode in GiD. It seems that the quadrature rules
used in my code are not supported by GiD. Coulds you tell me more details
aboit the note display in the help menu explaining the "Postprocess results
format: ProjectName.post.res, ProjectName.flavia.res" :
-------------------------------------------------
Note:
If the natural coordinates used are the internal ones, almost all the Results
visualization possibilities will have some limitations for tetrahedra and
hexahedra with more than one gauss points. If the natural coordinates are
given, these limitations are extended to those elements with
number_gauss_points_per_element not included in the list written above.
-------------------------------------------------
Also, I use an hexahedron quadratic mesh (H20) created in GiD to solve a
problem using the linear version of this mesh (H8). In this way, the results
in the result file are those at vertices (the 12 other nodes are not included
in the result file). In post-processing mode, I’m unable to see these
results. According to this problem, What is the sense of this note in the
help:
-------------------------------------------------
Holes are allowed in any result. The element nodes with no result defined will
not be drawn, i.e. they will appear transparent.
-------------------------------------------------
Is the element nodes with no result can be skipped from the result file or
not ?
As I can see, the hexahedra of 20 nodes in postprocess are supported since
version 8.1.2b
Thanks,
Daniel Marceau
P.S. the result and mesh files are attached.






\

3

Dear GiD,

I was trying to transfer my fortran code from compaq Visual fortran 6.6 to Intel IA-32 compiler v.10 (running on VS .net2005 platform). The problem is that the compiler can’t interpret “gidost.lib” from the previous version. Do you have some experience on that matter? Thank you.

Best regards,

Adisorn Owatsiriwong
-------------- next part --------------
An HTML attachment was scrubbed…
URL: http://listas.cimne.upc.edu/pipermail/gidlist/attachments/20070803/650b5728/attachment.htm

4

Hello Adisorn, we have not tested that situation.

We need you to answer a few question in order to diagnose the problem:

  • what is the version of gidpost?

  • what does the compiler say when it try to use gidpost.lib?

  • did you build gidpost.lib?

regards,


adisorn wrote:
Dear GiD,
I was trying to transfer my fortran code from compaq Visual fortran 6.6
to Intel IA-32 compiler v.10 (running on VS net2005 platform). The
problem is that the compiler can’t interpret “gidost.lib” from the
previous version. Do you have some experience on that matter? Thank you.
Best regards,
Adisorn Owatsiriwong

5

Hello GiD team,

I want to do
“dividing the problem into different layers according to the different
materials” for a .post.msh file which I created using my simple mesh
generator (not a generated mesh of GiD).
In GiD manual (FilesImportGid mesh…), it says GiD offers the possibility
to do this. However, I struggled for an hour, I was not able to do it.
Please let me know the point which describes how to do it in the manual.

For testing, I have been using a small size of .post.msh shown below.
In real problem, however, mesh size is large and it is very hard to select
elements within mouse operation.

Best regards,

HEMMI, Shigeru
ITOCHU Techno-Solutions Corporation (CTC), Japan.

########################################################################
MESH dimension 3 ElemType Hexahedra Nnode 8
Coordinates
1001 -0.91 0.0 0.0
1002 -0.9 0.0 0.0
1003 -0.7857 0.0 0.0
1004 -0.6714 0.0 0.0
1013 -0.2285 0.0 0.0
1014 -0.225 0.0 0.0
1020 -0.91 0.01 0.0
1021 -0.9 0.01 0.0
1022 -0.7857 0.01 0.0
1023 -0.6714 0.01 0.0
1032 -0.2285 0.01 0.0
1033 -0.225 0.01 0.0
1051 -0.2285 0.195 0.0
1052 -0.225 0.195 0.0
1362 -0.91 0.0 0.01
1363 -0.9 0.0 0.01
1364 -0.7857 0.0 0.01
1365 -0.6714 0.0 0.01
1374 -0.2285 0.0 0.01
1375 -0.225 0.0 0.01
1381 -0.91 0.01 0.01
1382 -0.9 0.01 0.01
1383 -0.7857 0.01 0.01
1384 -0.6714 0.01 0.01
1393 -0.2285 0.01 0.01
1394 -0.225 0.01 0.01
1412 -0.2285 0.195 0.01
1413 -0.225 0.195 0.01
end coordinates

Elements
1 1001 1002 1021 1020 1362 1363 1382 1381 1
2 1002 1003 1022 1021 1363 1364 1383 1382 1
3 1003 1004 1023 1022 1364 1365 1384 1383 1
13 1013 1014 1033 1032 1374 1375 1394 1393 2
31 1032 1033 1052 1051 1393 1394 1413 1412 2
end elements

6

It exists an special command to send the elements with a material number to
the desired layer, but it’s necessary to manually say for each material
number the layername to be sent.

This command not very common, it’s a little hidden and undocumented.

7

Thanks,

but it seems somthing misunderstood or something incorrect.
(Sorry if the cause was my English)

The “right buttons” command you wrote
“escape View Layers layername material number”
did not work for me.

On the other hand, I found a workaround:

  1. Import .post.msh and then export it as a NASTRAN format.
  2. Re start new GiD window, and then import NASTRAN file.
    GiD creates new layers named CHEXA_Pid_1 and CHEXA_Pid_2 for such a
    NASTRAN file automatically. This feature is nice and I hope Cimne to add such
    a feature in importing externally created GiD mesh file.

regards,


HEMMI, Shigeru
ITOCHU Techno-Solutions Corporation (CTC), Japan.


escolano wrote:
It exists an special command to send the elements with a material number to
the desired layer, but it’s necessary to manually say for each material
number the layername to be sent.
This command not very common, it’s a little hidden and undocumented.
From the “rigth buttons” (or the lower command line) use
escape View Layers layername material number

Note: to visualize the “rigth buttons” (hidden by default), use
Utilities-Tools-Toolbars…
Select “Right buttons” - Inside
Regards
Enrique Escolano

GiDlist mailing list
GiDlist at gid.cimne.upc.es
_http://gid.cimne.upc.es/mailman/listinfo/gidlist_

8

The correct command is:
" escape escape escape escape"
As much escapes as you need for get to initial menu and then:
" View Layers Material layer name Number of material whose entities will
be assignad to Layer "
Note: layer name have to be an existing layer.
Regards,
Adrià Melendo


----- Original Message -----
From: “HEMMI, Shigeru” shigeru.hemmi at ctc-g.co.jp
To: gidlist at gatxan.cimne.upc.edu
Sent: Thursday, August 09, 2007 2:33 AM
Subject: Re: [GiDlist] Dividing the problem into different layers according
to the different materials


Thanks,
but it seems somthing misunderstood or something incorrect.
(Sorry if the cause was my English)
The “right buttons” command you wrote
“escape View Layers layername material number”
did not work for me.
On the other hand, I found a workaround:
1. Import .post.msh and then export it as a NASTRAN format.
2. Re start new GiD window, and then import NASTRAN file.
GiD creates new layers named CHEXA_Pid_1 and CHEXA_Pid_2 for such a
NASTRAN file automatically. This feature is nice and I hope Cimne to add
such a feature in importing externally created GiD mesh file.
regards,

HEMMI, Shigeru
ITOCHU Techno-Solutions Corporation (CTC), Japan.

escolano wrote:
It exists an special command to send the elements with a material number
to the desired layer, but it’s necessary to manually say for each
material number the layername to be sent.
This command not very common, it’s a little hidden and undocumented.
From the “rigth buttons” (or the lower command line) use
escape View Layers layername material number

Note: to visualize the “rigth buttons” (hidden by default), use
Utilities-Tools-Toolbars…
Select “Right buttons” - Inside
Regards
Enrique Escolano

GiDlist mailing list
GiDlist at gid.cimne.upc.es
_http://gid.cimne.upc.es/mailman/listinfo/gidlist_

GiDlist mailing list
GiDlist at gid.cimne.upc.es
_http://gid.cimne.upc.es/mailman/listinfo/gidlist_

9

Thanks for the support.
It worked fine for me as I expected.

Best regards,

HEMMI, Shigeru
ITOCHU Techno-Solutions Corporation (CTC), Japan


Adrià Melendo wrote:

The correct command is:
" escape escape escape escape"
As much escapes as you need for get to initial menu and then:
" View Layers Material layer name Number of material whose entities
will be assignad to Layer "
Note: layer name have to be an existing layer.
Regards,
Adrià Melendo

----- Original Message ----- From: “HEMMI, Shigeru”
shigeru.hemmi at ctc-g.co.jp
To: gidlist at gatxan.cimne.upc.edu
Sent: Thursday, August 09, 2007 2:33 AM
Subject: Re: [GiDlist] Dividing the problem into different layers
according to the different materials

Thanks,
but it seems somthing misunderstood or something incorrect.
(Sorry if the cause was my English)
The “right buttons” command you wrote
“escape View Layers layername material number”
did not work for me.
On the other hand, I found a workaround:
1. Import .post.msh and then export it as a NASTRAN format.
2. Re start new GiD window, and then import NASTRAN file.
GiD creates new layers named CHEXA_Pid_1 and CHEXA_Pid_2 for such a
NASTRAN file automatically. This feature is nice and I hope Cimne to
add such a feature in importing externally created GiD mesh file.
regards,

HEMMI, Shigeru
ITOCHU Techno-Solutions Corporation (CTC), Japan.

escolano wrote:
It exists an special command to send the elements with a material
number to the desired layer, but it’s necessary to manually say for
each material number the layername to be sent.
This command not very common, it’s a little hidden and undocumented.
From the “rigth buttons” (or the lower command line) use
escape View Layers layername material number

Note: to visualize the “rigth buttons” (hidden by default), use
Utilities-Tools-Toolbars…
Select “Right buttons” - Inside
Regards
Enrique Escolano

10

We don’t want to automatically create layers for the materials of the GiD
mesh ASCII file.

Probably a good option is to enhance the “View Layers Material layername
material number” command, with an “Automatic” sub-command to automatically
create as layers as necessary, and send to this layers the entities.

Note: It’s possible to create a macro to do the same, without expect a new
GiD version with this feature.

Enrique Escolano


On Thu, 09 Aug 2007 09:33:43 +0900, HEMMI, Shigeru wrote
Thanks,
but it seems somthing misunderstood or something incorrect.
(Sorry if the cause was my English)
The “right buttons” command you wrote
“escape View Layers layername material number”
did not work for me.
On the other hand, I found a workaround:
1. Import .post.msh and then export it as a NASTRAN format.
2. Re start new GiD window, and then import NASTRAN file.
GiD creates new layers named CHEXA_Pid_1 and CHEXA_Pid_2 for such a
NASTRAN file automatically. This feature is nice and I hope Cimne to
add such a feature in importing externally created GiD mesh file.
regards,
HEMMI, Shigeru
ITOCHU Techno-Solutions Corporation (CTC), Japan.
escolano wrote:
It exists an special command to send the elements with a material number
to
the desired layer, but it’s necessary to manually say for each material
number the layername to be sent.
This command not very common, it’s a little hidden and undocumented.
From the “rigth buttons” (or the lower command line) use
escape View Layers layername material number

Note: to visualize the “rigth buttons” (hidden by default), use
Utilities-Tools-Toolbars…
Select “Right buttons” - Inside
Regards
Enrique Escolano

GiDlist mailing list
GiDlist at gid.cimne.upc.es
_http://gid.cimne.upc.es/mailman/listinfo/gidlist_

GiDlist mailing list
GiDlist at gid.cimne.upc.es
_http://gid.cimne.upc.es/mailman/listinfo/gidlist_

11

Sorry, I think I was a little bit to fast. Original Message:

Hi,

i wrote a tcl-Routine to get the number of nodes of the linear elements
in the mesh. Therefore I want to loop over all nodes:

*set var ndifnum = 0
*loop nodes
*if(*tcl(NumIfaceNodes *NodesNum) == 1)
*set var ndifnum = operation(ndifnum+1)
*end nodes

with the following tcl-Routine:

proc NumIfaceNodes { NodesNum } {
foreach elem [GiD_Info mesh elements Linear 1 end -sublist] {
set num [lindex $elem 0]
set nodes [lrange $elem 1 end-1]
foreach node $nodes {
lappend ifacenodes $node
}
}
set boolean 0
foreach node $ifacenodes {
if {$NodesNum==$node} {set boolean 1}
}
return [expr {$boolean}]
}

But it doesn’t work. I’ve tried the routine in a few different ways, but
I can’t get a variable in the bas-datei via tcl-Routine. Do you have any
idea?

Thanks in advance
Frithjof Pasenow

–
Dipl.-Ing. Frithjof Pasenow

Institute for Structural Analysis
Technical University Braunschweig
Beethovenstrasse 51
38106 Braunschweig

Tel : +49 (0)531 391-3662
Fax : +49 (0)531 391-8116
Mail : f.pasenow at tu-bs.de

www.statik.tu-braunschweig.de