-
Notifications
You must be signed in to change notification settings - Fork 16
Encountering anomalies in generating reports using MedViLL #22
Description
Certainly, here's a template for an email in English that you can send to the author regarding the issue you encountered while using their pre-trained model:
Subject: Inquiry About Anomaly in Generated Reports Using Your Pre-trained Model
Dear Professor/Dr./Mr./Ms. [Author's Name],
I hope this email finds you well.
First and foremost, I would like to express my sincere gratitude for sharing and publishing your pre-trained model. Your research has been incredibly helpful and inspiring for our work.
However, I have encountered an issue while using the pre-trained model you provided, and I am writing to seek your advice and assistance.
I followed the code and data preprocessing steps outlined in your publication, and used the same parameter settings to run the model. Unfortunately, the generated text reports contain a large number of repeated characters or nonsensical sequences, which significantly differ from the results described in your paper.
I have attempted to resolve the issue by:
Verifying the data preprocessing steps to ensure they are consistent with those used during training.
Checking the versions of all dependencies to match those specified in your published code.
Setting a fixed random seed for reproducible results.
Re-downloading the model file and verifying its integrity.
Debugging the decoder, but without finding any obvious issues.
Given the above, I kindly request your help or suggestions to address the problem I am experiencing. Specifically, I would appreciate information on:
Whether other users have encountered similar issues while using the model.
Any known issues or limitations that may cause anomalies in the generated reports.
Additional steps or parameter settings I may need to follow or adjust.
I would be deeply grateful if you could take the time to respond to my email and provide some guidance or advice. I am also willing to provide any necessary detailed information or log files to help you better understand the issue.
Thank you once again for your hard work and dedication. I look forward to your reply.
