mapping all old attributes to new file

[krober10nd]

• if new mesh doesn't contain blank fort.13 nodal attributes, map_mesh_properties won't map it back over
• this enables all old attributes to be mapped regardless if the new mesh has blank default values or not
• probably should do this also for the fort.24?

[WPringle]

I don't quite understand this. What is a blank nodal attribute? The numofnodes may be different between old and new mesh right?

[krober10nd]

If the new mesh that you want the nodal attributes on from an old mesh does not have default values for these nodal attributes, nothing will be migrated.

On Sun, 28 Feb 2021 at 4:35 PM William Pringle notifications@github.com wrote:

I don't quite understand this. What is a blank nodal attribute? The numofnodes may be different between old and new mesh right?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/CHLNDDEV/OceanMesh2D/pull/194#issuecomment-787509073, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEOBZ7DHC23NUG6KL76RVI3TBKLIZANCNFSM4YJ5HNHQ .

-- Keith Jared Roberts (krober@usp.br) Postdoctoral Research Fellow Escola Politécnica, Universidade de São Paulo keithroberts.site

[WPringle]

I see, but numofnodes should be updated to length(ind) still.

And in case of you pass 'ind' then new mesh is equal to the old mesh right?

[WPringle]

 obj.f13 = m_old.f13; 
 obj.f13.NumOfNodes = m_old.f13.NumOfNodes; 
 obj.f13.NumOfNodes = m_old.f13.nAttr; 

should be something like this:

 obj.f13 = m_old.f13; 
 obj.f13.NumOfNodes = length(ind);  

[krober10nd]

I didn’t have any problems with this. Will have to see later when I have time.

I rather have a function to set default attributes for a nodal attribute.

And then leave the migration the way it was