Welcome, Guest
Username: Password: Remember me

TOPIC: Bug with velocity layer

Bug with velocity layer 6 years 11 months ago #28223

  • riadh
  • riadh's Avatar
Hello all

I remarked that BK modifies the name of the velocity field when we copy the file (file -> save copy as) or when we close the file and reload it. The name of the fild which was VELOCITY UV becomes VELOCITY UV UV (see figure).

With this new name, Telemac does not take into account the velocity field when we use this file as a restart file.
--> to expert users, how to overcome such issue without reinterpolating the fild
--> to developpers, is it possible to fix this bug


with my best regards

Riadh
Attachments:
The administrator has disabled public write access.

Bug with velocity layer 6 years 11 months ago #28224

  • c.coulet
  • c.coulet's Avatar
  • OFFLINE
  • Moderator
  • Posts: 3722
  • Thank you received: 1031
Hi Riadh
This is due to the fact that BK automatically recognize vector fields...
But It doesn't decompose those vector fields automatically when you save a selafin file...

The solution to overcome this problem is to manually decompose the vector field with the calculator. You could extract X and Y components and map them on the variable VELOCITY U and VELOCITY V...

Regards
Christophe
The administrator has disabled public write access.
The following user(s) said Thank You: riadh

Bug with velocity layer 6 years 11 months ago #28225

  • riadh
  • riadh's Avatar
Hello Christophe

Thank you for your reply.
This is what I'm doing at each time, but this is really cumbersome and boring to do each time.
The problem is that after the extraction of X and Y components and then their remapping, if you change something, let's say on the bottom layer and then save, BK will again change the name of the velocity layer, which is not normal (in my opinion).

kind regards

Riadh
The administrator has disabled public write access.
Moderators: Serrer, a.barton

The open TELEMAC-MASCARET template for Joomla!2.5, the HTML 4 version.