Closed MalikTeng closed 1 year ago
A quick update -- When I try to visualize the GP_ED.txt for Venus 2, the notebook print out the following,
This issue happens when I change the ED phase from 0 to another, e.g. 36. In that case, if the cine images don't have that many phases, e.g. only 20, the volume at that phase will be all zero and the notebook won't find any landmark points from the volume. This is quite common for manual labelling that choosing a phase as ED for SAX images while another phase for LAX images.
Consequentially, I stick to using your phase prediction network to decide the ED and ES frames instead of using the manually selected phases.
Just to clarify, the issue is that the ED points are not written to the guide points file? However, they still display correctly? Let me look into this a little since this is an issue that should be resolved.
I found the problem in the guidepointprocessing.py file, lines 279 - 282 for the SAX view (also in other locations for the LAX views, this occurs every place the write_to_GP_file() command is used).
ED is hard coded as 0 in this file (i.e., it will only recognize it ad ED if time is < 1). All other points are written to the ES file. Should be a simple fix.
Describe the bug Some times when after I manually correct the landmark points on 3CH view the notebook cannot process the guide points and throw errors below,
I print out the landmarks['MV1'] and there is no points recorded in landmarks['MV1'],
Series([], Name: MV1, dtype: object)
But those points should be recorded because I saw the output like this when printing out the 'three_chamber_df',