define_ref_peak about peaks

[rgiessmann]

Hallo,

ich habe gerade meine letzte Version hochgeladen -- ich hatte das Committen
vergessen.

Du siehst in meinem Branch nun, wie ich es gelöst habe.

Meld dich bei Fragen!

2016-04-19 9:31 GMT+02:00 Ovicula [email protected]:

Hey

Ich bastel gerade an dem define_ref_peak-Funktion rum. Allerdings weiß ich
jetzt nicht genau, wie ich dafür sorgen kann, dass die durchschnittlichen
Peak-Höhen der 0M-traces die neuen Peak Höhen für die Ref-trace ergeben?
Und irgendwo muss dann auch noch ein Fehler sein, aber ich weiß nicht wo...

Ich hab die Funktion mit 4 traces und

ref = prog.define_reference_peak(trace_list, accepted_offset=0.25)

print("trace_list:"+str(trace_list))
print("ref:"+str(ref))

getestet.

Kannst du mir da evtl einen Tipp geben oder etwas helfen?
Danke!

—
You are receiving this because you were assigned.
Reply to this email directly or view it on GitHub
#12

[rgiessmann]

Hey,

I just uploaded my last version -- sorry, forgot to commit.

In my branch you can see how I solved this issue.

Don't hesitate to come up with follow-up questions!

[Ovicula]

Do we really need

for trace in conc_0_traces[1:]:
correct_peaks_with_factor(trace,determine_factor_numerically(conc_0_traces[0],trace))

I don't think so because the proportions of the peak sizes should stay te same even if the height is not adjusted. Since the factor determination is another error source I would prefer to not use it if not really necessary. What do you think?

[Ovicula]

Ok, I just saw that you are calculating the deviation a little bit below that. Then of course you need the height adjustment....

[rgiessmann]

Please also note that the 0M traces might have different amounts of DNA injected, so you'll need height correction, as it's not about the ratios but real peak heights! However, you're true, this introduces another error -- it would be good to check the overall deviation so you know how good the correction was.