ID Synonym Error with npc
I just got the following errors:
It is forbidden to use a synonym for ID in the $INPUT record. at constructor tool::npc::new (defined at /opt/PsN/4.8.0/PsN_4_8_0/tool/npc.pm line 5587) line 2443.
It is forbidden to use a synonym for MDV in the $INPUT record. at constructor tool::npc::new (defined at /opt/PsN/4.8.0/PsN_4_8_0/tool/npc.pm line 5587) line 2443.
Can PsN detect what the ID and MDV columns are and use those throughout?
Yes. PsN uses the reserved names for the ID and MDV columns. In your model I guess you had ID=SMTH1 and MDV=SMTH2 or similar, which the vpc does not support.
You’re right, I was aliasing both similar to what you indicated. I am curious if vpc could detect what those mappings are and use them automatically rather than require a model rewrite.
Just out of curiosity: what is the benefit of aliasing these column labels?
When working with other data management (outside of NONMEM and PsN), it simplifies the mapping for me. Data that I receive often uses a column name "ID" for other purposes. I typically use USUBJIDN to map to the SDTM field USUBJID, and having it come out that way simplifies that mapping.
It's a soft benefit.