Troubleshooting and Problems

I've noticed in the past that configuring the validator (i.e., in version 2.0) to use the SNOMED dictionary results in an increased processing time.  For a study that might have taken less than a minute to run without it, incorporating SNOMED can cause it to run for 2-3 minutes, not necessarily a bad deal when the number of records to be processed is considered.

In the latest version of the validator, the same study still takes less than a minute to run without SNOMED, but now takes over 12 hours to run with it.

Regards,

Carlo

Hi,

when i am validating define (2.0.0) using openCDSIC 1.5 then I am getting below errors. i checked <<SDTM Terminology.odm.xml>> file under ....\opencdisc\opencdisc-validator-1.5-bin\opencdisc-validator\config\data. i could not find these C-code. i am using SDTM Terminology 2014-09-26 which has those values.  othere thing only First one is for LBTESTCD/LBTEST CT others are for EGTEST/EGTESTCD but openCDISC report shows all for LBTESTCD. Please suggest how to resolve these error.

Hi,

I have strange messages when validating data from the command line with OC 2.0.1 (see below). For the last line, I think it is due to "IG.FA" being used in 2 places in the xml config files: replacing
<val:Prototype ItemGroupOID="IG.FA" KeyVariables="__OBJ"/>
with:
<val:Prototype ItemGroupOID="IG.FINDINGSABOUT" KeyVariables="__OBJ"/>
makes it disappear.

When we run OpenCDISC Community v2.0.1 on a particular study, the validation process hangs and no report is produced.  The hang has lasted as much as a half-hour before we've given up and halted the process.

Running from the command line, we see the following message generated:

"The ItemGroupDef named FA conflicts with a configuration prototype (oid: IG.FA). This shouldn't happen!"

Any suggestions what might be causing this or how to work around it?

Hi, I have check marked for Automatic Updates but did not get one for v2.01.

I don't know whether this is the right place in the forum, but there is no tab for "source code".

Using Community 2.0 - Validator.  Select SDTM and pick XPT files.  Click the "Validate" button.  New window opens and says "Starting".  Nothing happens.  Application is hung.

Launch Task Manager.  Kill Community application.  Switch to Processes view in Task Manager.

Restart Community again doing the same things while watching Processes in Task Manager.  Saw JAVA process start runing the CLI JAR file.  It only lived for 2 seconds and disappeared.

Hi ,

I am running open CDISC 1.5 for SDTM 3.1.3 validation and getting SD0063 warning: SDTM/dataset variable label mismatch for Supplemental Qualifiers dataset. Please suggest what is missing. label is matching with IG.

Please see what config-sdtm-3.1.3.xml has

Hello,

I have two part question regarding define.xml hyperlinks:

1.) Recently our company changed the IE from version 8 to version 10 and none of the links are now working for define.xml but      if I open define.xml using Firefox all links are working except the link for "Dataset". If I am in the middle of the define.xml and      try to hit the "Dataset", it doesn't work.

2.) Dose the program needs to be altered in order to use the IE v10 or is there any quick fix available.

Thanks,

Regards,

Ankur

On one study we're working on, a co-worker noticed that there were more issues showing up when OpenCDISC 2.0 was run interactively than when it was run from the command line.  Looking closely at the results, it appears that the command-line invocation of the validator did not use the controlled terminology rules with OpenCDISC IDs of CT2001, CT2002, CT2004, and CT2005.  (These were the only CT rules triggered by the data--CT2003 and CT2006 appeared in neither report.)