Use correct turbine names in plots

[aclerc]

I was just discussing this with @paulf81 and he encouraged me to add an issue :)
Please can any plots showing turbine names use the correct turbine names. For example in the farm shown below the turbines are actually named T02, T04, T05, etc. but T00, T01, T02, etc. is displayed. If the correct turbine names are not available using the name "T00" will probably never be right, so if you have to fall back to generated names I would at start with T01

[aclerc]

sorry looks like my screenshot is too fuzzy to read but @paulf81 can add the original image if needed!

[misi9170]

Hi @aclerc, thanks for bringing this up! I think the functionality you are after is actually available in FLASC. For example, take a look at this function, where you can pass layout_plotting_dict={"turbine_names": ["T02", "T04", "T05",...]}. There are also other layout plotting functions that you can take a look at there, as well as additional flexibility with how layouts are plotted.

However, this functionality is a bit hidden on FLASC. This ties in well with discussion #789, and is probably a point in favor of moving the functionality over to FLORIS.

[rafmudaf]

@aclerc can you share more information so that we can recreate this issue? A simplified analysis script including the functions you used for plotting would be helpful. Also, which version of FLORIS are you using?

[paulf81]

hi all, just to jump in, I think this is more enhancement than bug. Typically turbines in a farm have a name/identifier. In FLORIS and FLASC we use 0-index for each turbine, and so plotting functions typically label turbines according to that system. @misi9170 you're right this currently more a FLASC issue, but with the move to FLORIS, I think the main idea in this issue is that any plot that labels specific turbines, should have the option to use provided names in place of 0-index. A secondary point, is that if we label turbines 0-index we should probably not add the T-prefix, is that is usually how a named turbine would be specified

[paulf81]

Believe this issue is resolved by #805