Add PM tag to @RG header

[keiranmraine]

Hi,

As PL is a restricted list could PM, 'Platform Model', be added to the RG header definition? This would be an unrestricted text field allowing for more detailed information about the machine generating the data.

Regards,
Keiran

[tfenne]

I think this is a good idea. For the longest time we've all been writing PL:illumina for the various Illumina instruments. It's likely that at least with the new chemistry on the NextSeq that we'll want to be able to identify NextSeq 2-color chemistry data vs. SBS 4-color. And with so many tools relying on PL I'm hesitant to change the value there.

-t

On Jan 29, 2014, at 3:46 AM, Keiran Raine notifications@github.com wrote:

Hi,

As PL is a restricted list could PM, 'Platform Model', be added to the RG header definition? This would be an unrestricted text field allowing for more detailed information about the machine generating the data.

Regards,
Keiran

—
Reply to this email directly or view it on GitHub.

[keiranmraine]

Any chance this will happen? I notice that there has been a new spec version since this request was created.

[jmarshall]

Since this tag was suggested, there's been an optional alignment aux tag added and a small error corrected. So there hasn't really been a whole new spec version released; it's just that now that the infrastructure is in order, it's very easy to regenerate the PDFs on the website so we do so after each little commit.

Would you like to propose some text describing PM, suitable for the table in §1.3?

[keiranmraine]

Thanks for the clarification. How about (inserted between PL and PU):

Platform Model: more detailed description of platform, e.g. 'HiSeq 2500'. Field is not controlled, however appropriate PL should be specified when using this tag.

[tfenne]

Wouldn't that be "Platform Model" not Unit?
-t

On Apr 2, 2014, at 5:59 AM, Keiran Raine notifications@github.com wrote:

Thanks for the clarification. How about (inserted between PL and PU):

Platform Unit: more detailed description of platform, e.g. 'HiSeq 2500'. Field is not controlled, however appropriate PL should be specified when using this tag.

—
Reply to this email directly or view it on GitHub.

[keiranmraine]

Sorry yes, correcting now