-
|
This is a technical question. I am inspecting the internal functions inside After investigating I spotted that the problem is indeed in at this point my datasets look like these, which for me makes sense. it is just the current interval row computed (with two keep_columns for the interval: The problem is indeed with the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
I think I found the problem. My original dataset presented attributes (labels) associated to the column names of my datasets, which where included in the keep_columns of my custom intervals. This did not bring any warning nor problem during the use of A potential end-solution will be to prevent the presence of any formatting at this point by: But of course I guess that a better solution would be to either run this action right in all |
Beta Was this translation helpful? Give feedback.
I think I found the problem. My original dataset presented attributes (labels) associated to the column names of my datasets, which where included in the keep_columns of my custom intervals. This did not bring any warning nor problem during the use of
PKNCAdata(), but at this point inpk.nca()/pk.nca.intervals()it will make incompatible thecbindaction...A potential end-solution will be to prevent the presence of any formatting at this point by:
But of course I guess that a better solution would be to either run this action right in all
PKNCAdataobjects or introduce a warnin…