Originally created by: danielwe...@gmail.com
Originally owned by: danielwe...@gmail.com
Future milestone... just some thoughts for now.
- One measurement ^= record in <chromatogram>
- <chromatogram> is populated automatically, but most fields are empty
We have projects consisting of different experiments consisting of different chromatograms.
<project> - <experiment>
1 : n (m:n?)
<experiment> - <chromatogram>
1 : n
Grouping data into experiments can sometimes be aided by directory structure (based on date, not experiment) or by parsing sequence files. Still, manual changes will always be necessary.
User has to add metadata per experiment:
- Short title
- Description
- stable isotope experiment? handle differently
- define experiment specific groups "Ctrl" "Condition A" "Condition B"
??that are linked to global groups "Control" "Treatment" "..."??
User has to add metadata per sample:
- Measurement quality? Crappy / Usable
- Type QA / blank / alkane / ... -> do not process raw data
"real" sample -> do processing
- Assign group (as defined above)
The interface might become rather complex...
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: danielwe...@gmail.com
Always associate alkane measurement with experiment for (future) automated calibration , ...
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: jlin...@gmail.com
i hope the survival thing is tough but fun buddy. attached is a mockup where i combined the select chromatogram step with the sample to group association assignment. let's talk when you are back to cushioned chairs.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: danielwe...@gmail.com
Oh it was fun :). Back to civilization now.
Looking forward to see that form. Let's talk this week.