[MOAB-dev] [Fathom] Why can't mbsize print dense tags?

[Jason Kraftcheck]

On 11/16/2010 03:06 PM, Iulian Grindeanu wrote:
> So, in a little experiment, when I used a dense tag only for vertices,
> the vtk file contains a SCALARS section just for vertices (even though I
> have elements in the model). If a just set the tag value for one triangle
> in the model, a new "SCALARS" section appears in the vtk file, for all
> "CELLS", including edges, and all triangles. 

As you probably observed while reading the VTK file, there is no way to
store attribute data in a non-dense format.  The behavior you describe above
is dictated by the file format, and has nothing to do with what MOAB may or
may not store.

> I am surprised that the
> value shown for edges is 0 (not the default), but for the triangles it is
> -1 (the default one).
> 

That is a bug.

> It is true that the vtk file is not our format of choice.
> 
> Iulian ----- Original Message -----
>> Hello, So if a dense tag is defined, is this meaning that all entity
>> handles in the database have a value for that tag? (so , all vertices,
>> all elements, all sets?) 

If a tag has a default value it is defined for all entities.

If a tag is dense, then it may be defined for more entities than it was
explicitly set on.  Which entities those are depends on MOAB's internal data
representation.

- jaosn


>> 
>> ----- Original Message -----
>>> Since dense tags have a default value, it would be difficult to tell 
>>> whether a tag was actually set on the entity or if it was just
>>> returning the default value. If there were a lot of tags on a mesh,
>>> that output would be pretty large.
>>> 
>>> If you'd like to implement an option to mbsize that prints dense 
>>> tags too, that would be fine with me.
>>> 
>>> - tim
>>> 
>>> On 11/16/2010 12:37 PM, Robert Smith wrote:
>>>> Mbsize -ll will print all sparse tags on an entity. It ends up 
>>>> using Core::print() to do this.
>>>> 
>>>> Is there a reason only sparse tags are printed? All tags are 
>>>> retrieved but all but sparse are ignored. Is it an efficiency
>>>> issue?
>>>> 
>>>> Printing both types would make debugging somewhat easier. And 
>>>> mbsize would be showing ALL data in the file now.
>>>> 
>>>> --Bob _______________________________________________ Fathom
>>>> mailing list Fathom at lists.mcs.anl.gov 
>>>> https://lists.mcs.anl.gov/mailman/listinfo/fathom
>>>> 
>>> 
>>> -- ================================================================ 
>>> "You will keep in perfect peace him whose mind is steadfast, because
>>> he trusts in you." Isaiah 26:3
>>> 
>>> Tim Tautges Argonne National Laboratory (tautges at mcs.anl.gov)
>>> (telecommuting from UW-Madison) phone: (608) 263-8485 1500
>>> Engineering Dr. fax: (608) 263-4499 Madison, WI 53706
>>> 
>>> _______________________________________________ Fathom mailing list 
>>> Fathom at lists.mcs.anl.gov 
>>> https://lists.mcs.anl.gov/mailman/listinfo/fathom
>> _______________________________________________ Fathom mailing list 
>> Fathom at lists.mcs.anl.gov 
>> https://lists.mcs.anl.gov/mailman/listinfo/fathom
> _______________________________________________ Fathom mailing list 
> Fathom at lists.mcs.anl.gov 
> https://lists.mcs.anl.gov/mailman/listinfo/fathom


-- 
"A foolish consistency is the hobgoblin of little minds" - Ralph Waldo Emerson