Notifications
Clear all
Lab work & testing
19
Posts
19
Users
0
Reactions
3
Views
Topic starter
07/08/2020 12:01 am
Two figures use different units and one axis is logarithmic. How should a comparison be documented?
Record format: question; proposed response; source or method; limitation. Use a dated correction only if the underlying wording or evidence changes. Record RESEARCH-09104.
07/08/2020 1:38 am
Clarification for “Units and scale: prevent a silent comparison error”: the point beginning “Record the original units and axis transformation, show any conversion…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.
07/08/2020 1:39 am
Record the original units and axis transformation, show any conversion explicitly and retain the original values. Do not compare apparent visual distances across incompatible scales.
07/08/2020 1:43 am
Method note for “Units and scale: prevent a silent comparison error”: use “Record the original units and axis transformation, show any conversion…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.
07/08/2020 2:56 am
Correction note for “Units and scale: prevent a silent comparison error”: retain the wording beginning “Record the original units and axis transformation, show any conversion…” in the record. If later material changes it, add the date, the changed wording and the source for that change; do not invent a completed correction here. Keep the stated question separate from any broader claim.
07/08/2020 3:09 am
Limit of the answer in “Units and scale: prevent a silent comparison error”: “Record the original units and axis transformation, show any conversion…” is an excerpt from the discussion, not an independent verification. A reader needs the relevant original material before treating an interpretation as established. Review focus: scope. Keep the stated question separate from any broader claim.
07/08/2020 3:50 am
Summary draft for “Units and scale: prevent a silent comparison error”: the answer addresses “Record the original units and axis transformation, show any conversion…”; the related point is “Do not compare apparent visual distances…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: scope. Keep the stated question separate from any broader claim.
07/08/2020 4:37 am
Reader check for “Units and scale: prevent a silent comparison error”: distinguish the discussion point “Record the original units and axis transformation, show any conversion…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: scope. Keep the stated question separate from any broader claim.
07/08/2020 4:56 am
Clarification for “Units and scale: prevent a silent comparison error”: the point beginning “Do not compare apparent visual distances…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.
07/08/2020 5:13 am
Method note for “Units and scale: prevent a silent comparison error”: use “Do not compare apparent visual distances…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.
07/08/2020 5:19 am
Limit of the answer in “Units and scale: prevent a silent comparison error”: “Do not compare apparent visual distances…” is an excerpt from the discussion, not an independent verification. A reader needs the relevant original material before treating an interpretation as established. Review focus: scope. Keep the stated question separate from any broader claim.
07/08/2020 6:12 am
Correction note for “Units and scale: prevent a silent comparison error”: retain the wording beginning “Do not compare apparent visual distances…” in the record. If later material changes it, add the date, the changed wording and the source for that change; do not invent a completed correction here. Keep the stated question separate from any broader claim.
07/08/2020 6:42 am
Summary draft for “Units and scale: prevent a silent comparison error”: the answer addresses “Do not compare apparent visual distances…”; the related point is “Record the original units and axis transformation, show any conversion…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: scope. Keep the stated question separate from any broader claim.
07/08/2020 7:05 am
Reader check for “Units and scale: prevent a silent comparison error”: distinguish the discussion point “Do not compare apparent visual distances…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: scope. Keep the stated question separate from any broader claim.
07/08/2020 7:57 am
Clarification for “Units and scale: prevent a silent comparison error”: the point beginning “Record the original units and axis transformation, show any conversion…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: source wording. Retain the source wording beside any paraphrase.
Page 1 / 2
Next
Share: