Determine channel role mapping

[DHowett]

FAM+VIC CH1 Unknown CH2 Unknown
0xF3: 0x80 (0b1000`0000)

FAM+HEX CH1 Unknown CH2 Unknown
0xF3: 0x80 (0b1000`0000)

FAM+HEX CH1 Reference CH2 Positive Control
0xF3: 0xA0 (0b1010`0000)

FAM+HEX CH1 Negative Control CH2 NTC
0xF3: 0xA0 (0b1010`0000)

Imputed meaning of 0xF3: channel role, perhaps bitfield.

[seaaan]

Are the second two really the same? It seems like they should be different if it really represents the channel role

On Oct 15, 2016 6:08 PM, "Dustin L. Howett" notifications@github.com wrote:

FAM+HEX CH1 Unknown CH2 Unknown 0xF3: 0x80 (0b1000`0000)

FAM+HEX CH1 Reference CH2 Positive Control 0xF3: 0xA0 (0b1010`0000)

FAM+HEX CH1 Negative Control CH2 NTC 0xF3: 0xA0 (0b1010`0000)

Imputed meaning of 0xF3: channel role, perhaps bitfield.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/DHowett/qlbreader/issues/6, or mute the thread https://github.com/notifications/unsubscribe-auth/AKDNdSGJv92OrwtuOWumLxxaDbknyZrEks5q0XkMgaJpZM4KX29Z .

[DHowett]

Good question. This could actually be represented in the qlr and qlp sidecar files.

We may need to parse those as well; they all seem to share the same basic layout.

[DHowett]

@seaaan Is the qlp the project file? It looks like it contains the column names/channel mappings for the wells:

fam hex different types.qlp
A01
Absolute Quantification
Not Used
Not Used
A02
Absolute Quantification
Not Used
Not Used
...
G07
Absolute Quantification
Reference
FAM REF
Positive Control
HEX POS
...
H07
Absolute Quantification
Negative Control
FAM NEG
NTC
HEX NTC

(interspersed with binary data)

[seaaan]

Yep, it's the project file. I didn't look that closely, but I noticed that there are a lot of null bytes interspersed with text. A plate/project can have up to 96 samples, but most of these projects (e.g. fam hex different types.qlp) only had a few samples, so I suspect the null bytes might be placeholders for all the unused samples/wells.

On Sun, Oct 16, 2016 at 9:38 PM, Dustin L. Howett notifications@github.com wrote:

@seaaan https://github.com/seaaan Is the qlp the project file? It looks like it contains the column names/channel mappings for the wells:

fam hex different types.qlp A01 Absolute Quantification Not Used Not Used A02 Absolute Quantification Not Used Not Used ... G07 Absolute Quantification Reference FAM REF Positive Control HEX POS ... H07 Absolute Quantification Negative Control FAM NEG NTC HEX NTC

(interspersed with binary data)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/DHowett/qlbreader/issues/6#issuecomment-254111140, or mute the thread https://github.com/notifications/unsubscribe-auth/AKDNdZ0B0RGhr4_fzH370h9Vq7kU3cttks5q0vvjgaJpZM4KX29Z .

[DHowett]

Since qlbreader now parses entire directories, we could include qlp/qlr reading and emit another sidecar data file into the output directory. Leaving open for now.