<ul>
<li>THIS MODEL HAS TWO FILES. YOU NEED TO USE THEM TOGETHER!!!</li>
<li>The associated trigger words are only for reference, it may need to be adjusted at some times.</li>
<li>The recommended weight for the embedding model is 1, which provides higher fidelity; if greater generalization is required, it can be lowered to 0.5. </li>
<li>The recommended weight for the LoRA model is 0.85; if there's evidence of contamination, consider lowering it to 0.5.</li>
<li>The preview images were generated using a few fixed test prompts and several prompts derived from clustering dataset features. Random seeds were used, ruling out cherry-picking. What you see is what you get.</li>
<li>No specialized training was done for outfits. You can check our provided preview post to get the prompts corresponding to the outfits.</li>
</ul>

<h2>How to Use This Model</h2>

THIS MODEL HAS TWO FILES. YOU NEED TO USE THEM TOGETHER!!!. 
In this case, you need to download both <code>sucrose_genshin.pt</code> and 
<code>sucrose_genshin.safetensors</code>, then use <code>sucrose_genshin.pt</code> as texture inversion embedding, and use
<code>sucrose_genshin.safetensors</code> as LoRA at the same time.

このモデルには2つのファイルがあります。一緒に使う必要があります！！！。
この場合、<code>sucrose_genshin.pt</code>と<code>sucrose_genshin.safetensors</code>の両方をダウンロード
する必要があります。<code>sucrose_genshin.pt</code>をテクスチャ反転埋め込みとして使用し、同時に<code>sucrose_genshin.safetensors</code>をLoRAとして使用してください。

这个模型有两个文件。你需要同时使用它们！！！。
在这种情况下，您需要下载<code>sucrose_genshin.pt</code>和<code>sucrose_genshin.safetensors</code>这两个文件，然后将<code>sucrose_genshin.pt</code>用作纹理反转嵌入，
同时使用<code>sucrose_genshin.safetensors</code>作为LoRA。

이 모델은 두 개의 파일이 있습니다. 두 파일을 함께 사용해야 합니다!!!. 
이 경우에는 <code>sucrose_genshin.pt</code>와 <code>sucrose_genshin.safetensors</code> 두 파일을 모두 다운로드하신 다음에 <code>sucrose_genshin.pt</code>을 텍스처 반전 임베딩으로 사용하고, 
동시에 <code>sucrose_genshin.safetensors</code>을 LoRA로 사용하셔야 합니다.

(Translated with ChatGPT)

The trigger word is <code>sucrose_genshin</code>, and the recommended tags are <code>best quality, masterpiece, highres, solo, {sucrose_genshin:1.15}, green_hair, animal_ears, glasses, semi-rimless_eyewear, hat, bangs, vision_\(genshin_impact\), blush, multicolored_hair, long_hair, hair_between_eyes, cat_ears, orange_eyes, breasts, yellow_eyes</code>.

<h2>How This Model Is Trained</h2>

This model is trained with <a href="https://github.com/7eu7d7/HCP-Diffusion" rel="ugc">HCP-Diffusion</a>. 
And the auto-training framework is maintained by <a href="https://huggingface.co/deepghs" rel="ugc">DeepGHS Team</a>.

<h2>Why Some Preview Images Not Look Like Sucrose Genshin</h2>

All the prompt texts used on the preview images (which can be viewed by clicking on the images) 
are automatically generated using clustering algorithms based on feature information extracted from the 
training dataset. The seed used during image generation is also randomly generated, and the images have 
not undergone any selection or modification. As a result, there is a possibility of the mentioned 
issues occurring.

In practice, based on our internal testing, most models that experience such issues perform better in 
actual usage than what is seen in the preview images. The only thing you may need to do is adjusting 
the tags you are using.

<h2>I Felt This Model May Be Overfitting or Underfitting, What Shall I Do</h2>

Our model has been published on <a href="https://huggingface.co/CyberHarem/sucrose_genshin" rel="ugc">huggingface repository - CyberHarem/sucrosegenshin</a>, where
models of all the steps are saved. Also, we published the training dataset on 
<a href="https://huggingface.co/datasets/CyberHarem/sucrose_genshin" rel="ugc">huggingface dataset - CyberHarem/sucrosegenshin</a>, which may be helpful to you.

<h2>Why Not Just Using The Better-Selected Images</h2>

Our model's entire process, from data crawling, training, to generating preview images and publishing, 
is 100% automated without any human intervention. It's an interesting experiment conducted by our team, 
and for this purpose, we have developed a complete set of software infrastructure, including data filtering, 
automatic training, and automated publishing. Therefore, if possible, we would appreciate more feedback or 
suggestions as they are highly valuable to us.

<h2>Why Can't the Desired Character Outfits Be Accurately Generated</h2>

Our current training data is sourced from various image websites, and for a fully automated pipeline, 
it's challenging to accurately predict which official images a character possesses. 
Consequently, outfit generation relies on clustering based on labels from the training dataset 
in an attempt to achieve the best possible recreation. We will continue to address this issue and attempt 
optimization, but it remains a challenge that cannot be completely resolved. The accuracy of outfit 
recreation is also unlikely to match the level achieved by manually trained models.

In fact, this model's greatest strengths lie in recreating the inherent characteristics of the characters 
themselves and its relatively strong generalization capabilities, owing to its larger dataset. 
As such, this model is well-suited for tasks such as changing outfits, posing characters, and, 
of course, generating NSFW images of characters!😉".

For the following groups, it is not recommended to use this model and we express regret:

<ol>
<li>Individuals who cannot tolerate any deviations from the original character design, even in the slightest detail.</li>
<li>Individuals who are facing the application scenarios with high demands for accuracy in recreating character outfits.</li>
<li>Individuals who cannot accept the potential randomness in AI-generated images based on the Stable Diffusion algorithm.</li>
<li>Individuals who are not comfortable with the fully automated process of training character models using LoRA, or those who believe that training character models must be done purely through manual operations to avoid disrespecting the characters.</li>
<li>Individuals who finds the generated image content offensive to their values.</li>
</ol>

Files with SHA256: 2c8576264fe68b255526ebb3642d4f671d5df9a4672fe95519457721ede2d737