open TELEMAC-MASCARET The mathematically superior suite of solvers

Hi,

I'm using the new BK build (3.11.9). When I try to save my mesh to *.xyz I now get the message:

"Expecting current attribute to be NUMERIC; it is not"

and fails to save to file. This worked in previous editions and I'm using an older mesh which it worked before prior to this release. Is there a new function or a workaround for this?

It's a simple 2D mesh prior to any modelling (i.e. no time steps etc.)

Thanks!

Weird... can you create a small mesh and attach it to this post? And/or copy the mesh file's header...

Sorry about this!
Alan

I created a new trial mesh and tried the same. I got the same error message.

Ok... can you please tell me which file menu you are using and/or take a screen snapshot of your workspace

Select object > File > Save Copy As > *.xyz

(aforementioned 0kb was a memory issue on my side)

I should have been more clear; I was wondering how you created your mesh. I'm guessing you created points and then triangulated it?

Not to worry; I now see what is happening.

Your mesh has 2 attributes; the first is "NodeType" and the second is "Density". Did you try to save the "NodeType" as an *.xyz file or the "Density"? Likely "Density" will work and "NodeType" may not currently work because it would need to be converted to a numeric type internally (it is a "oneof" type). I will dig around in the code to see what is going on more precisely in this case to confirm. However, I can't look any time soon. So, please check which attribute is the currently selected attribute and let me know...

Kindly,
Alan

Your mesh loaded twice; and displaying each of your two attributes...

Apologies. Yes, I created a boundary and triangulated using the T3 Mesh Generator.

What's puzzling me is my old meshes, which saved easily as *.xyz previously, now can't. I'm sure they're NodeType. Is there a way around this? e.g. a type conversion etc?

I usually do it to acquire the node ID and attributes.

I have been doing many, many deep internal things related to attributes. Now, the effect of my changes are starting to show up. I like this because now it is very clear for me what is going on.

In your case, since the attribute is a "oneof", there are 2 possible things to write into an *.xyz file. One is the category, such as "black" and the other is the value, such as 12. In the case of the *.xyz file the category value does not make sense, I suppose. But for other file types a decision will need to be made about what should be written out. I will need to handle them on a case-by-case basis.

I will look at the code that writes out the *.xyz data and I will write out the value (e.g. 12) in order to let the old behaviour stay...

I just tried saving as a *.pt2 file; a conversion from "oneof" to "double" seems to have occurred... however, it looks like some testing is also needed in this area because the values do not look correct! sigh... testers are always very much appreciated

Sorry about this; I will get these small fixes completed and included in the next Blue Kenue alpha...

Alan

Found the fault for saving to *.xyz

For those who like to know details; the fault is due to the co-ordinate system validation. In this particular mesh, the co-ordinate system is "Cartesian" with an unknown ellipsoid...

Will try investigating the *.pt2 fault now...

Kindly,
Alan