Add warning and info message for beta and gamma parameters

[zly-idleness]

What does this PR do?

This adds a warning message to notify about the renaming of gamma and beta parameters during initialisation and also during loading.

before:

(vqa-audio) (base) jeeves@notebook-5064-cadence:~/ChatTTS/rhapsodyaudio$ python tmp_save_pretrain.py 
bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
Loading checkpoint shards: 100%|██████████████████████████████████████████████████████████████████████████████| 8/8 [00:16<00:00,  2.02s/it]
Some weights of Qwen2AudioForConditionalChatTTS were not initialized from the model checkpoint at /mnt/data/user/tc_agi/luoyuanZ/ChatTTS_default and are newly initialized: 

['tts.dvae.decoder.decoder_block.0.gamma', 'tts.dvae.decoder.decoder_block.1.gamma', 'tts.dvae.decoder.decoder_block.10.gamma', 'tts.dvae.decoder.decoder_block.11.gamma', 'tts.dvae.decoder.decoder_block.2.gamma', 'tts.dvae.decoder.decoder_block.3.gamma', 'tts.dvae.decoder.decoder_block.4.gamma', 'tts.dvae.decoder.decoder_block.5.gamma', 'tts.dvae.decoder.decoder_block.6.gamma', 'tts.dvae.decoder.decoder_block.7.gamma', 'tts.dvae.decoder.decoder_block.8.gamma', 'tts.dvae.decoder.decoder_block.9.gamma', 'tts.dvae.encoder.decoder_block.0.gamma', 'tts.dvae.encoder.decoder_block.1.gamma', 'tts.dvae.encoder.decoder_block.10.gamma', 'tts.dvae.encoder.decoder_block.11.gamma', 'tts.dvae.encoder.decoder_block.2.gamma', 'tts.dvae.encoder.decoder_block.3.gamma', 'tts.dvae.encoder.decoder_block.4.gamma', 'tts.dvae.encoder.decoder_block.5.gamma', 'tts.dvae.encoder.decoder_block.6.gamma', 'tts.dvae.encoder.decoder_block.7.gamma', 'tts.dvae.encoder.decoder_block.8.gamma', 'tts.dvae.encoder.decoder_block.9.gamma']

after:

(vqa-audio) (base) jeeves@notebook-5064-cadence:~/ChatTTS/rhapsodyaudio$ python tmp_save_pretrain.py 
bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
This model <class 'muffin.model.infer_qwen2tts.Qwen2AudioForConditionalChatTTS'>contains parameters that have been renamed internally (a few are listed below but more are present in the model):

Loading checkpoint shards: 100%|██████████████████████████████████████████████████████████████████████████████| 8/8 [00:14<00:00,  1.81s/it]

Fixes #29554 and #33190 (issue)

Before submitting

• Did you read the contributor guideline,
  Pull Request section?
• Was this discussed/approved via a Github issue or the forum? Please add a link
  to it if that's the case.
• Did you write any new necessary tests?

Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

[zly-idleness]

cc @amyeroberts

[amyeroberts]

Thanks for adding this @zly-idleness!

At the moment, this involves iterating over the loaded keys twice - once on L4116 and then on L4146. It also involves a redefinition of original_loaded_keys. We should rework the code to reduce the double logic

[zly-idleness]

Thanks for adding this @zly-idleness!

At the moment, this involves iterating over the loaded keys twice - once on L4116 and then on L4146. It also involves a redefinition of original_loaded_keys. We should rework the code to reduce the double logic

Thank you for pointing that out. I'll refactor the code to eliminate redundancy ☺️

[amyeroberts]

This doesn't work - this will modify both loaded_keys and original_loaded_keys:

In [1]: li_0 = list(range(10))

In [2]: li_1 = li_0

In [3]: for i in range(10):
   ...:     if i % 2:
   ...:         li_0[i] = -1
   ...:

In [4]: li_0
Out[4]: [0, -1, 2, -1, 4, -1, 6, -1, 8, -1]

In [5]: li_1
Out[5]: [0, -1, 2, -1, 4, -1, 6, -1, 8, -1]

[zly-idleness]

Thank you sir ! You are totally right , I forget add a copy() to ensure that the original_loaded_keys remain unaltered.

[amyeroberts]

Thanks for iterating!

At the moment, the logic is being forced around the old renaming code. There are also changes in the PR to the olmoe model which should be removed

[amyeroberts]

There shouldn't be any changes to this file in the PR

[amyeroberts]

This message isn't consistent - at the moment all of the renamed keys will be listed. Like in the other places where this logic is added, let's just take the first renames

[amyeroberts]

Rather than try and use the existing _fix_key logic - it would be better to rework this to:

• Not use copy
• To only add the first renaming case for gamma and beta respectively

[zly-idleness]

ok , I will do it