Troubleshooting and Problems

Hello, I am ketan and studying Master of Science in Computer science at Lamar University Texas, USA. I am very enthusiastic to contribute in to the Pinnacle Community, and for that i am working on source code of the application since last  1 months.

I Downloaded Pinnacle21 Community Source code from the  https://bitbucket.org/opencdisc/  and imported it in to the Eclipse, but I got below Error:

Hi Pinnacle Team,

When I use the CLI with the newest Pinnacle 21 Validator the old Software Version 2.1.2 will still be displayed in the Excel file (see example below).

Configuration: /.../pinnacle21-community-2.2.0/components/config/SDTM 3.2.xml

Define.xml: Not provided

Generated: 2016-09-30T13:35:42

Software Version: 2.1.2

Does the CLI version realy use an older version or is it only a display error?

Thank you in advance,

Matthias

Hello,

I'm not sure if this has already been reported, but just in case it hasn't...

I have just ran two reports using the Pinnacle 21 Community v2.2.0 Validator, one creating Excel output, the other CSV output but both using exactly the same XPT files and Define.XML.

In the CSV report I appear to be missing values in the NAME and VALUE columns but only for the Define.XML related issues - see screenshots for details.

Kind regards

Steve

It appears there may be an error in the SEND Config file.  Up until Pinnacle21 Community version 2.1.2, the dataset variable types seemed to match the SENDIG.

Now they appear to no longer be in alignment.  This is returning false errors I believe.  I noticed this case in the LB Domain, where the dataset type according to SENDIG is Num or numeric for LBORNRLO and LBORNRHI.  Our LB.xpt file contains this information at the metadata level, but the validator returns error SE0055/FDAN032.  Prior versions had this type as float.

I am getting warning DD0059 with these values

DefineDescription, Dataset, StandardDescription

Chloride, IT.LB.LBORRES.CL, Clinical Observations

It appears that the LBTESTCD CL is being confused with the CL domain dataset?

Here is the ItemDef

      <ItemDef OID="IT.LB.LBORRES.CL" Name="CL" DataType="integer" Length="3" SASFieldName="CL">

        <Description>

          <TranslatedText xml:lang="en">Chloride</TranslatedText>

        </Description>

CL is published controlled terminology

DD0059 is reporting warnings on dataset labels in define.xml that are not incorrect.  It appears that you do not have the dataset labels from the SEND IG entirely correct.

(1) POOLDEF

Here are the values from the warning:  Pooled Definition, IG.POOLDEF, Pool Definition

The SENDIG 3.0 lists the POOLDEF label as "Pooled Definition" (not Pool Definition) on page 239:

pooldef.xpt, Pooled Definition - Relationship Datasets. One record per subject per pool, Tabulation.

(2) PP

We're working on producing a define.xml from from a spec spreadsheet in Excel, using the Pinnacle21 system. We're noticing that for value-level variables, the where clause will be duplicated if the same text is used to qualify two or more variables. In the attached example, DRVMTH and one other variable are both qualified by PARAMCD, which is normal, but the where-clause gets repeated. It is worth noting that we have checked that the WhereClause ID is definitely distinct.

I've verified this using a few versions of OpenCDISC and Pinncle21 versions.

The newest version appears to be using USUBJID, SUB:SITEID rather than USUBJID, SUBJID when cross checking within a SEND dataset.  This is resulting in ERRORS in every domain except trial design and DM.  This bug was not present in 2.1.1.

Hi,

I'm validating with the latest version (2.1.2) and get the warning "Missing FWENDY variable, when FWENDTC variable is present" for my FW dataset.  While I don't have the FWENDY column and do have the FWENDTC column, I don't have the FWDY column in the dataset.  I think without the FWDY present, having the FWENDY wouldn't make sense and this rule should not report.

Thanks!