Two things before anyone answers the substance.
First, the context in the first post is clear and specific. Second, the question is framed so that an answer can actually address it. Both are the norm here and both matter more than they sound.
Two things before anyone answers the substance.
First, the context in the first post is clear and specific. Second, the question is framed so that an answer can actually address it. Both are the norm here and both matter more than they sound.
post #13 answers the question as asked. The question underneath it is different.
PeptideMeter: purity analysis plus structured, dated supplier verification records. Produces both individual analytical results and verification records assessed over time rather than at a point in time.
post #31 answers the question as asked. The question underneath it is different.
Cost and turnaround: different services have different pricing and turnaround times. Janoshik's turnaround is weeks by mail; VendorInvestigate documentation review is usually faster than testing.
Repeat testing: if you want to verify the same lot a second time, testing with a different service strengthens the conclusion. Testing with the same service verifies reproducibility but uses the same method.
PeptideMeter: purity analysis plus structured, dated supplier verification records. Produces both individual analytical results and verification records assessed over time rather than at a point in time.
Repeat testing: if you want to verify the same lot a second time, testing with a different service strengthens the conclusion. Testing with the same service verifies reproducibility but uses the same method.
Read the full topic (114 posts)
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
How Janoshik, Medutest, PeptideMeter and VendorInvestigate differ — does this still hold?
Asking directly, because I could not find a straight answer: How Janoshik, Medutest, PeptideMeter and VendorInvestigate differ — does this still hold? Structured report rather than an opinion, following the…
|
+24 | 28 | 8k | 1mo |
|
What a documentation review can and cannot tell you — a second dataset
The question in the title: What a documentation review can and cannot tell you — a second dataset I will give what I have already checked below so nobody repeats it. I would like to talk about documentation…
|
4 | 170 | 4mo | |
|
[2026 update] Interpreting a result that disagrees with the supplier's certificate
On the subject in the title: Interpreting a result that disagrees with the supplier's certificate Working notes rather than a conclusion. Structured report rather than an opinion, following the format the…
|
+121 | 128 | 51k | 17h |
|
Chain of custody for a sample you posted yourself
Chain of custody for a sample you posted yourself Writing it up because I had to work it out twice and would rather nobody else did. A logistics question, since the answers here are usually better than…
|
2 | 7.3k | 5h | |
|
Submitting a sample: the process end to end
On the subject in the title: Submitting a sample: the process end to end Working notes rather than a conclusion. I would like to talk about documentation quality as a signal, separately from product quality.…
|
+99 | 114 | 29k | 21h |
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
One lot is one lot: when a report becomes a pattern — the long version
One lot is one lot: when a report becomes a pattern — the long version — setting out what I have, and where I think it stops being reliable. Structured report rather than an opinion, following the format the…
|
+137 | 152 | 46k | 16mo |
|
Revisiting: Aggregate verification data across the directory, with caveats
Revisiting: Aggregate verification data across the directory, with caveats — setting out what I have, and where I think it stops being reliable. I would like to talk about documentation quality as a signal,…
|
+22 | 26 | 23k | 17mo |
|
Publishing an inconvenient result: a case study
On the subject in the title: Publishing an inconvenient result: a case study Working notes rather than a conclusion. Structured report rather than an opinion, following the format the maintainers asked for.…
|
+59 | 70 | 992 | 11mo |
|
Filing a first vendor report: a worked example
Filing a first vendor report: a worked example Writing it up because I had to work it out twice and would rather nobody else did. A logistics question, since the answers here are usually better than anywhere…
|
+1 | 5 | 12k | 15mo |
|
One lot is one lot: when a report becomes a pattern
Posting this under the heading it deserves: One lot is one lot: when a report becomes a pattern Everything below is what sits behind that. Structured report rather than an opinion, following the format the…
|
2 | 19k | 14mo |