-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
define_ref_peak #12
Comments
Hallo, ich habe gerade meine letzte Version hochgeladen -- ich hatte das Committen 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 notifications@github.com:
|
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! |
Do we really need
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? |
Ok, I just saw that you are calculating the deviation a little bit below that. Then of course you need the height adjustment.... |
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.
|
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
getestet.
Kannst du mir da evtl einen Tipp geben oder etwas helfen?
Danke!
The text was updated successfully, but these errors were encountered: