You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The terminology is confusing. NONMEM is a proprietary software tool and stands for non-linear mixed effects modelling. First, it has nothing to do with data.
Please replace throughout the ReportingEngine: nonmenColumn --> datasetColumn nonmemUnit --> datasetUnit
(And yes, it is not a typo by me... it is currently written as "nonmenColumn"...)
@sfrechen do we need backward compatibility in the dictionaries? I mean: if the new column name is not found: should RE try to find the old column name?
E.g. if the "datasetUnit" column is missing: should RE look for the "nonmemUnit" column?
If yes: data dictionaries in existing RE workflows can be kept AS IS. Otherwise existing datadictionaries need to be adjusted for the new naming.
I don't have any RE workflows for R ReportingEngine :-).
But I would guess if we fix it soon... there is virtually no impact since it hasn't been used in a productive way too often.
And to reproduce old results (if there are one), one needs to use anyway the corresponding ReportingEngine version.
Thus: I would say: no backward compatibility needed.
The terminology is confusing. NONMEM is a proprietary software tool and stands for non-linear mixed effects modelling. First, it has nothing to do with data.
Please replace throughout the ReportingEngine:
nonmenColumn
-->datasetColumn
nonmemUnit
-->datasetUnit
(And yes, it is not a typo by me... it is currently written as "nonmenColumn"...)
Affected files (no warranty for completeness):
@Yuri05 @Christoph27 @AnnikaRPS
The text was updated successfully, but these errors were encountered: