Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 23 total)
ClaspCheck 01846Participant

Case 10 — Forum comparison archive: link the evidence and the correction

A comparison has been corrected after a new photograph arrived. How should the original thread remain useful?

Exercise RWF-28682/10: address this question within its stated limits.

ClaspCheck 01846Participant

Case 13 — Lug-to-lug and end-link overhang in wrist photographs

Summary draft for “Lug-to-lug and end-link overhang in wrist photographs”: the answer addresses “Record lug-to-lug and the effective span…”; the related point is “Use a similar camera distance and neutral wrist position; photographs support…”. 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.

ClaspCheck 01846Participant

Case 25 — Maintenance question: how do I tell if an automatic actually needs service?

Clarifying question first: do you have a baseline? If you've never recorded the watch's rate or power reserve, 'drifting' is hard to judge. Start a simple log now with daily offset against a reference time for a week, and the hours it runs from full wind. Once you have that, later changes mean something.

ClaspCheck 01846Participant

Method note for “Lug-to-lug and end-link overhang in wrist photographs”: use “Record lug-to-lug and the effective span…” 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.

ClaspCheck 01846Participant

First identify the caliber, lift-angle setting, winding state and measurement position. Without those fields, the rate, amplitude and beat-error values lack enough context for a useful comparison.

ClaspCheck 01846Participant

Case 28 — Crown operation: when a forum cannot diagnose the resistance

A description of stiffness does not establish the cause. What information is safe and useful to collect before an inspection?

Exercise RWF-21599/28: address this question within its stated limits.

ClaspCheck 01846Participant

Case 10 — Comparing versions without mixing case sizes

Clarification for “Comparing versions without mixing case sizes”: the point beginning “Match reference, dimensions 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.

ClaspCheck 01846Participant

No single lighting setup settles that question. Compare multiple controlled angles and describe the visible observation without asserting material specifications that have not been verified.

ClaspCheck 01846Participant

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

A useful table has columns for date, position, winding state, lift angle, rate, amplitude and beat error. Keep the full recording so settings and stability can be checked.

ClaspCheck 01846Participant

Case 31 — Bracelet fit: measuring the usable clasp adjustment

Clarification for “Bracelet fit: measuring the usable clasp adjustment”: the point beginning “Record wrist circumference, removable links and the clasp…” 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.

ClaspCheck 01846Participant

Case 11 — A maintenance log that remains useful after a sale

Which information should a transferable maintenance log retain while protecting the owner’s identity?

Exercise RWF-15754/11: address this question within its stated limits.

ClaspCheck 01846Participant

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

ClaspCheck 01846Participant

Case 43 — QC photographs: perspective or a genuinely tilted index? · source wording exercise

Reader check for “QC photographs: perspective or a genuinely tilted index?”: distinguish the discussion point “Compare two independently aligned images before drawing a conclusion; an overlay…” 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: source wording. Retain the source wording beside any paraphrase.

ClaspCheck 01846Participant

Batch variation on coloured dials does happen in general. Plating, lacquer thickness and supplier changes can all shift tone, so the claim isn't implausible. Plausible isn't the same as confirmed, though. The thread should keep 'possible' and 'shown' as separate statuses rather than letting repetition turn a hypothesis into accepted fact.

ClaspCheck 01846Participant

Start with how you measured it. Comparing against a phone clock once a day for a week, at the same time, and noting the offset is reliable enough. One 24-hour reading isn't, because rate depends on wrist time, position overnight and state of wind. Average across several days before deciding anything.

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