Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running inference for report reconstruction? #5

Open
peiqi-sui opened this issue Nov 13, 2023 · 4 comments
Open

Running inference for report reconstruction? #5

peiqi-sui opened this issue Nov 13, 2023 · 4 comments

Comments

@peiqi-sui
Copy link

Really interesting work! I'm trying to test the effectiveness of PRIOR's report reconstruction on some clinical data, and I'm wondering if there's an efficient way to run inference without making significant changes to the repo?

Thank you so much for your help!!

@QtacierP
Copy link
Owner

Thanks for your attention. I will try my best to push these codes in Dec once I have finished my recent workload. It is worth noting that the "report reconstruction" only reconstructs the high-level prototypes rather than the linguistic reports. We only can visualize the prototype distribution over the memory bank.

@QtacierP
Copy link
Owner

QtacierP commented Nov 13, 2023

@peiqi-sui
Copy link
Author

Thank you for clarifying. This is the sentence from the paper that threw me off: "each sentence embedding is updated by a learnable sentence-wise prototype memory bank (SPB) for the final linguistic representation". It left me with the impression that the reports are being updated through the prototype memory bank.

In that case, it'd be amazing if you could make it possible to run inference on subregion-sentence alignment at some point. Much appreciated!

@QtacierP
Copy link
Owner

Right~ Aligning fine-grained features is our ultimate goal. To be honest, the results of VLP models in this regard are not yet promising for clinical applications. However, they do have the potential to enhance the explanations provided by these models. I will re-organize the related codes in the next update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants