Closed achubaty closed 6 years ago
perhaps using unique()
in the slicer module...
THere should only be one tab for each polygon. If unique does that, then yes. But, it has to maintain the correct data. I feel that it was dealt with during the calculation stages (largePatchesFn etc.), but apparently not. My hunch is that the calculations must be done there and that unique
in the slicer module won't give the correct number. Please confirm.
I think unique
solves this. Testing now.
for some reporting polygons, only one or two tabs are duplicated, but things escalate quickly in some cases:
also, the hists appear for the first tab only and not for any subsequent tabs.