Issue 845: User says Agilent 6495C can go down to a dwell time of 0.5ms, but we insist on integer dwell times in UI

issues
Status:closed
Assigned To:Guest
Type:Defect
Area:Skyline
Priority:3
Milestone: 
Opened:2021-11-11 15:05 by Brian Pratt
Changed:2026-01-06 12:50 by Brendan MacLean
Resolved:2026-01-06 12:49 by Brendan MacLean
Resolution:GitHub Move
Closed:2026-01-06 12:50 by Brendan MacLean
2021-11-11 15:05 Brian Pratt
Title»User says Agilent 6495C can go down to a dwell time of 0.5ms, but we insist on integer dwell times in UI
Assigned To»Kaipo
Type»Defect
Area»Skyline
Priority»3
See user's point #1 of https://skyline.ms/announcements/home/support/thread.view?rowId=53519 (other points are split into other issues)

Probably should check with Agilent to verify this, find out actual supported precision, are there other models that do this, etc

2021-11-11 15:11 Brian Pratt
User says "The Agilent 6495C can go down to a dwell time of 0.5ms (which we are currently running), however, skyline only allows integers in the Dwell time (ms) field when exporting a method. We changed it to 1 in order to export the method without an error, but if it is possible to allow lower dwell times in a future release, that would be helpful."

2026-01-06 12:49 Brendan MacLean
resolve as GitHub Move
Statusopen»resolved
Assigned ToKaipo Tamura»Brendan MacLean
Skyline issues have moved to GitHub Issues at https://github.com/ProteoWizard/pwiz/issues
Issues will be ported as necessary for active work.

2026-01-06 12:50 Brendan MacLean
close
Statusresolved»closed
Assigned ToBrendan MacLean»Guest