Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 18 total)

Method note for “Lume questions: why does my lume fade so quickly, and how should I compare it?”: use “A bright initial glow followed by a steep drop…” 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.

Method note for “Model comparison: dive bezel action and alignment, how to compare fairly”: use “Separate three properties: click count (60 or 120 positions), feel (how…” 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.

Clarification for “QC checklist: prioritise observable faults over pixel hunting”: the point beginning “Start with function, legibility, assembly and…” 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.

Correction note for “Disputed observation: is this dial colour shift real or just lighting?”: retain the wording beginning “The difficulty is that phone cameras adjust white balance automatically,…” 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.

Case 35 — Lume comparison: keep exposure and charging conditions consistent

Summary draft for “Lume comparison: keep exposure and charging conditions consistent”: the answer addresses “Treat the comparison…”; the related point is “Repeat with equal light source, charging duration, elapsed time and camera…”. 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.

Case 15 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained

Correction to a common shortcut: don't measure lug width on an existing strap. Leather and rubber straps compress or swell, and some are made slightly undersized on purpose. Always measure between the lugs themselves, with the strap removed if possible.

Add lug-to-lug, thickness and lug width as separate rows. Diameter alone tells you little about wearability. Two cases 2mm apart in diameter can be within 1mm of each other lug to lug, and that number decides whether the watch overhangs a small wrist. Also give the source for each figure: manufacturer sheet, caliper measurement, or catalogue listing.

Case 40 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem · source wording exercise

Limit of the answer in “Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem”: “Fit often improves by moving one link from the 6 o'clock…” 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: source wording. Retain the source wording beside any paraphrase.

Case 15 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?

I ran a watch on a basic timegrapher and got +6 s/d, 245 degrees amplitude and 0.8 ms beat error, dial up, about an hour after winding. Is this good, bad or normal? I don't want to send it for service on a single reading.

Exercise RWF-15901/15: address this question within its stated limits.

Correction note for “QC photographs: perspective or a genuinely tilted index?”: retain the wording beginning “Request a level straight-on image with the hands…” 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.

Case 40 — Comparing dial colour under different lighting · source wording exercise

Summary draft for “Comparing dial colour under different lighting”: the answer addresses “Compare controlled images where available and avoid calling a…”; the related point is “State the lighting and…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: source wording. Retain the source wording beside any paraphrase.

Reader check for “Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?”: distinguish the discussion point “Start with how you…” 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.

Case 12 — Case finishing: distinguish a reflection from a surface mark

Method note for “Case finishing: distinguish a reflection from a surface mark”: use “Ask for photographs with the light moved and…” 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.

Clarification for “Movement identification: the limits of a rotor photograph”: the point beginning “Describe visible bridge shapes and markings separately…” 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.

Clarification for “Forum comparison archive: link the evidence and the correction”: the point beginning “Add a dated correction near the original conclusion…” 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.

Viewing 15 posts - 1 through 15 (of 18 total)