[INSTRM-1488] AG images was truncated on gen2 (vgw) Created: 10/Dec/21  Updated: 09/Jul/22  Resolved: 09/Jul/22

Status: Done
Project: Instrument control development
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: yuki.moritani Assignee: Yoshida, Hiroshige
Resolution: Done Votes: 0
Labels: EngRun
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to INSTRM-1458 Implement the DAMD-2 PFSD files. In Progress
Sprint: PreEngRun05 F, PreEngRun06June

 Description   

During the November 2021 run, AG images (AG6 image in most case) sent VGW didn't refresh occasionally after exposure. Inspection found that the image was truncated probably because transfer request was send before completing writing down the image file.



 Comments   
Comment by hassan [ 22/Jan/22 ]

The implementation of INSTRM-1458 should be made first before this ticket, as this problem may go away after that implementation.

Comment by yuki.moritani [ 18/Apr/22 ]

According to Yoshida-san, VGW actor copies the file which originally AGCC actor writes under /data/raw/yyyy-mm-dd/agcc/ to different place and creates another file with additional tables if any. The original image is now prefixed by an underscore ( "_" ) to avoid overwritten and truncation. This is under test between Yoshida-san and Eric-san.

Comment by eric [ 21/Apr/22 ]

So currently, we are not seeing the truncation.  If the test is using the same basic method as will be used in the engineering then I think PFS has solved this truncation issue.  However, we need to wait until the engineering with real cameras and guiding to close the ticket.

Comment by hassan [ 28/Apr/22 ]

This can be closed. Scratch that. Wait till real data is taken as Eric proposes in the earlier comment.

Comment by yuki.moritani [ 08/Jul/22 ]

Yoshida, Hiroshige , eric , Could you please confirm again that the truncation issue never happened this run?

Comment by eric [ 09/Jul/22 ]

I think this issue has been solved.  I didn't see any truncation issues in the last run.

 

Comment by hassan [ 09/Jul/22 ]

Closed following Eric's comment.

Generated at Sat Feb 10 16:36:00 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.