Troubleshooting and Problems

Hi,

I'm getting the following message while runing openCDISC CLI to generate the define.xml on Solaris

I'm not sure where to start with troubleshooting the problem.

 Any help is greatly appreciated.

Thank you.

Vanessa

Deleted

No matter what value I have for RSSTRESC, it is reported that the value isn't in the codelist.  I think that this is because the codelist isn't in SDTM Terminology Fixed.xml.  Please confirm.

Rule violation SD1011 is triggered when durations are formatted according to ISO 8601 uncertainty rules.  The SDTMIG instructes to follow ISO 8601 uncertainty formatting when representing a durations such as "between 24 weeks and 26 weeks".  This example duration would be formatted as " P24W/P26W" according to ISO 8601, but OpenCDISC does not

I have been getting Errors on duplicate values checks, but I do not see any duplicate records in the dataset.

Particulary, SD1201 indicates Error for records where USUBJID and AEDECOD are duplicate but AESTDTC has different dates. 

SD0005     Duplicate value for AESEQ variable 

SD1201 Duplicate USUBJID/AEDECOD/AESTDTC 

SD0083 Duplicate USUBJID 

Hi,

There is a bug in the configuration file: I get a message stating: "Value for QSTEST not found in (KPS Scale TEST) CT codelist", while the value in question is correct. When looking into the config file, I found this:

Hi, From the changelog, I saw that there was a new version (1.1) of the SDTM configuration released on August 19. Is there a way to see in the XML which version of the configuration I am looking at? I have the stock original configuration downloaded with the OpenCDISC 1.4 release last spring, and also the configuration I just downloaded from here: http://svn.opencdisc.org/validator/trunk/config/ however, both say version 1.0 in the header (line 24). Thank you

When we verify our XPT files (with or without define.xml) we get a different OpenCDISC.xls file when we run it from the command prompt (CLI usage) then when we use the Graphical User Interface (GUI).

Further investigation learns us that is has to do with split domains.
The GUI is ok: it looks like it concatenates the LB01 and LB02 split domains and then executed the checks
The CLI gives us errors like LB01 and LB02 are unrecognized domains. And in CO domain it says that RDOMAIN=LB is invalid. Same for SUPPLB01, SUPPLB02. And that domain LB is missing.

We upgraded to version 1.4 and found that the feature "source format : Delimited" \t is now not working. Is there a workaround or a planned fix to re-enable this feature?

1. There are inconsistencies with the following variable label checking:

CODY (Domain CO): SD0063   SDTM/dataset variable label mismatch.

There appears to be a spelling mistake in the configuration file.

2. If length is less than 20 for ARMCD there appears the following  message:

SD1058 Non-recommended variable length

This message should appear if the variiable ARMCD (Domain: DM) is longer than 20 characters,  not if it is below.