Page 1 of 1

[GiDlist] Precision in Export Mesh File

Posted: Wed Aug 06, 2003 8:42 pm
by Oleg Zarechnyy
Hello,

I have the following problem:

When I do Utilities\List\Points for definition of coordinates some
point or node it gives me more accurate value then I take this
coordinates from file which is produced by Files\Import/Export\Write
Mesh procedure. Can I change the precision of coordinates in this
file?
Thanks.


Oleg mailto:oleg2205 at mail.ru

[GiDlist] (no subject)

Posted: Thu Aug 07, 2003 8:52 am
by Adisorn Owatsiriwong
Dear Gid team,

Is the order of command *set, *add is important to gid? Please see this code.

*#--- Nodal Forces
*set cond Point-forces *nodes ---Line 1
*add cond Line-forces *nodes ---Line 2
*add cond Surface-forces *nodes ---Line 3
*if(condnumentities(int)0)
*loop nodes *onlyincond
*format "%d %.3f %.3f %.3f"
*nodesnum *cond(1,real) *cond(2,real) *cond(3,real) ---Line 4
*end nodes
*endif


The problem occurs if I swap the line no. 1 and 3 to be

*set cond Surface-forces *nodes ---Line 1
*add cond Line-forces *nodes ---Line 2
*add cond Point-forces *nodes ---Line 3

The command on line 4 will print nothing unless I apply the surface condition. But it counts the right value of entities if we look in *condnumentities variable.

My questions are:

1. If these command work like a 'union' operation, why do their order be important? If not so, how we judge which statement should be defined as *set.

2. How does gid judge which condition should be the criteria of *onlyincond ('union' or 'intersect'), is it depend on the oder of those statement?

3. What happens if I use more than one *set command to setup the condition. Will it be only the last condition that gid accept? And how can I apply those command in the 'intersect' sense.


Thank you in advanced.

Best regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listas.cimne.upc.edu/pipermail/gidlist/attachments/20030807/f74c911f/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: flagshyp.cnd
Type: application/octet-stream
Size: 1952 bytes
Desc: not available
Url : http://listas.cimne.upc.edu/pipermail/gidlist/attachments/20030807/f74c911f/attachment.obj

[GiDlist] Precision in Export Mesh File

Posted: Fri Aug 08, 2003 5:40 pm
by Ramon Ribó
Hello,

If you define a customized .bas file, you can define there
the precision that you need by using *format or similar.

Check at Help-Customization help for details.

Regards,

--
Compass Ing. y Sistemas Dr. Ramon Ribo
http://www.compassis.com ramsan at compassis.com
c/ Manuel Girona, 61 bajos tel. +34 93 204 10 82
08034 Barcelona, Spain fax. +34 93 204 19 09

-----Mensaje original-----
De: gidlist-admin at gatxan.cimne.upc.es
[mailto:gidlist-admin at gatxan.cimne.upc.es] En nombre de Oleg Zarechnyy
Enviado el: miƩrcoles, 06 de agosto de 2003 21:41
Para: gidlist at gatxan.cimne.upc.es
Asunto: [GiDlist] Precision in Export Mesh File


Hello,

I have the following problem:

When I do Utilities\List\Points for definition of coordinates some point
or node it gives me more accurate value then I take this coordinates
from file which is produced by Files\Import/Export\Write Mesh procedure.
Can I change the precision of coordinates in this file? Thanks.


Oleg mailto:oleg2205 at mail.ru


_______________________________________________
GiDlist mailing list
GiDlist at gid.cimne.upc.es
http://gid.cimne.upc.es/mailman/listinfo/gidlist

[GiDlist] (no subject)

Posted: Mon Aug 11, 2003 2:54 pm
by Enrique Escolano
This command :
*set cond Point-forces *nodes
*add cond Line-forces *nodes
creates internally a list of nodes with the condition Point-forces or the condition Line-forces.
If two conditions are applied over the same node, if you use *canrepeat, then, the node is listed two times (one for each value),
but if not use canrepeat, the last condition overwrite the first condition.

Note: If you use a field *cond(3,real), must be sured that the 3? field exists for Point-forces, and also for Line-forces
(is best to use field names instead field numbers: for example, instead *cond(3,real), use *cond(Pressure-Z,real) )

If you use *set cond, then the previous *set/add are reset.


Regards

Enrique Escolano
----- Original Message -----
From: Adisorn Owatsiriwong
To: GiD
Sent: Thursday, August 07, 2003 9:50 AM
Subject: [GiDlist] (no subject)


Dear Gid team,

Is the order of command *set, *add is important to gid? Please see this code.

*#--- Nodal Forces
*set cond Point-forces *nodes ---Line 1
*add cond Line-forces *nodes ---Line 2
*add cond Surface-forces *nodes ---Line 3
*if(condnumentities(int)0)
*loop nodes *onlyincond
*format "%d %.3f %.3f %.3f"
*nodesnum *cond(1,real) *cond(2,real) *cond(3,real) ---Line 4
*end nodes
*endif


The problem occurs if I swap the line no. 1 and 3 to be

*set cond Surface-forces *nodes ---Line 1
*add cond Line-forces *nodes ---Line 2
*add cond Point-forces *nodes ---Line 3

The command on line 4 will print nothing unless I apply the surface condition. But it counts the right value of entities if we look in *condnumentities variable.

My questions are:

1. If these command work like a 'union' operation, why do their order be important? If not so, how we judge which statement should be defined as *set.

2. How does gid judge which condition should be the criteria of *onlyincond ('union' or 'intersect'), is it depend on the oder of those statement?

3. What happens if I use more than one *set command to setup the condition. Will it be only the last condition that gid accept? And how can I apply those command in the 'intersect' sense.


Thank you in advanced.

Best regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listas.cimne.upc.edu/pipermail/gidlist/attachments/20030811/1b0e63a9/attachment.htm

[GiDlist] Precision in Export Mesh File

Posted: Wed Sep 03, 2003 10:54 am
by Enrique Escolano
At this moment the precision of the exported mesh is the standard C output
(6 significant digits)
It is possible to write a simple *.bas template, to export the mesh with a
user specified format.

For future versions, this output precision must be a user format preference.

Regards
Enrique Escolano

----- Original Message -----
From: "Oleg Zarechnyy" oleg2205 at mail.ru
To: gidlist at gatxan.cimne.upc.es
Sent: Wednesday, August 06, 2003 9:40 PM
Subject: [GiDlist] Precision in Export Mesh File


Hello,

I have the following problem:

When I do Utilities\List\Points for definition of coordinates some
point or node it gives me more accurate value then I take this
coordinates from file which is produced by Files\Import/Export\Write
Mesh procedure. Can I change the precision of coordinates in this
file?
Thanks.


Oleg mailto:oleg2205 at mail.ru


_______________________________________________
GiDlist mailing list
GiDlist at gid.cimne.upc.es
http://gid.cimne.upc.es/mailman/listinfo/gidlist