Skip to content

Update CRIMSON metric to align with up-to-date CRIMSON implementation#21

Open
MohammedSB wants to merge 1 commit intojbdel:mainfrom
MohammedSB:main
Open

Update CRIMSON metric to align with up-to-date CRIMSON implementation#21
MohammedSB wants to merge 1 commit intojbdel:mainfrom
MohammedSB:main

Conversation

@MohammedSB
Copy link
Copy Markdown

  • Auto-disable guidelines for default MedGemma HF model (model is trained without them)
  • Port robust JSON parsing from standalone (handles orphan keys, bad escapes, unescaped quotes, smart quotes, malformed arrays)
  • Fix scoring fallback defaults to match standalone (0.25 for unknown significance instead of 0.0)
  • Update default HF model to rajpurkarlab/medgemma-4b-it-crimson
  • Add cache_dir parameter for controlling HF model cache location
  • Add CRIMSON to README acknowledgments

I also saw that you added the repetition_penalty=1.1, which is good for helping the model not get stuck in the self-repetitive loop, which it sometimes does. This is especially true if the inputs are not formatting as expected. Do you have any tips on how to improve fine-tuning to avoid this?

- Match HF model init: padding_side="left", generation_config detection,
  flash attention 2 support, repetition_penalty=1.1
- Auto-disable guidelines for default MedGemma HF model (trained without them)
- Port robust JSON parsing from standalone (handles orphan keys, bad escapes,
  unescaped quotes, smart quotes, malformed arrays)
- Fix scoring fallback defaults to match standalone (0.25 for unknown
  significance instead of 0.0)
- Update default HF model to rajpurkarlab/medgemma-4b-it-crimson
- Add cache_dir parameter for controlling HF model cache location
- Add CRIMSON to README acknowledgments

I also saw that you added the repetition_penalty=1.1, which is good for helping the model not get stuck in the self-repetitive loop, which it sometimes does. This is especially true if the inputs are not formatting as expected. Do you have any tips on how to improve fine-tuning to avoid this?
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

Successfully merging this pull request may close these issues.

1 participant