<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2025-06-10T18:43:35Z</TimeStamp>
    <ReleaseNote>Adds a cursor and left/right arrow support for viewer</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-06-10T17:32:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-06-10T17:31:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-06-10T17:30:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-06-10T17:25:19Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0@52811
 
functionality is similar to case 44156 and same requirements as 44156 with the exception that 4.0 does not have decimation</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2025-06-05T20:32:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>I will move this one forward as well</Comment>
    <StatusString>Assigned</StatusString>
    <TimeStamp>2025-06-04T18:02:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Young Jung</User>
    <Comment>Chad email 5/20
 
43574: needs to be higher priority.
 
So, I moved from sprint 10 to Sprint 02. (this ticket is only 8hr)</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-05-20T21:16:26Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Young Jung</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-05-20T21:13:44Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Young Jung</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-05-12T22:30:07Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Young Jung</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-05-12T21:05:45Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Young Jung</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-05-09T22:32:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-05-08T15:28:07Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-03-17T20:11:04Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2025-03-17T16:11:41Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2025-03-13T15:39:11Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>related case 43446
     
VPG Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe.
     

  
 
##- Please type your reply above this line -##
 
You are a follower on this request (#13770, #dtsweb.zendesk.com/agent/tickets/13770). Reply to this email to add an internal note to the request.
         
   
Nathan Brown (DTS)
 
Mar 13, 2025, 09:49 CDT
 
This is implemented, currently in 4.4 branch only. This is a development branch which will not be released for public use for some months. I will follow up with feasibility to port this back to 4.0.
  
 Thanks everybody!
         
 
         
   
Nathan Brown (DTS)
 
Mar 13, 2025, 09:47 CDT
     
Private note
     
Toyota requested this feature for their labs using 4.0. I see this is in 4.4, so will also be in 5.0 eventually.
  
 In the meantime I'm making an assumption we'll plan to keep this in 4.4+ branches only since it's catering to decimated data, which didn't exist in 4.0?
  
 Planning the relationship with Toyota, thinking if I'll need to encourage them to think about moving to 4.4 when it's finished.
         
 
         
   
Rollin White (DTS)
 
Mar 4, 2025, 13:35 CST
     
Private note
     
Automatic Update from Manuscript:
 MS Case: http://manuscript.dts.local/f/cases/43446
 EventStatus: Resolved
 Timestamp (PT): 3/4/2025 11:32:00 AM
 User: Dan McFadden
 ReleaseNote:
 
 Comment:
 I would say this is by design - unless you are fully zoomed in and not decimated you can't guarantee individual spots, there may be a single data point that is hard to hit even if you can see one on the screen but are still not zoomed in. I think the primary use case is zoomed in.
         
 
         
   
Rollin White (DTS)
 
Feb 27, 2025, 12:35 CST
     
Private note
     
Automatic Update from Manuscript:
 MS Case: http://manuscript.dts.local/f/cases/43446
 EventStatus: Resolved
 Timestamp (PT): 2/27/2025 10:30:44 AM
 User: Dan McFadden
 ReleaseNote:
 
 Comment:
 4.4@52105
         
 
         
   
Rollin White (DTS)
 
Feb 10, 2025, 11:35 CST
     
Private note
     
Automatic Update from Manuscript:
 MS Case: http://manuscript.dts.local/f/cases/43446
 EventStatus: Opened
 Timestamp (PT): 2/10/2025 9:08:10 AM
 User: Chris Balogh
 ReleaseNote:
 
 Comment:
 Ticket: Data Viewer Cursor – DTS – Zendesk As a DataPRO user I need to see the data points as an EU/mv/ADC value at a specific time value. Each of the data points on the screen will be valid if we're decimated or not. The old style of data cursor would be acceptable.   The algorithm for LTTB is non-destructive to the data, it just removes non-displayable extra data points. I would be satisfied with having to zoom in to see the exact sample-to-sample view.   Talk to you soon, Chris
         
 
         
   
Chris Balogh (DTS)
 
Feb 10, 2025, 11:10 CST
     
Private note
     
43446: Re-Implement the Data Cursor in the Viewer - Manuscript
         
 
         
   
Nathan Brown (DTS)
 
Feb 10, 2025, 09:56 CST
     
Private note
     
I can't connect to VPN to check on updates with this FR. Is it scheduled? Do we have an eta?
  
 Thank you!
         
 
         
   
Dan McFadden (DTS)
 
Jul 17, 2024, 12:08 CDT
     
Private note
     
No, just going over important factors; Cursor point to point probably doesn’t make too much sense with down sampled data which is the default now in the viewer – so to add back in cursor mode we’d probably need to have a flag for when to turn off downsampling – maybe for crash industry large viewer abilities isn’t as important as point to point, so they can run with that flag turning off the large data viewer and turning on the point to point instead.
 
 
 
We can also go point to point in downsampled data but it seems that’s probably not useful as it’s not sample to sample, so we’d probably want to reject that, add in a way to turn off downsampling and turn back on cursor.
 
 
 
We should probably filter that through the new feature process as it needs priority decision then at that point.  Turning off LTTB is much simpler than turning it on, and cursor mode might be easily turned back on as well, so there’s a clear path to implementing with around a day or two of work, but probably should be discussed a little bit before it’s worked on.
 
 
 
~ Dan
 
 
                         
                         
       
       
                                       
Dan McFadden​​​​
     
Software Engineering Manager
                 
Diversified Technical Systems, Inc.
   
 | 
   
Seal Beach
   
, 
   
CA
                     
e:
       
dan.mcfadden@dtsweb.com
       
|
           
o:
       
+1 562 493 0158 x137
       
|
       
www.dtsweb.com
                                         
CONFIDENTIALITY: This email and any attachments may contain information from Diversified Technical Systems, Inc. (DTS) which​ is confidential ​and/or proprietary. If you received this transmission in error, any use, reproduction or dissemination of this transmission​ is strictly prohibited. ​Please delete this message and notify sender immediately.  
 ​EXPORT CONTROL NOTICE: This e-mail may contain technical data whose export, transfer, and/or disclosure may be controlled by​ the US ​International Traffic in Arms Regulation (ITAR) 22 CFR part 120-130 or the Export Administration Regulations (Commerce).
 ​
 ​
                   
 
                 
Attachment(s)
 ~WRD3085.jpg
         
 
         
   
Nathan Brown (DTS)
 
Jul 17, 2024, 11:53 CDT
     
Private note
     
Does this mean the feature request is rejected?
         
 
         
   
Dan McFadden (DTS)
 
Jul 17, 2024, 10:27 CDT
     
Private note
     
This was already present but was removed because now that the viewer is not showing actual data the point to point are lies – it now uses Largest triangle three bucket
 
timescaledb-toolkit/docs/lttb.md at main · timescale/timescaledb-toolkit · GitHub to downsample.
 
 
 
 
                         
                         
       
       
                                       
Dan McFadden​​​​
     
Software Engineering Manager
                 
Diversified Technical Systems, Inc.
   
 | 
   
Seal Beach
   
, 
   
CA
                     
e:
       
dan.mcfadden@dtsweb.com
       
|
           
o:
       
+1 562 493 0158 x137
       
|
       
www.dtsweb.com
                                         
CONFIDENTIALITY: This email and any attachments may contain information from Diversified Technical Systems, Inc. (DTS) which​ is confidential ​and/or proprietary. If you received this transmission in error, any use, reproduction or dissemination of this transmission​ is strictly prohibited. ​Please delete this message and notify sender immediately.  
 ​EXPORT CONTROL NOTICE: This e-mail may contain technical data whose export, transfer, and/or disclosure may be controlled by​ the US ​International Traffic in Arms Regulation (ITAR) 22 CFR part 120-130 or the Export Administration Regulations (Commerce).
 ​
 ​
                   
 
                 
Attachment(s)
 ~WRD0418.jpg
         
 
         
   
Nathan Brown (DTS)
 
Jul 16, 2024, 13:44 CDT
     
Private note
     
I logged into terminalserver to reach Manuscript.
  
 Here's a closed MS ticket. I haven't seen this feature in production--perhaps it was axed?
  
 http://manuscript.dts.local/f/cases/10908/Implement-Display-crosshair-and-data-values-feature
         
 
         
   
Nathan Brown (DTS)
 
Jul 16, 2024, 13:35 CDT
     
Private note
     
+Dan
  
 I believe this is already reported. I am unable to get to MS or Chris' MS/Buildserver tool to check.
  
 If there is not an MS ticket, is there enough info to implement? Data cursor to inspect the currently selected point in the Data Viewer?
         
 
         
   
Doug Nelson
 
Jun 26, 2024, 14:25 CDT
 
Thank you, Lower priority for us over our other tickets but definitely a large time saver.
         
 
         
   
Omar Bravo (DTS)
 
Jun 25, 2024, 12:09 CDT
 
Doug,
  
 Thank you for using the DTS help center!
  
 I am assigning this ticket to Nate for follow up.
  
 Best Regards,
  
 Omar
         
 
         
   
Doug Nelson
 
Jun 25, 2024, 11:17 CDT
 
Broken Issue off from ticket #13365.
 
 From 5-9-24:
 
 View Data after test, want to quickly inspect data points without the hassle of the set t0 workaround.
 We can mouseover and zoom in but it's difficult to track point-to-point to find inflection points, local maximums
         
----------------------------------------------
 Customer Details:
 Name: Doug Nelson ( doug.nelson@toyota.com )
 Organization: TEMA
 
----------------------------------------------
 If you no longer wish to see notifications for this ticket, please use the 'Unfollow' option in the Followers List.
 
You are an agent. Add a comment by replying to this email or view ticket in Zendesk Support.
     
Ticket #
   
13770
     
Status
   
On-hold
     
Requester
   
Doug Nelson
     
CCs
   
Jared Vogt, Tory Showek
     
Followers
   
Chris Balogh, Dan McFadden, Khanh Nguyen, Omar Bravo
     
Group
   
Support
     
Assignee
   
Nathan Brown
     
Priority
   
Normal
     
Type
   
Question
     
Channel
   
Web Form
     
 
 
This email is a service from DTS. Delivered by Zendesk.
 
[MKR954-9LVDV]Ticket-Id:13770Account-Subdomain:dtsweb</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2025-03-13T15:39:11Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>